Free tool
Free website speed test
Is your site slow? Enter its address. We measure it on mobile and on desktop with Google’s Core Web Vitals, then tell you what to fix first.
A website speed test measures how long a page takes to display and to respond, on mobile and on desktop. It gives a score from 0 to 100 and Google’s Core Web Vitals: LCP, good under 2.5 seconds; INP, good under 200 milliseconds; and CLS, good under 0.1.
Test your website speed
An address is all it takes. Keep this page open while it runs.
What the tool checks
- Google score, mobile and desktop
- LCP, INP, CLS: the Core Web Vitals
- Server response time, measured from Quebec
- Compression, HTTP/2, caching
- The 5 fixes with the biggest payoff
Free, no account needed.
Your result
Speed test result
The short answer
What is a website speed test?
A website speed test loads a page the way a visitor would and times every step: the first byte sent by the server, the first visible text, the big image at the top, the moment the page finally responds to clicks. The result fits in a score from 0 to 100, along with the Core Web Vitals Google uses to judge the experience of a page. The test runs twice, because a phone on a cellular network has nothing in common with a desktop on fibre. Our tool relies on Google’s PageSpeed Insights engine for the lab measurement, adds real Chrome user data when your site gets enough traffic, then checks your server itself from Quebec, Canada. You see what slows the page down, what it costs in seconds and where to start. No access to your site is needed, and it works on WordPress, Wix, Shopify or a hand-coded site.
A website is judged on a phone first: that is where most customers discover it.
What is at stake
Why does website speed matter?
Someone looking for a plumber, an accountant or an IT provider opens three results at once. The one that shows up first gets a chance. The others get closed before they show anything.
Google knows it. Core Web Vitals feed into its rankings, and AI engines read a light, well-built page more easily. A slow site loses on both sides: fewer visits, fewer quote requests.
- More visitors stay long enough to read your offer
- A slight edge on Google when relevance is equal
- Forms filled out on mobile without frustration
- Less bandwidth, hosting that lasts longer
The metrics
What do LCP, INP and CLS mean?
They are the three Core Web Vitals. Google picked them because they match what a visitor feels. LCP answers “is it loading?”: the time before the main content appears. INP answers “is it responding?”: the delay between a click and the response on screen. CLS answers “is it moving?”: the sum of layout shifts during loading, the ones that make you tap the wrong button. To pass the assessment, a page has to be in the green on all three, measured at the 75th percentile of real visits. Three supporting metrics help find the cause: FCP, TTFB and TBT. The table lists Google’s official thresholds, so you can read your result at a glance and know which number to work on first.
| Metric | What it measures | Good | Needs work | Poor | Common cause |
|---|---|---|---|---|---|
| LCPcore Largest Contentful Paint | Time before the main content appears: the hero photo, the top headline. | ≤ 2.5 s | 2.5 to 4 s | > 4 s | Heavy hero image, slow server |
| INPcore Interaction to Next Paint | Delay between a click, tap or key press and the response on screen. | ≤ 200 ms | 200 to 500 ms | > 500 ms | Too much JavaScript, third-party scripts |
| CLScore Cumulative Layout Shift | What moves while the page loads: the button that slides away just as you tap it. | ≤ 0.1 | 0.1 to 0.25 | > 0.25 | Images without dimensions, banners that push content |
| FCP First Contentful Paint | The first text or image that shows up. | ≤ 1.8 s | 1.8 to 3 s | > 3 s | Render-blocking stylesheets or fonts |
| TTFB Time to First Byte | How long the server takes to send the start of the page. | ≤ 0.8 s | 0.8 to 1.8 s | > 1.8 s | Slow hosting, no page cache |
| TBT Total Blocking Time | Time the page stops responding during loading. Stands in for INP in the lab. | ≤ 200 ms | 200 to 600 ms | > 600 ms | Large JavaScript files |
The performance score reads like this: 90 to 100 is fast, 50 to 89 needs work, under 50 is slow.
How it works
How does the speed test work?
Four steps, nothing to install. The test looks at your site from the outside, like a visitor.
- 01
You enter the address
Your home page or, better, the page that brings in customers.
- 02
Google measures the page
The PageSpeed Insights engine loads the page on mobile, then on desktop.
- 03
We measure from Quebec
Server response time, HTTPS, compression, HTTP/2 or HTTP/3, caching.
- 04
You see what to fix
Core Web Vitals, real-user data when Google has it, and the fixes that pay off most.
The fixes
How do you speed up a website?
Start with what weighs the most. On a small business site, images almost always come first: a 4 MB phone photo shown in a 600-pixel box is enough to fail LCP. Next come the scripts added over the years, a chat tool, two ad pixels, a slider, all blocking the page while the phone reads them. The server comes third: shared hosting without page caching can take more than a second just to answer. The last gains come from fine tuning, such as compression, fonts and space reserved for banners. Make one change at a time, then test again: you will know what actually helped. On WordPress, most of these fixes take an evening. On an old, overloaded theme, a redesign sometimes costs less than patching it, and you get a site that is easier to update.
- Slim down your imagesWebP or AVIF, at the size they are actually displayed, with width and height set. Images are often half of the page weight.
- Load what is lower down laterAdd loading="lazy" to images below the fold. Never on the hero image: it has to load first.
- Drop third-party scripts you do not needChat widgets, ad pixels, sliders, social widgets: keep the ones that pay off, remove the rest.
- Defer JavaScriptUse defer or async, remove inactive WordPress plugins, lighten the page builder.
- Speed up the serverPage caching, a recent PHP version, better hosting, a content delivery network (CDN) close to your visitors.
- Turn on compression and HTTP/2Brotli or gzip for text, HTTP/2 or HTTP/3 at the host, long cache lifetimes for images and stylesheets.
- Reserve space for every elementDimensions on images, room set aside for banners, cookie notices and ads, so the page stops jumping.
- Limit web fontsTwo families at most, self-hosted, preloaded, with font-display: swap.
Compare
Lab data or real visitors: what is the difference?
The test shows two kinds of data. They do not say the same thing, and they work best together.
| Criterion | Lab test | Real-user data (CrUX) |
|---|---|---|
| Who measures | A Google browser, one simulated visit | Real visitors using Chrome, over 28 days |
| Device | Mid-range phone on throttled 4G, then desktop | Your customers’ own devices |
| Responsiveness | TBT, since nobody clicks | INP |
| Available | Always | Only when the site has enough traffic |
| Good for | Finding the cause, checking a fix right away | Knowing what customers live through, what Google keeps |
Good habits to keep a site fast
- Test the pages that sell, not just the home page
- Look at mobile first: it is the result Google keeps
- Compress every photo before uploading it
- Test again after every new theme, plugin or script
- Keep WordPress up to date and remove idle plugins
- Follow the Core Web Vitals report in Google Search Console
Fixes or redesign
My site is slow: should I rebuild it?
Not necessarily. A recent site with oversized images can be fixed in a few hours. An old WordPress theme full of abandoned plugins stays slow even after weeks of tuning.
If the test stays under 50 on mobile even with clean images, read our page on website redesign: it explains how to rebuild the site without losing your rankings. For a first site, see website design for small businesses, built to pass this test from day one.
Speed is only one part of the picture. The free website audit also covers SEO, GEO, AEO and security, with a report reviewed by a specialist.
Go further
More free checks for your website
GEO checker
Can AI engines like ChatGPT read your site and cite it?
Security scanner
HTTPS, security headers, outdated software, domain email.
All our free tools
Seven tools to check your site, your compliance and your security habits.
To make sense of the terms: what is SEO, what is GEO, what is AEO.
Questions and answers
Website speed questions
How do I test my website speed?
Why is my website slow?
What are Core Web Vitals?
What is a good PageSpeed score?
Why does my score change from one test to the next?
Why is my site slower on mobile than on desktop?
Does website speed affect Google rankings?
Is the speed test free? Is there a limit?
A fast site that brings in customers
We go over your result with you and tell you plainly whether a few fixes will do or a redesign will pay off more.
Reviewed by Antonio Pazzi, president of OKTO Solutions · updated