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 ·

eleventy-google-docs-starter.netlify.app

https://eleventy-google-docs-starter.netlify.app/

100 89 100 100 –CWV 8AXE

Data from Aug 20, 2026, 9:29 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

100
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 777 ms — — 777 ms 777 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 777 ms — — 777 ms 777 ms
Speed Index 777 ms — — 777 ms 777 ms
TTFB Time to First Byte 610 ms — — 610 ms 610 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 41 ms
time to first byte 12 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 827 B — — 827 B 827 B
Requests 1 — — 1 1
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 0 B — — 0 B 0 B

By resource type

document 827 B · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 80 ms — — 80 ms 80 ms
Long Tasks 0 — — 0 0
DOM Elements 41 — — 41 41
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 8 — — 8 8
A11y Failures 2 — — 2 2
A11y Failing Nodes 4 — — 4 4

Main thread work

other 49 ms
style layout 16 ms
script evaluation 9 ms
paint composite render 4 ms
parse HTML 2 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

8 violating nodes across 2 rules, 107 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 7 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 2 of 13 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.

  • target-size — Touch targets do not have sufficient size or spacing. 3 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:29 PM UTC 100 777 ms 0 0 ms 827 B 3/3 ±0 2,443 20s

Embed this score

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