Why it matters
Speed affects every visit. A one-second delay noticeably increases how many mobile visitors give up. The fixes are usually unglamorous: caching, a CDN, image compression and removing scripts you don't need.
How to fix it
Check time to first byte in your scan (we time slow pages twice, so one cold cache isn't enough), then run PageSpeed.
Turn on page caching and a CDN.
Compress and resize images, and serve WebP or AVIF.
Remove unused plugins, widgets and third-party scripts.
Upgrade hosting if the server itself responds slowly.
How That One Crawler checks it
Slow server responseWarning
The server took over 1.8 seconds to start answering (time to first byte), which web.dev rates poor. Every visitor waits that long before anything appears.
Fix: Cache pages (a CDN or page cache), upgrade slow hosting, and cut slow database or API calls. Run PageSpeed for a detailed breakdown.
Frequently asked questions
What's a good page load time?
Aim for a Largest Contentful Paint under 2.5 seconds on mobile for most visitors. A server response under about 800 ms is a healthy start.
Should I trust lab data or field data?
Field data from real visitors (the Chrome UX Report) is what Google uses for Core Web Vitals. Lab data from PageSpeed tests helps you debug.
Find every page with this problem
Free, no signup, results in a couple of minutes. Your scans stay in your browser.