Speedfree audit

Audit in progressAudit complete

Free · no sign-up

Is your site fast enough?

Your page, loaded three times on a simulated phone over slow 4G. You see what keeps your customers waiting.

Nothing is changed. No email needed.

  • Slow 4G
  • 3 loads
  • Page weight
Right now, somewhere

The same page, two phones, the same network. The only difference: on the right, three images were made lighter and one word added to a tag. Watch who gets to read first.

Today · 8.2 MB
After the fix · 1.1 MB

The same page, twice side by side. On the right, three lighter images and one word in a tag. An hour’s work.

1.3 seconds. On the right, the text is there, the visitor is reading.

On the left, still blank. Hurried visitors are already gone.

5.4 seconds. The left page finally arrives, in front of nobody.

Four times faster, with identical content.

No site rebuild. Three images and one word.

What divides the time by four takes three images and one word in a tag.

On a desktop, at the office, on fiber, you’ll never see this wait. Your visitors will.

What goes into the score

Structural checks, the same from Paris to Tokyo. Load times are shown as references, with their method: they don’t enter the score.

Questions we get asked
Why not a simple stopwatch?

Because a stopwatch depends on everything: distance to the server, network, device, time of day. Two runs on the same site can differ by 15%. Page weight, file count, oversized images, compression and caching (the copy the browser keeps) stay the same from Paris to Tokyo. They cause the slowness, and the score rests on them.

What are the displayed times worth?

They’re reference points, not the score. They come from a simulated phone on slow 4G with a throttled CPU, from our server in Malaysia. We show the median of our loads (up to three), the middle one. Only the server response time enters the score, because it doesn’t depend on the device.

Why does the place of measurement matter?

Because the server response time includes the trip to ours, in Malaysia. If your site is hosted in France or Europe, your visitors there get a faster answer. Compare this time mainly from one test to the next.

What does the score measure?

A score out of 100, by category. Weight (total, images, file count), delivery (compression, caching, protocol), display (blocking scripts, fonts, content from other sites) and the server. A check with nothing to look at, such as a page without web fonts, leaves the calculation.

Who fixes this, and how fast?

Your developer can redo the images in about an hour with the list provided. Compression and caching take a few lines at your host. Blocking scripts need one word, “defer”. Nothing here requires rebuilding the site.

Audit in progress

    Audit of example.com

    0,0 s
    0/ 100
    Reading your site

    Your score is building.

    Each check adds the points it earns, and shows the ones you’re missing.

    0points out of 100
    Reading your site Connecting to the site
    Connection Connecting to the site
    Audit details

    PricingFAQLegal noticePrivacyTermsContact us