Performance

Website performance analysis
what’s measured and why it matters

Performance is how long your website takes to appear and to respond to the person using it: how heavy it is, how its images arrive and what the server is doing in the meantime. Wakaris measures it with 12 checks and explains every finding in plain language.

  • 12 checks
  • 6 possible findings
  • 6 guides
What’s reviewed

What Wakaris checks
in your website’s performance

That’s 12 checks grouped into 6 blocks. Each block is a finding that can show up in your report.

Finding01/ 06

Blocks3 checks

Performance metrics

They’re the three metrics Google uses as a page experience signal, and the only performance metrics with a public threshold: no need to interpret whether 2.4 seconds is good or bad, it’s written down.

What it checks

  • LCP (Largest Contentful Paint)Time until the largest visible element is rendered. No finding at 2,500 ms or less; limits between 2,500 and 4,000 ms; blocks above 4,000 ms.
  • CLS (Cumulative Layout Shift)Measures unexpected content shifts during load. No finding at 0.10 or less; limits between 0.10 and 0.25; blocks above 0.25.
  • TBT (Total Blocking Time)Adds up the blocking time of tasks longer than 50 ms during load. No finding at 200 ms or less; limits between 200 and 600 ms; blocks above 600 ms.
Read the guide: Performance metrics 

Finding02/ 06

Limits1 check

Page weight and load

Weight is the cause behind almost everything else. You can fine-tune the loading order, but if five megabytes have to come down, they have to come down: on mobile data that’s several seconds of waiting and part of your visitor’s data plan.

What it checks

  • Total transferred weightAdds up all bytes transferred during load. No finding at 1,600 KiB or less; limits between 1,600 and 5,000 KiB; blocks above 5,000 KiB.
Read the guide: Page weight and load 

Finding03/ 06

Limits2 checks

Response and delivery

TTFB is time in which nothing can happen: the browser has already asked for the page and is waiting. Everything optimized afterward starts with that delay already spent.

What it checks

  • TTFBTime from the start of navigation until the first byte of HTML is received. No finding at 800 ms or less; limits between 800 and 1,800 ms; blocks above 1,800 ms.
  • HTTP protocolChecks whether HTTP/2 or HTTP/3 is used when the origin serves 6 or more static resources. Blocks with HTTP/1.1 or earlier in that case; inconclusive with fewer than 6 resources.
Read the guide: Response and delivery 

Finding04/ 06

Limits2 checks

Caching and compression

They’re the two cheapest performance improvements there are: you turn them on once on the server, nothing has to be rebuilt and they affect every page at once.

What it checks

  • Static resource cachingChecks that cacheable resources have a minimum lifetime of 30 days (2,592,000 seconds). Blocks if at least one is below it.
  • Text compressionLooks for text resources sent without brotli, gzip or deflate. Blocks if there is one of 1.4 KiB or more whose estimated saving from compression is 10% or higher.
Read the guide: Caching and compression 

Finding05/ 06

Limits3 checks

Image optimization

Images are almost always the heaviest part of a page, and also where there’s the most to gain without touching the design: the same photo can take a tenth of the space with no visible difference on screen.

What it checks

  • Oversized imagesCompares the downloaded size with what’s needed given the actual on-screen dimensions and device pixel density. Blocks if any could save 4 KiB or more by resizing.
  • Image compressionFor JPEG and BMP, compares the original with a recompression at quality 85. Blocks if any could save 4 KiB or more.
  • Image formatCompares the actual download with efficient delivery for that format. Blocks if any image has an estimated saving of 4 KiB or more.
Read the guide: Image optimization 

Finding06/ 06

Affects1 check

Rendering cost

It’s why a lightweight page can feel heavy. It isn’t downloading anything: it’s repositioning thousands of elements, and while it does, it doesn’t respond to anything the visitor does.

What it checks

  • Forced reflowDetects forced reflows caused by JavaScript. No finding if none exceeds 30 ms; blocks if at least one does.
Read the guide: Rendering cost 

The label tells you how much each finding weighs: Blocks critical,Limits important,Affects could be better.

Why it matters

Why your website’s performance
matters

A slow website isn’t a technical problem: it’s people leaving before they see what you offer.

  • The wait gets noticed

    Someone arriving on their phone with an ordinary connection won’t wait for your website to finish loading. If it’s slow, the first thing they learn about you is the wait.

  • It counts for Google

    Google takes the loading experience into account when ranking results. Between two equally useful pages, the one that loads better starts with an advantage.

  • Every step drags

    A page that’s slow to respond makes every click longer: the form, the basket, the contact button. What’s hard to use gets abandoned sooner.

To understand it

Performance guides
to understand each finding

Each guide explains one finding from this area in plain language: what it is, how it’s measured, why it matters to you and how to fix it. The technical part is kept separate, for whoever looks after your website.

6guides on performance

See the 6 guides
Frequently asked questions

Common questions
on performance

How does Wakaris measure my website’s speed?

It loads your page in a real browser, just as a visitor would, and measures what happens: how long the main content takes to appear, how heavy the download is and how the server responds. There’s nothing to install and no access to give.

Why does the result change from one analysis to the next?

Because speed depends on things that vary: how busy the server is at that moment, the network or what’s already cached. It’s normal for the figures to move a little. What doesn’t change from one run to the next is the causes: unoptimised images, missing caching or more code than needed.

My website loads fast for me. Why does it come out slow?

Because your browser has already saved a good part of the website and you’re probably opening it on a good connection. The analysis loads it like someone arriving for the first time, which is exactly the visitor you want to win over.

Do I have to change hosting to make it faster?

Not necessarily. A good share of performance findings are solved on the website itself: compressing images, turning on caching or loading less code. The report separates what depends on the website from what depends on the server, so you know who to ask.

Who has to fix whatever comes up?

Usually whoever looks after your website or your hosting provider. Every finding comes explained, with the evidence that proves it and a ready-made prompt to fix it with an AI, and you can share it with a link.

How much does the performance analysis cost?

Nothing. Analysing a page is free, asks for no sign-up or card and gives you the result in a few seconds. Performance is reviewed alongside the other eight areas in the same analysis.