How to Check Your Website Speed: A No-Jargon Guide for Founders

You can check your website speed using Google PageSpeed Insights — paste your URL at pagespeed.web.dev and get a score in under 30 seconds. No sign-up, no technical skills, no cost.

If the score is below 90, your site is losing visitors and rankings every day. Google's data shows that a page taking more than 3 seconds to load loses 53% of mobile users before they even see a word you've written. For a founder who has invested in design, copy, and ads, a slow site quietly destroys that investment.

This guide walks you through five free tools — step by step — and explains exactly what the numbers mean. You'll also get the top five causes of slowness and what to do about each one.

The Quick Answer: How to Check Your Website Speed Right Now

Website speed is measured by how long it takes your page to load in a real browser, on a real device, on a real internet connection. Google measures this with three metrics called Core Web Vitals — and every business website is scored on them.

If you have two minutes right now, do this:

1. Open a new browser tab.
2. Go to pagespeed.web.dev.
3. Type or paste your homepage URL into the box.
4. Click Analyze.
5. Wait 20–30 seconds for the results.

You will see two scores: one for Mobile and one for Desktop. Mobile almost always scores lower — that is normal. What matters is whether you are in the green (90+), amber (50–89), or red (<50) zone.

Screenshot your score. You'll use it later when you start fixing things so you can measure progress.

Tool 1: Google PageSpeed Insights — Step-by-Step

Google PageSpeed Insights is the most authoritative website speed tool available because it is built and maintained by Google — the same company that uses these scores as ranking signals. It tests your page using real Chrome user data (from millions of real visitors) combined with a simulated lab test.

Here is how to use it properly:

1. Go to pagespeed.web.dev.
2. Paste your full URL including https:// (e.g. https://yourdomain.com).
3. Click Analyze and wait — it takes 20–40 seconds.
4. When results load, look at the Mobile tab first — this is how most of your visitors arrive.
5. Note the score (0–100) and the three Core Web Vitals readings: LCP, INP, and CLS.
6. Scroll down to the Opportunities section — these are specific fixes ranked by how much time each one saves.
7. Also check Diagnostics — these are issues that do not directly affect the score but indicate deeper problems.
8. Test your three most important pages separately: homepage, a service page, and your contact page. Each page can have a different score.

One important note: if your site is new or low-traffic, PageSpeed Insights may say "Insufficient Field Data" in the top section. That's fine — scroll down to the Lab Data section, which still gives you a score based on a simulated test.

Tool 2: GTmetrix — Step-by-Step

GTmetrix is a free website speed testing tool (with paid upgrades) that gives you a more visual breakdown of your page load. It shows a waterfall chart — a timeline of every file your page loads, in order — which is invaluable when you are trying to identify exactly what is slowing you down.

1. Go to gtmetrix.com.
2. Create a free account (optional, but it saves your reports and lets you test from multiple locations).
3. Paste your URL into the test field.
4. Click Test your site.
5. GTmetrix will run the test and return a Performance Score (A–F) and a Structure Score (how well-built the page is).
6. Click the Waterfall tab — you will see a bar for every file your page downloads. Files with the longest bars are your bottlenecks.
7. Look for any bar that extends beyond 2–3 seconds. That is your first target.
8. Click the Video tab to see a frame-by-frame recording of your page loading. This shows exactly what a visitor sees — and how long they see a blank screen before content appears.

GTmetrix grades your site from A (excellent) to F (failing). Aim for a Grade A or B. If you are on Grade C or below, your visitors are likely abandoning your site before it finishes loading.

Tool 3: Chrome DevTools — A Quick Look

Chrome DevTools is built into every Chrome browser. You do not need to install anything. It gives you a live performance view of your own page as it loads — useful if you want a quick sanity check without opening a third-party tool.

1. Open your website in Google Chrome.
2. Press F12 on Windows or Cmd + Option + I on Mac to open DevTools.
3. Click the Network tab at the top.
4. Press Ctrl + Shift + R (or Cmd + Shift + R) to hard-reload the page. This forces everything to reload fresh, as if a new visitor had arrived.
5. Watch the coloured bars appear in real time — each bar is one file your page downloads.
6. At the very bottom of the panel, look at the total load time: "DOMContentLoaded: X ms" and "Load: X ms". Aim for Load under 3,000 ms (3 seconds).
7. Click the Performance tab for a more detailed breakdown. Press the record button, reload the page, then stop recording. You'll see a flame chart showing where time was spent.

