“Trustworthy on paper, but the page keeps tripping over its own shoelaces.”
For a companionship service, this site is doing the emotional equivalent of arriving on time with the wrong shoes: decent intent, messy execution. It looks like it wants to reassure families in Hertford and Ware, then hands them a slow-loading casserole of hesitation.
https://aircarerscompanion.co.uk/
screenshot
TECHNICAL SUMMARY
The good news: SEO is basically behaving, with crawlability, canonicals, robots, and structured data all present and accounted for. The bad news: performance is leaking credibility through a 4.7 s LCP, 3.9 s FCP, 13.9 s Speed Index, and 253 KiB of unused JavaScript, while the page is also carrying 2,200 ms of render-blocking baggage and 3 broken assets that can derail trust right before a lead is supposed to happen. Fix the hero/media payload and blocking scripts first; that’s the fastest path to better confidence, better engagement, and fewer families bouncing before they ever reach "Get Started."
🔥Your 4.7 s LCP is slower than a thoughtful phone conversation and less comforting.
💀
The page is technically alive, but performance makes it feel like it’s arriving by bus from another county.
→
Compress the hero imagery and convert it to WebP/AVIF so the main visual stops dragging the page down.
LCP: 4.7 sImpact: highEffort: medium
Why this matters
The largest contentful paint is too slow for a local trust page, and the hero asset is the most likely thing stealing the first meaningful impression.
→
Defer non-critical JavaScript and cut render-blocking resources so the page can paint before it starts gossiping to the browser.
TBT: 20 msImpact: highEffort: medium
Why this matters
Render-blocking work is still delaying visible content, and the audit shows room to remove blocking behavior instead of making families wait for the page to wake up.
→
Enable CDN caching and long cache TTLs for static assets so repeat visits don’t keep reheating the same slow soup.
FCP: 3.9 sImpact: mediumEffort: low
Why this matters
The first contentful paint is too sluggish for a local service page, and better caching can reduce the wait without a full rebuild.