Speed Check (Light)

A light, automated check — not the deep audit. Paste a page address; we fetch it once from our server, time the response, weigh the HTML and count what it loads — scripts, stylesheets, images, fonts, embeds — and measure the first 24 assets. You get a score and a fix list.

A free, light website speed check that measures what a page loads: server response time, HTML weight, compression, render-blocking scripts, script and stylesheet counts, image sizes, DOM size and embeds — with the heaviest assets listed and a fix for each finding. Every number is measured from a real fetch of your page — not estimated. It is the quick, automated version for one page at a time. Nothing stored.

Every extra second on a phone sends a share of your visitors back to the search results — to the next result, which is a competitor.

Your page, timed from a real fetch by our server. Nothing stored.

Free · light check

Ten checks per ten minutes
  • Nothing stored
  • Public pages only
  • Measured from a real fetch
  • About 10 seconds
What exactly do we read?
Light check — one page, measured from a real fetch by our server: response time, HTML weight, compression, scripts, images (the first 24 assets weighed). For the deep audit (a person, the whole site), use the button under the result.

The page you enter is fetched once by our server (public sites only), read, and discarded — nothing is stored, and your own files never come into it.

What the research says

How load time changes what mobile visitors do

Google measured real mobile visits, and Deloitte measured what a tenth of a second was worth across 37 brand sites. The green band is the load time Google calls good.

good · under 2.5 spoor · over 4 s1 s3 s5 s6 s10 s+0%+50%+100%+32%+90%+106%+123%
3.0 s

At 3.0 s a mobile visitor is +32% more likely to leave than at 1 s, as Google published it. Measure your page →

How much more likely a mobile visitor is to leave, compared with a page that loads in one second.Source: Google / SOASTA Research, mobile page speed benchmarks, 2017 Source: web.dev, Core Web Vitals, 2024
53%of mobile site visitors leave a page that takes longer than three seconds to load.
Source: Google, New industry benchmarks for mobile page speed, 2017

The rise after mobile pages got 0.1 seconds faster.

  • Retail conversion rate8.4%
  • Retail spend per order9.2%
  • Travel conversion rate10.1%
Source: Deloitte & Google, Milliseconds Make Millions (37 brand sites), 2020

These figures are other people’s research, quoted as published. Your own site’s numbers come from the free checks and the audit.

After the check

Your site, looked after every week

Your site todayYour site, looked after

Left: your site as it stands today, with whatever this check finds and the things it cannot see from outside. Right: the same site with my team looking after it. It is checked every week, a backup is taken before anything changes, and if something breaks, my team looks into it and tells you what happened.

  • The findings fixed, in the order they matter
  • Checked again every week, with a backup taken first
  • Someone watching: uptime, speed, what Google sees
900+ projects
since 2017
4.9★
400+ five-star reviews on Fiverr
9+ years
building WordPress and Next.js sites

Support is the whole team, not one person — reach us any time, and someone picks it up.

“Working with Sandipan Das was fantastic! The attention to detail and professionalism in his work was outstanding, and his proactive communication and timely delivery made the entire process smooth. He crafted the website exactly as I envisioned—highly recommend! 👍”
Indoor Pro Golf · 3-page WordPress site · the project

Schedule a Meeting

Bring what the tool found. I lead every project, and on the call we go through the list together and decide what to fix first.

Schedule a Meeting

How it works

How to use the Speed Check (Light)

  1. 01Paste the address of the page.
  2. 02Read the checks: server response, HTML size, compression, render-blocking scripts, script count, images, stylesheets, DOM size, embeds.
  3. 03See the heaviest assets — usually a few images or scripts explain most of the weight.

Good to know

How this differs from PageSpeed Insights

PageSpeed runs the page in a browser and reports Core Web Vitals. This tool reads what the page asks the browser to download. The two agree on the causes: heavy images, too many scripts, no compression, slow hosting. Use this to see what to fix; use PageSpeed to confirm it worked.

In more depth

About the speed check (light)

Why websites are slow — the usual four

Images that are far bigger than the space they fill; too many scripts (plugins, tag managers, chat widgets, three fonts); a server that takes a second to start answering; and nothing cached or compressed. The fixes for all four are well known.

The check shows which of the four you have. The heaviest-assets list at the bottom usually explains most of the total in three or four lines.

What a speed job actually involves

Resize and convert images (the image tools on this site do it), defer or remove scripts, enable compression and caching, and — if the server response is slow — move hosting. It is fixed-scope work: we can tell from this list what it will take.

FAQ

Speed Check (Light) — questions

How is this different from Google PageSpeed Insights?

PageSpeed renders the page in a browser and reports Core Web Vitals scores. This tool reads what the page asks the browser to download and measures it. It answers the question PageSpeed leaves you with: what exactly is heavy.

What is TTFB?

Time to first byte — how long the server takes to start answering. Under 600 ms is healthy. Over 1.5 s points to the server, usually a missing page cache or a hosting plan short of resources for the site, and no amount of image optimisation fixes it.

What is a render-blocking script?

A script in the <head> without defer or async. The browser stops building the page until it downloads and runs. Adding defer is often a one-word fix.

Why only 24 assets measured?

To keep the check fast and light on the site being checked. The first 24 in the HTML are usually the ones that matter (they load first); the counts cover everything.

What does the score mean?

The share of checks that pass. It is a light page-weight score from a real fetch — not a Core Web Vitals score — so use it to find what to fix, then confirm with PageSpeed.

More tools

The other tools

All tools

Next step

Need a tool that does not exist yet?

Small internal tools like these are a normal part of the work — tell me what your team does by hand.