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 ·

blog.tomayac.com

https://blog.tomayac.com/

100 100 100 100 CWV 2AXE

Data from Aug 20, 2026, 7:19 PM UTC — 23h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 23h

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
Self-hosted · Caddy 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

100
Performance
no change
100
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 887 ms 887 ms 887 ms
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 887 ms 887 ms 887 ms
Speed Index 887 ms 887 ms 887 ms
TTFB Time to First Byte 707 ms 707 ms 707 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 141 ms
time to first byte 107 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
2026-07-11
2026-07-04
2026-06-27 1.78 s 0 1.93 s 1.06 s
2026-06-20 1.70 s 0 1.74 s 1.04 s
2026-06-13 1.63 s 0 1.61 s 1.02 s
2026-06-06 1.62 s 0 1.61 s 977 ms
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 74.7 kB 74.7 kB 74.7 kB
Requests 17 17 17
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

script 36.5 kB · 4 req
other 22.6 kB · 4 req
document 6.3 kB · 1 req
stylesheet 5.0 kB · 4 req
image 4.1 kB · 4 req

Page health

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

Main thread work

other 126 ms
style layout 63 ms
script evaluation 46 ms
paint composite render 22 ms
parse HTML 18 ms
script parse compile 12 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 505 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 label-title-only — Form elements should have a visible label 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 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, 7:19 PM UTC 100 887 ms 0 0 ms 74.7 kB 3/3 ±0 2,363 24.4s

Embed this score

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