clikiti
Sign in

Website speed test: page weight & speed check.

This free speed check downloads every asset a page pulls in and tells you how heavy it really is: total kilobytes, number of requests and which files cost the most. It also flags the usual causes of a slow page, such as oversized images, uncompressed or uncached files, render-blocking scripts and a slow server response.

  1. Fetch the live pageWhiskers, waiting
  2. Read the documentWhiskers, waiting
  3. Weigh every assetTiger, waiting
  4. Check colour contrast (WCAG AA)Shadow, waiting
  5. Run heuristics, speed & a11y checksPaws, waiting
  6. Walk the user flowsWhiskers, waiting
  7. Score itTiger, waiting

Paste any homepage. Your report lands here in about a minute.

Free · no sign-up · one page per scan · results in about a minute

What it checks

What the speed check measures

  • KBTotal page weight

    The real transferred size of the page and up to 60 of its assets, measured by downloading them, not estimated from the markup.

  • ReqRequest count

    How many files the page pulls in, and how many bytes come from third-party hosts you cannot optimise.

  • ImgHeavy images & video

    Images and video files large enough to delay the page, which usually means an unresized export or an old format.

  • GzipCompression & caching

    Scripts, styles and HTML sent without compression, and static files with no cache lifetime, so returning visitors download them again.

  • JSRender-blocking scripts

    Scripts in the head with no defer or async, which stop the browser from drawing anything until they load.

  • TTFBServer response time

    Time to first byte from a single request by our scanner, plus missing image dimensions and images that are not lazy-loaded.

Reading your results

How to read the report.

Page weight (KB)
Lighter is faster, especially on mobile data. As a rough guide, under 1,500 KB is lean for a small-business homepage and several thousand KB is heavy.
Requests
Each request has a cost. A high count usually points at many separate scripts, fonts or tracking tags.
speed findings
Findings tagged speed name the specific file or pattern responsible, so you know what to compress, resize or defer first.
What it is not
This is not a lab load-time test: it does not report Core Web Vitals or Lighthouse timings. It measures what makes a page slow, which is usually where the fix is.

Beyond the scan

Want the fixed version?

A list of issues is a start. Clikiti also rebuilds the homepage with the same brand and real content, fixing what the scan found, so you can see the better version instead of imagining it.

Own the website?

Get a free homepage redesign concept.

Tell us your website and a professional web agency will send you a redesigned homepage concept. No cost, no obligation.

Get my site redesigned

Run an agency?

Send prospects the audit and the redesign.

Find prospects, scan their sites and send each one a finished homepage redesign on their own brand, as one link, before the first call.

See agency plans

Questions

Page weight & speed check FAQ.

Does this website speed test measure load time?

Not in seconds. It measures the causes of a slow page: page weight, request count, heavy files, missing compression and caching, render-blocking scripts and server response time. For lab timings such as Largest Contentful Paint, use a Lighthouse-based tool alongside it.

Does it report Core Web Vitals?

No, the free scan does not report Core Web Vitals. It focuses on page weight and the specific files and settings that usually drive those numbers.

What is a good page weight?

There is no single cut-off, but a small-business homepage under about 1.5 MB loads comfortably on mobile. Pages over 3–4 MB are usually carrying oversized images or video.

Why is my server response time different from other tools?

It is timed from a single request by our scanner, so it depends on where the scanner and your server are and whether your cache was warm. Treat it as a signal, not a benchmark.

Is the speed check free?

Yes, with no account, and it runs alongside the usability and accessibility checks in the same scan. A limit of a few scans per hour per connection applies.

More free tools

Same scan, other angles.