Chrome DevTools is excellent for developers but can be hard to interpret without experience. For most founders, PageSpeed Insights and GTmetrix will give you everything you need.

Tool 4: WebPageTest — For a Deeper Dive

WebPageTest (webpagetest.org) is a free, open-source testing platform used by performance engineers worldwide. It lets you test your site from dozens of real locations and devices — including 3G mobile connections from cities like Mumbai, London, or New York.

To use it, go to webpagetest.org, paste your URL, choose a test location and browser, and run the test. The results include a Speed Index (how quickly content becomes visually complete), a filmstrip view, and a detailed waterfall. WebPageTest is more technical than GTmetrix, but the filmstrip alone is worth using once a quarter to see exactly what a visitor in a different country experiences when they land on your site.

For most founders, you can treat WebPageTest as an occasional second opinion rather than a monthly routine tool.

Tool 5: Google Search Console Core Web Vitals Report

Google Search Console (GSC) is the closest thing to official Google feedback on your site's performance. Unlike the other tools, it shows real-world data from actual visitors to your site — not simulated tests. It groups your pages into Good, Needs Improvement, and Poor buckets, based on how they actually performed for real users over the past 28 days.

1. Go to search.google.com/search-console and sign in with the Google account connected to your site.
2. In the left sidebar, scroll to Experience and click Core Web Vitals.
3. You will see two reports: one for Mobile and one for Desktop.
4. Click the Mobile report and look at the breakdown: how many URLs are Good, Needs Improvement, and Poor.
5. Click Open Report to see a list of specific failing pages.
6. Click any individual page URL to see which Core Web Vital metric (LCP, INP, or CLS) is failing and why.
7. Use the PageSpeed Insights button inside GSC to jump directly to the detailed diagnosis for that page.

The GSC Core Web Vitals report is the single most important report for your Google rankings. A page flagged as Poor in GSC is actively being disadvantaged in search results. Fix Poor pages first, then work on Needs Improvement pages.

What the Scores Actually Mean: LCP, INP, and CLS in Plain English

Google measures website speed through three Core Web Vitals. These are not abstract developer metrics — they map directly to real experiences your visitors have every day.

LCP — Largest Contentful Paint

LCP measures how long it takes for the biggest visible element on your page to appear. Think of it as: when does a visitor see something meaningful — not a blank white screen, not a loading spinner, but actual content? That "something meaningful" is usually your hero image, your main headline, or your above-the-fold banner. Google considers an LCP under 2.5 seconds good. If your LCP is over 4 seconds, more than half your visitors have likely left before that element even appears.

INP — Interaction to Next Paint

INP measures how quickly your page responds when a visitor clicks a button, taps a menu, or submits a form. The analogy is a light switch — when you flip a switch, you expect the light to respond instantly. If there is a 2-second delay before anything happens on screen, the page feels broken. A good INP is under 200 milliseconds. A poor INP is over 500 milliseconds, which is the difference between a page that feels fast and one that feels stuck.

CLS — Cumulative Layout Shift

CLS measures how much your page jumps and shifts as it loads. Every time an element moves after you have started reading — because an image loaded late, an ad popped in, or a font swapped — that is a layout shift. A CLS score below 0.1 is good. A score above 0.25 is poor. High CLS is why you sometimes tap the wrong button on a mobile site because the page shifted just as you pressed. It is frustrating, and Google penalises it.

What Is a Good Website Speed Score?

Google's PageSpeed Insights scoring system is simple:

In practice, most professionally built business websites score 85–95 on desktop and 60–80 on mobile. Mobile scores are lower because mobile devices have slower CPUs, more limited memory, and often run on 4G rather than broadband. A mobile score of 65–75 with no Poor Core Web Vitals is a reasonable baseline for most sites.

If you are considering switching to Next.js, note that Next.js sites typically score 90+ on both mobile and desktop out of the box — because the framework is built around server-side rendering, static generation, and automatic image optimisation. Our clients regularly see a 20–40 point score jump after moving from a page-builder WordPress site to a Next.js build.

The Top 5 Reasons Your Website Is Slow — and How to Fix Each One

Website slowness almost always comes from one of five root causes. Here is each one in plain English, with the fix:

1. Unoptimised Images

Images are the single most common cause of slow websites. A photographer's portfolio or a hotel's gallery can have dozens of images at 4–8 MB each — when they should be under 100 KB. The fix: compress every image using a tool like TinyPNG or Squoosh, convert them to WebP format (which is 30% smaller than JPEG for the same quality), and ensure images are sized to their display dimensions — not uploaded at full camera resolution. On Next.js, the built-in <Image> component handles this automatically.

