speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

savjee.be

https://savjee.be/

Data from Aug 21, 2026, 3:36 PM UTC — 2h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 2h

This URL redirects to https://simplyexplained.com/.

Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

Eleventy 2.0.1 Built with Eleventy 2.0.1
Cloudflare Hosted by Cloudflare

Scores

86
Performance
no change
93
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.98 s 3.98 s 3.98 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.06 s 2.06 s 2.06 s
Speed Index 2.06 s 2.06 s 2.06 s
TTFB Time to First Byte 491 ms 491 ms 491 ms

What LCP is made of

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

element render delay 226 ms
resource load delay 118 ms
resource load duration 86 ms
time to first byte 80 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 473.7 kB 473.7 kB 473.7 kB
Requests 13 13 13
Third-party Weight 473.2 kB 473.2 kB 473.2 kB
Third-party CPU 3 ms 3 ms 3 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 443.1 kB · 6 req
stylesheet 12.9 kB · 1 req
document 7.8 kB · 1 req
script 4.1 kB · 1 req
other 1.1 kB · 2 req
third party 20.8 kB · 2 req

Third parties 2 entities

473.2 kB transferred, 3 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

simplyexplained.com 452.9 kB · 3 ms CPU
YouTube 20.3 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 366 ms 366 ms 366 ms
Long Tasks 1 1 1
DOM Elements 128 128 128
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 25 25 25
A11y Failures 2 2 2
A11y Failing Nodes 17 17 17

Main thread work

other 272 ms
style layout 51 ms
script evaluation 17 ms
paint composite render 13 ms
parse HTML 11 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

25 violating nodes across 4 rules, 237 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 20 nodes
  • moderate region — All page content should be contained by landmarks 3 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 2 of 18 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 16 nodes
  • landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 21, 2026, 3:36 PM UTC 86 3.98 s 0 0 ms 473.7 kB 3/3 ±4 2,370 23s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show savjee.be's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify-score.js component code into your site!

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://savjee.be/"></speedlify-score>