Search 110+ free tools… (e.g. json, vpn, password) ⌘K
Link Tools Dereferer Hide Referrer Link URL Shortener Affiliate Cloaker PayPal Links PayPal DonationPayPal Links Privacy Tools Password Generator Cloudflare Resolver My Referrer Torrent Tools Magnet → Torrent Torrent → Magnet Torrent Editor Pirate Bay Proxies Movierulz Proxies ExtraTorrent Proxies Dev Tools Base64 Encoder Hash Generator HTTP Headers Disposable Email Checker Company Blog About Us Contact Anonymize Free
Webmaster Tool

Website Speed Test

Measure your page load time, TTFB, page size and performance grade — instantly, no software needed.

⚡ Results take 5-15 seconds — we're fetching your page from our server

What Page Speed Actually Measures

"Speed" is not one number. A page can start rendering quickly but remain unusable for seconds, or load fast on your connection and crawl on a phone. Modern measurement separates loading, interactivity and visual stability, which is why a single overall score can be misleading. What matters most is how quickly the main content appears and how soon the page responds to a tap or click — not the moment the browser finishes fetching every last asset.

The Metrics That Matter

Largest Contentful Paint (LCP) marks when the biggest visible element — usually a hero image or heading block — finishes rendering; Google treats 2.5 seconds or less as good. Interaction to Next Paint (INP) measures how quickly the page responds to user input, with 200 milliseconds or less considered good. Cumulative Layout Shift (CLS) quantifies unexpected movement as things load, scored 0.1 or below for a good result. Time to First Byte (TTFB) covers server response time and sits upstream of everything else — a slow TTFB caps how good the other metrics can be.

Lab Data vs Real-User Data

A test like this one produces lab data: a single measurement from one location on a simulated connection. It is repeatable and useful for spotting regressions, but it is not what Google uses for ranking. That comes from field data collected from actual Chrome users over a 28-day window. The two often disagree, and when they do the field data wins. Use lab tests to diagnose and iterate quickly, then confirm improvements in Search Console once real-user data catches up — which typically takes several weeks after a fix ships.

Frequently Asked Questions

Why does my score change between test runs?+
Lab tests are affected by server load, network conditions, third-party scripts and CDN cache state at the moment of measurement. Variance of several points between runs is normal. Run a test three times and use the median rather than reacting to any single result.
Is page speed actually a ranking factor?+
Yes, but a modest one. Core Web Vitals are part of Google page experience signals, and they matter most as a tiebreaker between pages of similar relevance. A fast page with weak content will not outrank a slower page that answers the query better. Speed is worth fixing for users first and rankings second.
What usually causes a slow LCP?+
The most common causes are a slow server response, render-blocking CSS or JavaScript in the head, an unoptimised hero image, and fonts that delay text rendering. Serving the LCP image in a modern format at the right dimensions, and preloading it, often produces the single biggest improvement.
How do I fix layout shift?+
Set explicit width and height attributes on images and video so the browser reserves space before they load. Reserve space for ads, embeds and banners. Avoid inserting content above existing content after load, and use font-display settings that do not cause text to jump when a web font arrives.
Why is my mobile score so much worse than desktop?+
Mobile tests simulate a slower CPU and network on purpose, because that reflects real conditions for many users. JavaScript execution is the usual culprit: phones parse and run scripts far more slowly than laptops. Reducing bundle size and deferring non-critical scripts helps mobile far more than desktop.
Done!