Website Speed Test: How to Check Page Speed (and Fix It Fast)

A speed test freezes your page at a moment in time and reports how fast the main content appeared (LCP), how quickly it responds to clicks or taps (INP), and whether the layout jumps around as it loads (CLS). Together these are Google's Core Web Vitals, and they're the numbers that matter most to both rankings and visitors. Beyond those, a test reports page weight, request count, and how long the server itself takes to respond (TTFB).

Two different things matter: lab data (what a synthetic test in a datacenter reports) and field data (what real users experience on their own devices and connections). A fast lab test doesn't automatically mean fast in the real world — so an honest speed test looks at both.

You can test any URL in about thirty seconds, and you should test it the same way your visitors actually experience it.

• Test on mobile: most of your visitors are on phones over real connections — that's the number Google uses for rankings.
• Test a key while ignoring the homepage-only: a typical homepage is the lightest page; test your money pages too (the ones you need to convert).
• Compare the same page over a few run×: single runs bounce around, so the trend matters more than any one number.
• Use field data for the true story: a free scored audit and Search Console report real-user Core Web Vitals, which averaging over actual visits is far more honest than a single synthetic test.
• Isolate the bottleneck: once you know a page is slow, re-test with individual optimizations reverted to find the specific cause.

Nearly every slow site comes down to the same five problems. Find yours and you've found the fix.

• Oversized images: the #1 cause. A hero photo shipped at 5 MB with no compression will sink LCP no matter what else you do. Fix: compress to WebP/AVIF, cap dimensions, and serve the right size per device.
• Heavy JavaScript on load: animation libraries, chat widgets, and analytics pile up on the main thread and delay interactivity. Fix: defer or remove scripts that don't pay for themselves.
• A slow server: if TTFB is over ~600ms, the hosting or server config is the bottleneck. Fix: better hosting, caching, and a CDN.
• Render-blocking resources: scripts and stylesheets above the fold that block paint. Fix: defer, inline critical CSS, preload the LCP element.
• No browser caching: repeat visitors re-download everything. Fix: set long cache lifetimes on static assets.

Don't try everything at once. Do these in order and re-test after each — you'll usually see the biggest jump from the first two.

• Compress and resize your images: the single biggest, fastest win for most sites.
• Preload the LCP element: an explicit preload for your hero image can shave a second off LCP.
• Reserve space for media: width/height or aspect-ratio CSS stops layout shift cold.
• Cut or defer third-party scripts: each tracker adds work.
• Move to better hosting and add caching: a CDN with long cache lifetimes turns repeat visits into near-instant loads.
• Use font-display: swap: text renders instantly in a fallback font instead of waiting.

The fastest way to see where your site stands is to run the automated checks in one pass. A free scored audit reports your speed (and the rest of your site health — SEO, accessibility, security, content) in about 30 seconds, no signup needed for the preview. Then pair it with the 47-point website audit checklist to fix everything else, and track progress with your website health score.