Website Speed Test Online Free: Core Web Vitals and Page Weight

A website speed test only helps if it measures what visitors actually feel. This one loads your URL in a real headless Chromium browser and reports an overall grade, Core Web Vitals, total page weight and ranked recommendations. That matters because cheap checkers that only fetch HTML miss JavaScript execution and render-blocking resources - the usual cause of a slow feel. Largest Contentful Paint is how long until main content appears. Cumulative Layout Shift catches layout jumps that make people tap the wrong control. Interaction to Next Paint is how quickly the page responds to a click. Google uses all three for page experience, but they are worth fixing for users either way. Because each run drives a real browser, tests are limited to five per day.

Key benefits

• Renders in a real browser, so JavaScript cost and render-blocking resources are measured rather than estimated.
• Reports Core Web Vitals directly, which is what page-experience ranking actually considers.
• Breaks down page weight by resource, so you can see whether images, scripts or fonts are the problem.
• Gives specific recommendations rather than a bare number with no route to improving it.
• No account required to run a test.

How to use it, step by step

1. Enter the page URL. Test a specific page rather than just the homepage - templates differ, and a product page is often much heavier than the front page.
2. Run the test. A real browser loads the page, records every request and measures the vitals. This takes longer than a simple fetch because the page is genuinely rendered.
3. Read the grade and vitals first. These tell you whether there is a problem. The page weight breakdown tells you where it is coming from.
4. Work through the recommendations. They are ordered by impact. Fixing the top one or two usually moves the score more than everything else combined.

Common use cases

• Checking a site before launch, when slow pages are cheapest to fix.
• Diagnosing why a page feels sluggish when the server itself responds quickly.
• Comparing a page against a competitor to see where the difference actually is.
• Verifying that an optimisation - image compression, deferred scripts - had the effect you expected.
• Auditing a client site to produce concrete evidence rather than an impression.

Pro tips

• Test the page that actually gets traffic. Homepages are often the lightest page on the site and the least representative.
• Run a test before and after each change. One change at a time is the only way to know what helped.
• Images are the most common cause of a poor score, and also the easiest to fix - compress and correctly size them first.
• Ignore small score fluctuations between runs. Network variance moves the number by a few points without anything changing.
• A good lab score does not guarantee good field data. Real users are on slower devices and networks than a test environment.

Common mistakes to avoid

• Chasing a perfect 100. The last few points usually cost far more than they return, while the first thirty are often quick.
• Optimising the homepage only, when search traffic lands on product and article pages.
• Treating the score as the goal rather than the metrics behind it. LCP and INP are what visitors feel.
• Making several changes at once, then having no idea which one mattered.
• Ignoring layout shift because it does not affect the load time number - it is the most irritating problem for real users.

Frequently asked questions

How do I test my website speed?

Enter the page URL above and run the test. A real browser loads the page, then reports a grade, Core Web Vitals, the full page weight breakdown and prioritised recommendations.

Is this website speed test free?

Yes, with a limit of five tests per day. Each run drives a real headless browser, which is expensive to provide, so the cap keeps it available to everyone without an account.

What are Core Web Vitals and why do they matter?

Three metrics describing what a visitor experiences: Largest Contentful Paint (when the main content appears), Cumulative Layout Shift (whether the page jumps around while loading) and Interaction to Next Paint (how fast it responds to a click). Google uses them in page-experience ranking, and they map directly to whether a site feels fast.

Why did my site score lower than expected?

Usually large unoptimised images, render-blocking scripts and stylesheets, or a slow server response. The recommendations list what is costing the most on your specific page, ordered by impact.

Does this match what a real visitor experiences?

It closely approximates it by rendering in a real browser, but it is a lab test from one location on one connection. Real visitors vary by device, network and distance from your server, which is why field data in Search Console can differ from any lab tool.

Why do two runs give slightly different scores?

Network timing and server response vary between runs. Differences of a few points are noise; treat a change as real only when it is consistent and substantial.

People also search for

• website speed test free
• page speed checker
• core web vitals test
• why is my website slow
• gtmetrix alternative
• improve website loading speed
• test site speed mobile

Ready to get started? Open the Website Speed Test and try it now - completely free.