“A brochure site that never made it to opening night.”
auto-doc.it isn’t just hard to trust — it’s hard to even accuse of trying. The page shows up like a courtroom exhibit labeled “absence,” then cross-examines itself with a straight face.
TECHNICAL SUMMARY
The biggest failure is basic page delivery: LCP is 20.9s, Interactive takes 28.8s, TBT sits at 1,900ms, and the page weighs 5,426KiB with 1,083KiB of unused JavaScript. SEO is missing the essentials too — no title, no meta description, no canonical, and zero schema — so discoverability and click-through are both getting mugged before they start.
🔥Your LCP of 20.9s is less “loading” and more “hostage situation.” The page spends 28.8s becoming interactive, which is a rude way to say the user has plenty of time to leave.
💀
The page loads like it’s being assembled by committee in the dark.
→
Compress hero images and switch them to WebP/AVIF to reduce the main load bottleneck.
LCP: 20.9 sImpact: highEffort: medium
Why this matters
A 20.9s LCP means the largest visible content is arriving absurdly late, so shrinking the hero payload is the fastest way to cut the delay.
→
Defer non-critical JavaScript and strip out blocking resources before they hijack the main thread.
TBT: 1,900 msImpact: highEffort: medium
Why this matters
With 1,900ms of blocking time, the browser is too busy babysitting scripts to respond to the user.
→
Enable CDN caching and longer cache TTLs for static files so repeat visits don’t relive the same tragedy.
FCP: 3.0 sImpact: mediumEffort: low
Why this matters
A 3.0s FCP suggests the browser is waiting too long to show anything useful, and better caching can trim that first visible delay.