2. Too Many Plugins (WordPress)

Every WordPress plugin adds code that must load on every page visit. A site with 30–50 active plugins is loading dozens of extra JavaScript and CSS files — most of which are not needed on most pages. Audit your plugins quarterly. Deactivate and delete any plugin that is not actively being used. Replace multiple single-purpose plugins with one well-coded solution where possible. A leaner plugin stack is faster and more secure.

3. Cheap or Shared Hosting

Your hosting server responds to every visitor request. A shared hosting plan at $3/month puts your site on a server shared with thousands of other sites — if any of them spike in traffic, your site slows down. Good hosting matters. For WordPress, managed hosts like Kinsta or WP Engine are significantly faster than shared hosts. For Next.js, deploying to Vercel (the company that builds Next.js) gives you global edge caching with almost no configuration.

4. Render-Blocking JavaScript

Your browser builds a page by reading HTML from top to bottom. If it encounters a large JavaScript file halfway down, it stops — waits for that file to download and run — then continues. This is called render-blocking. The fix is to add defer or async attributes to non-critical scripts so they load after the visible page content. PageSpeed Insights will flag any render-blocking resources under Opportunities. This is a developer fix, but it is one of the highest-impact changes you can make.

5. No Content Delivery Network (CDN)

If your web server is in the US and a visitor is loading your site from Mumbai or Sydney, every file has to travel thousands of kilometres. A CDN stores copies of your site's static files (images, CSS, JavaScript) on servers in 50+ locations around the world. When a Mumbai visitor loads your page, they get files from a server in Mumbai — not New York. Cloudflare offers a free CDN plan that takes 10 minutes to set up and can cut load times in half for international visitors. For sites targeting Indian, UK, or global audiences, a CDN is not optional.

When to Call in a Professional

Some speed problems are straightforward — compress your images, clean up your plugins, move to better hosting. You can do those yourself. But other problems require a developer:

• Your PageSpeed Insights report shows render-blocking resources or unused JavaScript that you cannot identify.
• Your Core Web Vitals LCP is failing and you do not know which element is the culprit.
• Your site is on a page-builder (Elementor, Divi, or similar) and every fix creates new problems elsewhere.
• Your hosting is already good but scores are still below 60 on mobile.
• You have a large site (100+ pages) and need systematic fixes, not one-off patches.

These are all signs the underlying architecture of the site needs attention — not just surface-level tweaks. A professional web performance audit will identify every bottleneck, prioritise the fixes by impact, and tell you exactly what to rebuild versus what to optimise in place.

If your issues are more structural — slow scores across the board, a site built on a heavy page-builder, or a hosting environment you cannot change — it may be worth a conversation about switching to Next.js. A well-built Next.js site eliminates most of the performance problems described in this guide at the framework level. For a deeper look at what performance metrics to track, see our Core Web Vitals checklist for 2026.

Frequently Asked Questions

How do I check my website speed for free?

You can check your website speed for free by going to pagespeed.web.dev, pasting your URL, and clicking Analyze. Google PageSpeed Insights runs your page through a real-world performance test and returns a score from 0 to 100 — along with a list of what to fix. No account, no payment, no technical skills needed.

What is a good website speed score on PageSpeed Insights?

A score of 90 or above is considered Good by Google PageSpeed Insights. Scores between 50 and 89 are classified as Needs Improvement, and anything below 50 is flagged as Poor. Most well-optimised business websites score 85–95 on desktop and 60–80 on mobile — mobile scores are almost always lower because of slower connections and smaller screens.

Why is my website slow even though it looks simple?

A visually simple website can still be slow if the images have not been compressed, the hosting server is underpowered, or JavaScript files are loading before your page content. The design you see is separate from the underlying code and server performance. PageSpeed Insights will show you exactly which files and resources are causing the delay.

How often should I check my website speed?

Check your website speed at least once a month, and always after any significant change — a new plugin, a new image gallery, or a theme update. Speed can degrade silently over time as you add content. A monthly check with Google PageSpeed Insights takes under five minutes and catches problems before they hurt your rankings or conversions.

Does website speed affect Google rankings?

Yes — Google officially uses Core Web Vitals (LCP, INP, and CLS) as ranking signals through its Page Experience update. A slow site does not automatically disappear from Google, but a fast competitor with similar content will outrank you over time. Google's own data shows that as page load time goes from 1 second to 3 seconds, the probability of a user bouncing increases by 32%.