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 ·

yiddishkeit.info

https://yiddishkeit.info/

96 93 100 91 –CWV 134AXE

Data from Aug 21, 2026, 2:46 PM UTC — 4h old.

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

Scores

96
Performance
no change
93
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.15 s — — 2.15 s 2.15 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 123 ms — — 123 ms 123 ms
FCP First Contentful Paint 2.15 s — — 2.15 s 2.15 s
Speed Index 2.15 s — — 2.15 s 2.15 s
TTFB Time to First Byte 638 ms — — 638 ms 638 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 64 ms
time to first byte 40 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 400.9 kB — — 400.9 kB 400.9 kB
Requests 9 — — 9 9
Third-party Weight 383.2 kB — — 383.2 kB 383.2 kB
Third-party CPU 94 ms — — 94 ms 94 ms
Unused JS 138.0 kB — — 138.0 kB 138.0 kB
Unused CSS 23.8 kB — — 23.8 kB 23.8 kB

By resource type

script 358.2 kB · 6 req
stylesheet 24.9 kB · 1 req
document 17.7 kB · 1 req
third party 383.2 kB · 7 req

Third parties 5 entities

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

Google Tag Manager 289.4 kB · 70 ms CPU
Bootstrap CDN 41.5 kB · 5 ms CPU
jQuery CDN 24.1 kB · 7 ms CPU
Google Analytics 20.9 kB · 10 ms CPU
Cloudflare CDN 7.3 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 592 ms — — 592 ms 592 ms
Long Tasks 3 — — 3 3
DOM Elements 349 — — 349 349
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 134 — — 134 134
A11y Failures 2 — — 2 2
A11y Failing Nodes 132 — — 132 132

Main thread work

script evaluation 343 ms
other 95 ms
script parse compile 88 ms
style layout 42 ms
parse HTML 16 ms
paint composite render 9 ms

Axe violations axe-core 4.13.0, full rule set

134 violating nodes across 4 rules, 661 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 131 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
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 2 of 20 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. 131 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, 2:46 PM UTC 96 2.15 s 0 123 ms 400.9 kB 3/3 ±1 2,472 24.3s

Embed this score

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