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 ·

multiline.co/mment

https://multiline.co/mment

100 92 100 92 CWV 3AXE

Data from Aug 21, 2026, 5:32 AM UTC — 13h old.

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

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

100
Performance
no change
92
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.10 s 1.10 s 1.10 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 55 ms 55 ms 55 ms
FCP First Contentful Paint 1.10 s 1.10 s 1.10 s
Speed Index 1.10 s 1.10 s 1.10 s
TTFB Time to First Byte 714 ms 714 ms 714 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.

time to first byte 186 ms
element render delay 170 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 43.8 kB 43.8 kB 43.8 kB
Requests 12 12 12
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 23.0 kB · 3 req
image 8.4 kB · 2 req
stylesheet 6.2 kB · 2 req
script 6.1 kB · 2 req

Page health

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

Main thread work

script evaluation 3.87 s
other 349 ms
style layout 327 ms
garbage collection 320 ms
paint composite render 152 ms
parse HTML 40 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 418 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 frame-title — Frames must have an accessible name 2 nodes
  • serious aria-hidden-focus — ARIA hidden element must not be focusable or contain focusable elements 1 node

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

  • frame-title — `<frame>` or `<iframe>` elements do not have a title 2 nodes
  • aria-hidden-focus — `[aria-hidden="true"]` elements contain focusable descendents 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, 5:32 AM UTC 100 1.10 s 0 55 ms 43.8 kB 1/3 2,474 253.2s

Embed this score

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