Skip to content
In development

Tenvey is not running yet. Every number on this site comes from one example website, not from a live service. What that means

Tenvey

Performance

Numbers next to the release that moved them.

Response time went from 215 ms to 299 ms after v2.4.1 shipped at 16:24. Tenvey draws the release on the curve instead of leaving you to correlate two tabs.

Response time · 24 h · all regions

215 ms → 299 ms +39%

  • 16:24 · v2.4.1 shipped
  • 16:38 · first 500 on /checkout
  • now · 296 ms

Core Web Vitals · /checkout

LCPNeeds work
2.1 starget under 2.5 s
INPGood
184 mstarget under 200 ms
CLSGood
0.04target under 0.1
TTFBNeeds work
410 mswas 240 ms

Four numbers, each with a verdict.

Core Web Vitals are measured per URL on a throttled 4G profile, because that is the connection your slowest visitors are on. A value on its own means nothing, so every one is shown against the threshold it has to clear.

On /checkout, LCP sits at 2.1 s against a 2.5 s target and TTFB has risen from 240 ms to 410 ms. Two of the four are fine — the page does not say so in green and leave you guessing which.

A finding names the file.

“Optimise your images” is not a finding. Tenvey lists the six assets that load at full resolution before anything can render, what each one weighs, and what they cost: 1.8 s on a 4G connection.

The homepage ships 3.4 MB of images. Four files account for almost all of it.

Render-blocking assets · /

Warning
  • hero-desktop.png1.9 MB
  • gallery-01.jpg612 KB
  • gallery-02.jpg588 KB
  • 3 more images301 KB

Total 3.4 MB

Serve these as WebP at the size they are displayed. That removes about 3.0 MB.

When it runs

Performance carries 30% of the health score, the heaviest of the five, and currently scores 87.

On every deployment
A full run starts within two minutes of a release and is diffed against the previous one, so a regression is attributed while you still remember what you changed.
Every six hours
Pages that did not change are re-measured anyway. Third-party scripts and image CDNs get slower without you shipping anything.
Every 60 seconds
Time to first byte rides along with the uptime check, which is why the curve above has a point for every hour and needs no agent on your server.

Also watched