Free website speed test
Table of Contents
Test any page with Google PageSpeed Insights: performance score, Core Web Vitals and the fixes that would help most.
Results come from Google PageSpeed Insights and usually take 20 to 40 seconds. Tests run from Google's servers, not your device.
Updated November 2026
Key takeaways
- Use the free website speed test above: it runs Google PageSpeed Insights and shows your score, Core Web Vitals and the biggest fixes.
- A score of 90 to 100 is good; 50 to 89 needs improvement; below 50 is poor. Mobile scores are usually lower than desktop.
- Google judges page experience by Core Web Vitals from real users: LCP 2.5 seconds or less, INP 200 milliseconds or less, CLS 0.1 or less.
- Most small business sites get faster by compressing images, caching pages, cutting unused plugins and scripts, and using decent hosting.
Use the free website speed test above to check any page in about 30 seconds. Enter the address, choose mobile or desktop, and the test runs Google PageSpeed Insights: you get a performance score from 0 to 100, Core Web Vitals from real Chrome users (when Google has enough data), lab timings, and the fixes that would save the most time.
Updated November 2026.
How the website speed test works
The test sends your address to Google PageSpeed Insights, which does two things:
- Lab test. Google loads your page with Lighthouse, on a simulated mid-range phone and slower network for mobile (or a desktop profile), and measures how long each stage takes. This is repeatable, so it is ideal for checking fixes.
- Field data. Google looks up how real Chrome users experienced the page over the last 28 days, from the Chrome User Experience Report. This is what Google uses for page experience in search, but it only exists for pages with enough visitors.
The two can disagree. A page can score well in the lab and still feel slow to real users on older phones, or the reverse. When field data exists, treat it as the truth and use the lab test to find causes.
How to read your website speed test results
Performance score. Google’s Lighthouse score from 0 to 100: 90 to 100 is good, 50 to 89 needs improvement, and below 50 is poor. It combines several lab metrics, weighted toward loading and responsiveness.
Core Web Vitals (real users).
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | How long the main content takes to appear | 2.5 s or less | 2.5 to 4 s | over 4 s |
| Interaction to Next Paint (INP) | How quickly the page responds to taps and clicks | 200 ms or less | 200 to 500 ms | over 500 ms |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less | 0.1 to 0.25 | over 0.25 |
Google assesses each metric at the 75th percentile of visits: three out of four visits need to be in the "good" range for the page to pass.
Lab measurements. First Contentful Paint, Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift and Speed Index from the simulated load.
Opportunities. The specific changes that would save the most loading time, with an estimate of the savings.
What each metric means, and how to fix it
Largest Contentful Paint (LCP)
LCP is usually your hero image, a large heading or a banner. It is slow when the server responds slowly, the image is heavy, or scripts and stylesheets block rendering.
Fixes: compress and resize the hero image and serve it in WebP or AVIF; do not lazy-load the main image; preload it if needed; cut render-blocking CSS and JavaScript; improve server response with caching and better hosting.
Interaction to Next Paint (INP)
INP measures how long the page takes to respond after a tap or click. Heavy JavaScript is the usual cause: sliders, chat widgets, page builders and many tracking scripts.
Fixes: remove scripts you do not need; delay chat, social and marketing widgets until after the page loads or until someone interacts; keep plugins lean; avoid heavy page-builder effects.
Cumulative Layout Shift (CLS)
CLS rises when content moves while loading: images without dimensions, ads and embeds that push text down, or fonts that swap late.
Fixes: always set width and height on images and videos; reserve space for ads, embeds and banners; avoid inserting content above existing content; use font-display settings that reduce late swaps.
Total Blocking Time and Speed Index
Total Blocking Time (lab) counts time the main thread is too busy to respond; it tracks closely with INP problems. Speed Index shows how quickly the visible page fills in.
The fixes that speed up most small business websites
- Compress and resize images. Serve images no larger than they are displayed, in modern formats such as WebP or AVIF, and lazy-load images below the fold.
- Use caching. A caching plugin (for WordPress) or your host’s cache serves ready-made pages instead of building each one.
- Remove what you do not use. Every plugin, widget, chat tool and tracking script adds code; uninstall the ones you can live without.
- Defer non-essential scripts. Load analytics, chat and social widgets after the main content.
- Use a content delivery network (CDN). It serves files from a location close to each visitor.
- Choose decent hosting. Slow server response shows up as a long "time to first byte" and delays everything else.
- Reserve space for images and ads. Setting width and height stops content jumping, which improves CLS.
- Limit web fonts. Use one or two font families and only the weights you need.
- Avoid heavy sliders and auto-playing video on the homepage; a single well-compressed image usually converts as well.
A WordPress speed checklist
- Use a lightweight theme (see our guide to the best WordPress themes for blogs).
- Install one caching plugin and configure page caching and browser caching.
- Compress images on upload with an image optimisation plugin, and convert to WebP.
- Remove unused plugins rather than just deactivating them.
- Combine and minify CSS and JavaScript only if it does not break the layout; test after each change.
- Keep WordPress, the theme and plugins updated; newer versions are often faster.
- Use a recent PHP version supported by your host.
- Clean up the database occasionally (old revisions, spam comments, expired transients).
How to test website speed properly
- Test your most important pages, not just the homepage: a service page, a product page, a blog post and a contact page.
- Run each test two or three times and look at the typical result; lab tests vary a little between runs.
- Test mobile first: most local and small business traffic is on phones, and mobile is harder.
- Change one thing at a time and retest, so you know what helped.
- Watch field data over weeks: Core Web Vitals update on a rolling 28-day window, so improvements show up gradually.
Speed budgets: what to aim for
| Measure | Practical target for a small business page |
|---|---|
| Mobile performance score | 70 or more, ideally 90+ |
| LCP | 2.5 seconds or less |
| INP | 200 milliseconds or less |
| CLS | 0.1 or less |
| Total page weight | as small as practical; keep hero images compressed |
| Third-party scripts | only those you actively use |
Image optimisation guide
Images are the largest part of most small business pages. A practical guide:
| Image use | Typical display width | Format | Tip |
|---|---|---|---|
| Full-width hero or banner | about 1,600 to 2,000 px | WebP or AVIF | Compress hard; do not lazy-load it |
| Content image in an article | about 800 to 1,200 px | WebP | Lazy-load below the fold |
| Product or gallery thumbnail | about 300 to 600 px | WebP | Use responsive sizes (srcset) |
| Logo and icons | as small as possible | SVG | Vector files stay sharp at any size |
| Photos with transparency | as needed | WebP or PNG | PNG only when you need lossless quality |
Upload images at the size they are shown, not straight from a camera or phone at 4,000 px, and let your platform generate smaller versions for phones.
Hosting and website speed
| Hosting type | Speed | Good for |
|---|---|---|
| Basic shared hosting | Can be slow at busy times | Very small sites with little traffic |
| Managed WordPress hosting | Usually fast, with server caching built in | Most small business WordPress sites |
| Cloud or VPS hosting | Fast when configured well | Busy sites and stores, with technical help |
| Website builders (Wix, Squarespace, Shopify) | Hosting handled for you | Owners who want no server management |
If your server response time (time to first byte) is consistently slow, caching and a CDN help, but moving to better hosting often helps most.
Speed tips by platform
- WordPress: follow the checklist above; theme and plugin choices matter most.
- Shopify: limit apps (each can add scripts), compress product images, and choose a fast, modern theme.
- Wix and Squarespace: reduce heavy animations, video backgrounds and large galleries on key pages; compress images before uploading.
- Any platform: remove unused tracking pixels and embedded widgets, and keep the homepage simple.
Other website speed testing tools
| Tool | Best for |
|---|---|
| The website speed test on this page (PageSpeed Insights) | Quick scores, real-user Core Web Vitals and fixes |
| Lighthouse in Chrome DevTools | Testing pages locally or behind a login |
| Google Search Console, Core Web Vitals report | Seeing which groups of pages pass or fail across your whole site |
| WebPageTest | Detailed waterfalls and testing from different locations |
Why website speed matters for a small business
Visitors leave slow pages, especially on phones, and Core Web Vitals are part of how Google evaluates page experience. A faster site usually means more enquiries from the same traffic. If you are building or rebuilding a site, the free website builder creates lightweight pages, and the contractor website speed guide covers fixes for trade businesses. To check your local search basics too, run the free Local SEO Check.
Questions about website speed tests
What is a good website speed test score?
90 or above is good on Google’s scale. Many small business sites score 50 to 80 on mobile; aim to get Core Web Vitals into the green first.
Why is my mobile score lower than desktop?
The mobile test simulates a mid-range phone on a slower network, so heavy images and scripts cost more time.
Is this website speed test free?
Yes. It uses Google PageSpeed Insights, which is free; very heavy use can hit Google’s daily limit, in which case try again later.
How often should I test my website speed?
After any significant change (a new theme, plugin or design) and every few months otherwise. Real-user Core Web Vitals update over a rolling 28 days.
Why does my score change each time I test?
Lab tests vary slightly with network and server conditions. Run two or three tests and use the typical result.
My page has no real-user data. Why?
Google only shows field data when a page has enough Chrome visitors. Use the lab results, and check Search Console’s Core Web Vitals report for groups of pages.
Does website speed affect Google rankings?
Page experience, including Core Web Vitals, is one of many signals. Relevance and content matter more, but speed can make the difference between similar pages and affects how many visitors stay.
What slows down a WordPress site the most?
Usually heavy images, too many plugins, page builders with many effects, third-party scripts and slow hosting without caching.
How we put this together
The tool on this page calls Google’s public PageSpeed Insights service directly; Advanton does not alter the results. Metric definitions and thresholds follow Google’s published Core Web Vitals documentation.
Sources
- Google PageSpeed Insights and Lighthouse documentation (performance score bands, lab and field data).
- Google’s Core Web Vitals thresholds and 75th percentile assessment (web.dev).
- Chrome User Experience Report (CrUX) documentation.
Last reviewed November 10, 2026. Startup costs are estimates; check local prices, licensing and tax rules before you commit money.
This article is general information, not financial, legal or tax advice. Check the rules that apply to you or talk to a qualified professional before making decisions. See our disclaimer.

I am still learning from your website. I am absolutely enjoying reading about the free website testing tools. Keep up the good work!