makehoney.com Website Audit Report

LCP is unavailable because the PageSpeed API returned 500, so the hero asset risk is the safest known performance suspect.

TBT could not be measured, but 3 console errors and a broken Font Awesome script are strong signs that JavaScript is slowing or destabilizing the page.

The audit failed outright with a 500, which blocked detailed performance diagnostics and left the site arguing with its own measurement tool.

The current title is slightly too long at 63 characters, which is enough to get clipped and awkwardly trimmed in search results.

Without an OG image, shared links lose visual context and look like they were forwarded from a document scanner.

Twitter card markup exists, but the preview image is absent, so social posts arrive looking unfinished instead of agency-grade.

There are 27 images, but the visual system still leans hard on structure; more intentional imagery would better support the layout.

25 missing alt attributes is not a corner case; it’s most of the image set, which makes the design less inclusive and less robust.

Viewport support exists, but responsive behavior still needs checking because the content-heavy layout is already carrying a lot.

The page has one H1, so the top line has to do more heavy lifting without drifting into brand poetry overload.

With 86 sentences on the page, the copy needs more scannability or it starts reading like a press release that missed its own deadline.

Four CTAs are fine in theory, but the page needs one obvious lead horse instead of a polite committee.

The page has no nav element, so users are being asked to navigate a content maze without the obvious map.

Three console errors mean the page is already failing in ways users won’t forgive just because the branding looks nice.

Four broken assets create visible friction and directly explain why key UI behavior is wobbling.

Four CTAs are present, but none is clearly dominant enough to anchor the contact decision.

The contact path exists, but it needs to be more obvious and easier to use if you want interested visitors to actually start the conversation.

One trust signal is thin for a retainer-based PR agency where credibility is the product.