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 ·

fiff.de

https://www.fiff.de/

59 91 100 83 –CWV 151AXE

Data from Aug 21, 2026, 12:48 PM UTC — 6h old.

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

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
Self-hosted · Apache Hosted by Self-hosted

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP — no data
INP — no data
CLS — no data

Scores

59
Performance
no change
91
Accessibility
no change
100
Best Practices
no change
83
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 17.71 s — — 17.71 s 17.71 s
CLS Cumulative Layout Shift 0.009 — — 0.009 0.009
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 4.00 s — — 4.00 s 4.00 s
Speed Index 8.41 s — — 8.41 s 8.41 s
TTFB Time to First Byte 888 ms — — 888 ms 888 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 2.18 s
time to first byte 333 ms

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 — — — — —
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 — — — — —
2026-07-18 722 ms — 0 774 ms 306 ms
2026-07-11 714 ms — 0 740 ms 293 ms
2026-07-04 756 ms — 0 835 ms 304 ms
2026-06-27 738 ms 374 ms 0 833 ms 290 ms
2026-06-20 743 ms 314 ms 0 856 ms 285 ms
2026-06-13 870 ms 318 ms 0 960 ms 301 ms
2026-06-06 835 ms — 0 881 ms 300 ms
2026-05-30 863 ms — 0 886 ms 328 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 5.96 MB — — 5.96 MB 5.96 MB
Requests 201 — — 201 201
Third-party Weight 0 B — — 0 B 0 B
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 50.8 kB — — 50.8 kB 50.8 kB

By resource type

image 4.97 MB · 78 req
script 337.3 kB · 76 req
font 294.1 kB · 2 req
other 196.5 kB · 5 req
stylesheet 93.1 kB · 28 req
document 49.2 kB · 2 req
media 47 B · 1 req
third party 596.8 kB · 108 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.22 s — — 1.22 s 1.22 s
Long Tasks 3 — — 3 3
DOM Elements 1,950 — — 1,950 1,950
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 151 — — 151 151
A11y Failures 5 — — 5 5
A11y Failing Nodes 107 — — 107 107

Main thread work

other 641 ms
style layout 332 ms
script evaluation 94 ms
parse HTML 80 ms
paint composite render 57 ms
script parse compile 19 ms

Axe violations axe-core 4.13.0, full rule set

151 violating nodes across 6 rules, 3676 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.

  • moderate region — All page content should be contained by landmarks 90 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 42 nodes
  • serious aria-command-name — ARIA commands must have an accessible name 6 nodes
  • moderate heading-order — Heading levels should only increase by one 6 nodes
  • critical image-alt — Images must have alternative text 6 nodes
  • critical button-name — Buttons must have discernible text 1 node

Accessibility failures 5 of 32 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.

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 52 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 38 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 10 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 6 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 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, 12:48 PM UTC 59 17.71 s 0.009 0 ms 5.96 MB 3/3 ±23 2,468 54.6s

Embed this score

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