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 ·

eleventree.netlify.app

https://eleventree.netlify.app/

95 82 100 100 CWV 17AXE

Data from Aug 20, 2026, 9:27 PM UTC — 21h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 21h

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.

Netlify Hosted by Netlify

Scores

95
Performance
no change
82
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 2.83 s 2.83 s 2.83 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 59 ms 59 ms 59 ms
FCP First Contentful Paint 1.68 s 1.68 s 1.68 s
Speed Index 1.68 s 1.68 s 1.68 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 96 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 344.0 kB 344.0 kB 344.0 kB
Requests 8 8 8
Third-party Weight 337.0 kB 337.0 kB 337.0 kB
Third-party CPU 54 ms 54 ms 54 ms
Unused JS 72.2 kB 72.2 kB 72.2 kB
Unused CSS 16.9 kB 16.9 kB 16.9 kB

By resource type

script 160.5 kB · 1 req
font 130.7 kB · 2 req
image 28.2 kB · 2 req
stylesheet 22.3 kB · 2 req
document 2.4 kB · 1 req
third party 337.0 kB · 6 req

Third parties 4 entities

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

Google Tag Manager 160.5 kB · 54 ms CPU
Cloudflare CDN 148.3 kB · 0 ms CPU
GitHub 26.0 kB · 0 ms CPU
shields.io 2.1 kB · 0 ms CPU

Page health

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

Main thread work

script evaluation 183 ms
other 90 ms
style layout 53 ms
script parse compile 47 ms
parse HTML 17 ms
paint composite render 8 ms

Axe violations axe-core 4.13.0, full rule set

17 violating nodes across 6 rules, 114 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 link-name — Links must have discernible text 11 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 2 nodes
  • minor empty-heading — Headings should not be empty 1 node
  • 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 3 of 15 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.

  • link-name — Links do not have a discernible name 11 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 2 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 20, 2026, 9:27 PM UTC 95 2.83 s 0 59 ms 344.0 kB 3/3 ±4 2,491 22.3s

Embed this score

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