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 ·

makotokw.com

https://makotokw.com/

66 87 100 100 CWV 32AXE

Data from Aug 21, 2026, 3:11 AM UTC — 16h old.

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

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.

Cloudflare Hosted by Cloudflare

Scores

66
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 7.26 s 7.26 s 7.26 s
CLS Cumulative Layout Shift 0.040 0.040 0.040
TBT Total Blocking Time 241 ms 241 ms 241 ms
FCP First Contentful Paint 2.87 s 2.87 s 2.87 s
Speed Index 2.87 s 2.87 s 2.87 s
TTFB Time to First Byte 611 ms 611 ms 611 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.

resource load delay 128 ms
time to first byte 123 ms
element render delay 61 ms
resource load duration 14 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.13 MB 1.13 MB 1.13 MB
Requests 22 22 22
Third-party Weight 250.0 kB 250.0 kB 250.0 kB
Third-party CPU 57 ms 57 ms 57 ms
Unused JS 173.6 kB 173.6 kB 173.6 kB
Unused CSS 66.9 kB 66.9 kB 66.9 kB

By resource type

font 365.6 kB · 5 req
script 342.3 kB · 3 req
image 298.2 kB · 4 req
stylesheet 73.8 kB · 3 req
other 41.1 kB · 4 req
document 2.0 kB · 1 req
third party 250.0 kB · 7 req

Third parties 5 entities

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

Google Tag Manager 155.6 kB · 53 ms CPU
Google Fonts 45.6 kB · 0 ms CPU
GitHub 28.4 kB · 0 ms CPU
Cloudflare 11.5 kB · 4 ms CPU
Gravatar 9.0 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 995 ms 995 ms 995 ms
Long Tasks 5 5 5
DOM Elements 222 222 222
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 32 32 32
A11y Failures 3 3 3
A11y Failing Nodes 34 34 34

Main thread work

script evaluation 426 ms
other 243 ms
style layout 199 ms
script parse compile 84 ms
parse HTML 23 ms
paint composite render 20 ms

Axe violations axe-core 4.13.0, full rule set

32 violating nodes across 3 rules, 353 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 30 nodes
  • critical aria-roles — ARIA roles used must conform to valid values 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 3 of 25 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. 30 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 3 nodes
  • aria-roles — `[role]` values are not valid 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, 3:11 AM UTC 66 7.26 s 0.040 241 ms 1.13 MB 3/3 ±3 2,403 27.4s

Embed this score

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