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 ·

ribomation.se

https://www.ribomation.se/

76 89 100 100 CWV 13AXE

Data from Aug 21, 2026, 6:38 PM UTC — 34m old.

Built Awesome · 2 measurements · since Aug 21, 2026 · last attempt 34m

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 3.1.6 Built with Eleventy 3.1.6

Scores

76
Performance
no change
89
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.82 s 4.82 s 4.82 s
CLS Cumulative Layout Shift 0.039 0.039 0.039
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 3.19 s 3.19 s 3.19 s
Speed Index 3.19 s 3.19 s 3.19 s
TTFB Time to First Byte 621 ms 621 ms 621 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 167 ms
time to first byte 4 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.01 MB 2.01 MB 2.01 MB
Requests 54 54 54
Third-party Weight 74.8 kB 74.8 kB 74.8 kB
Third-party CPU 15 ms 15 ms 15 ms
Unused JS 0 B 0 B 0 B
Unused CSS 75.0 kB 75.0 kB 75.0 kB

By resource type

image 1.54 MB · 30 req
font 226.9 kB · 4 req
other 100.5 kB · 3 req
stylesheet 84.4 kB · 7 req
script 50.0 kB · 8 req
document 8.3 kB · 1 req
third party 74.8 kB · 7 req

Third parties 5 entities

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

Google Fonts 49.5 kB · 0 ms CPU
Cloudflare CDN 12.0 kB · 1 ms CPU
JSDelivr CDN 6.7 kB · 1 ms CPU
Unpkg 3.5 kB · 3 ms CPU
Plausible 3.0 kB · 10 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.05 s 1.05 s 1.05 s
Long Tasks 4 4 4
DOM Elements 670 670 670
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 13 13 13
A11y Failures 3 3 3
A11y Failing Nodes 16 16 16

Main thread work

other 411 ms
style layout 256 ms
script evaluation 204 ms
parse HTML 86 ms
paint composite render 63 ms
script parse compile 23 ms
garbage collection 8 ms

Axe violations axe-core 4.13.0, full rule set

13 violating nodes across 2 rules, 649 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 8 nodes
  • moderate heading-order — Heading levels should only increase by one 5 nodes

Accessibility failures 3 of 21 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. 8 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 5 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 3 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

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, 6:38 PM UTC 76 4.82 s 0.039 0 ms 2.01 MB 3/3 ±0 2,428 30.8s
Aug 21, 2026, 11:33 AM UTC TRACING_ALREADY_STARTED: An internal Chrome error occurred. Please restart Chrome and try re-running Lighthouse. 28.5s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show ribomation.se'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://www.ribomation.se/"></speedlify-score>