“Enterprise voice AI, wearing a tuxedo over a power outage.”

The LCP is 12.2s, so the hero is clearly too heavy and delaying the first meaningful render.

430ms of TBT shows JavaScript is still chewing up responsiveness when it should be getting out of the way.

FCP is 4.7s, and the page is carrying enough bytes that better caching can materially reduce the wait.

27 missing alt texts is too many for an enterprise homepage and weakens accessibility plus image understanding.

With only 1 of 4 AI crawlers effectively allowed, discoverability in AI answers is being artificially limited.

With 102 images already on the page, the visual system should be doing more to support key sections instead of leaving gaps in the story.

27 missing alt texts is a direct accessibility and semantics problem, not a style preference.

Viewport support is present, but responsive behavior still needs verification to protect the design across devices.

The single H1 should do the heavy lifting, and right now it’s carrying the brand line instead of the value.

The page has 126 sentences and 1,526 words, which is a lot of reading for a homepage that needs faster comprehension.

Five CTA instances with only two labels makes the call-to-action hierarchy feel diluted rather than decisive.

Two console errors, including a null-style read, are user-facing instability waiting to happen.

Twelve broken assets is enough to create visible breakage and undermine confidence in the page flow.

Thirteen fields is a lot of effort for a book-a-demo journey and raises unnecessary completion risk.

Five CTA instances with only two labels suggests the primary action needs clearer hierarchy, not more duplication.

The contact path exists, but it should remain easier to reach for enterprise buyers who want a softer next step.

Four social proof items are available, but their placement needs to work harder at the decision point.