Skip to content

Free Performance tool

Page speed test, in plain English

Enter an address and we measure how the page is served: server response, page weight, images, compression, caching, blocking files and third-party scripts, each with a plain-English fix. When Google’s lab test is available you also get Lighthouse scores, Core Web Vitals and real-visitor data.

Free to use, no account, and what you check is not stored.

( 01 )  How it works

  1. 01

    Enter an address

    Any public page works: a homepage, a product page, a landing page.

  2. 02

    We measure it

    We load the page and every file it asks for, and check how each is sized, compressed and cached.

  3. 03

    Fix the top of the list

    Findings are ordered by impact, each with the fix. Start with the red ones.

( 02 )  The short guide

Core Web Vitals in plain English

Largest Contentful Paint (LCP) is when the main content has appeared; good is 2.5 seconds or less. Interaction to Next Paint (INP) is how quickly the page responds to taps and clicks; good is 200 milliseconds or less. Cumulative Layout Shift (CLS) is how much the layout jumps while loading; good is 0.1 or less.

Google judges each at the 75th percentile of real visits, so three out of four visitors need a good experience for the page to pass.

Lab data and field data

A lab test loads the page once in a controlled browser, usually as a mid-range phone on a mobile connection. It is repeatable and good for finding causes. Field data comes from real Chrome users over the previous 28 days (the Chrome UX Report) and is what Google uses when it looks at page experience.

The two often disagree: your visitors may have faster phones than the lab, or slower ones. Use the lab to find what to fix and the field data to see whether it worked.

The fixes that usually matter most

Images: serve WebP or AVIF at the size they are shown, and lazy-load the ones further down the page. The server: cache pages at a CDN so the HTML arrives quickly. Blocking files: defer scripts and keep the CSS the first screen needs small. Third parties: every chat widget, heatmap and tag costs time on every visit. Fonts: preload the one or two the first screen uses.

How much does speed matter for search?

Core Web Vitals are part of Google’s page experience signals. They rarely outweigh relevant, useful content, but between similar pages they can tip the balance, and they matter a great deal to visitors on phones, who leave slow pages.

( 03 )  Questions

Why does the result change each time I test?

Networks, servers and third-party scripts vary from moment to moment. Lab scores typically move a few points between runs; look at the trend and the findings, not a single number.

Why are my numbers different from Google PageSpeed Insights?

Tests run from different places on different connections. Our quick check is measured from a server near you and does not run a browser, so it reports how files are served rather than a score.

Do I need a score of 100?

No. Aim for good Core Web Vitals for real visitors (LCP 2.5 s, INP 200 ms, CLS 0.1). Beyond that, extra points rarely change anything a visitor notices.

Can it test pages behind a login?

No. It can only measure public pages that load without signing in.

Is it free?

Yes. No account and no email wall. Nothing you enter is stored.

( 04 )  More free tools

Start a project

Need this done properly, across a whole site?

Let’s talk

Or write to hey@kliqer.com. We reply within two working days.