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 ·

preble1992.com

https://preble1992.com/

98 87 100 100 CWV 41AXE

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

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

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
Netlify Hosted by Netlify

Scores

98
Performance
no change
87
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 1.80 s 1.80 s 1.80 s
CLS Cumulative Layout Shift 0.065 0.065 0.065
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.63 s 1.63 s 1.63 s
Speed Index 1.63 s 1.63 s 1.63 s
TTFB Time to First Byte 604 ms 604 ms 604 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 140 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 403.1 kB 403.1 kB 403.1 kB
Requests 17 17 17
Third-party Weight 37.9 kB 37.9 kB 37.9 kB
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 310.9 kB · 7 req
script 46.2 kB · 1 req
font 34.2 kB · 1 req
document 6.2 kB · 1 req
other 3.4 kB · 4 req
stylesheet 755 B · 1 req
third party 37.9 kB · 5 req

Third parties 2 entities

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

Google Fonts 34.9 kB · 0 ms CPU
iconify.design 2.9 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 648 ms 648 ms 648 ms
Long Tasks 1 1 1
DOM Elements 318 318 318
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 41 41 41
A11y Failures 3 3 3
A11y Failing Nodes 35 35 35

Main thread work

script evaluation 310 ms
style layout 151 ms
other 134 ms
paint composite render 26 ms
parse HTML 16 ms
script parse compile 13 ms

Axe violations axe-core 4.13.0, full rule set

41 violating nodes across 3 rules, 448 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 37 nodes
  • serious listitem — <li> elements must be contained in a <ul> or <ol> 3 nodes
  • critical aria-required-children — Certain ARIA roles must contain particular children 1 node

Accessibility failures 3 of 26 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. 31 nodes
  • listitem — List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements. 3 nodes
  • aria-required-children — Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children. 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, 6:48 AM UTC 98 1.80 s 0.065 0 ms 403.1 kB 3/3 ±6 2,421 24.3s

Embed this score

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