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 ·

parkkamaki.com

https://parkkamaki.com/

100 93 96 92 CWV 1AXE

Data from Aug 21, 2026, 5:44 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 Built with Eleventy
GitHub Pages Hosted by GitHub Pages

Scores

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 796 ms 796 ms 796 ms
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 796 ms 796 ms 796 ms
Speed Index 796 ms 796 ms 796 ms
TTFB Time to First Byte 620 ms 620 ms 620 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 71 ms
time to first byte 11 ms

Page weight

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

image 105.6 kB · 4 req
document 3.0 kB · 1 req
script 2.5 kB · 4 req
stylesheet 2.4 kB · 1 req
other 1.6 kB · 2 req

Page health

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

Main thread work

other 76 ms
style layout 42 ms
script evaluation 18 ms
paint composite render 7 ms
parse HTML 5 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 260 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 html-has-lang — <html> element must have a lang attribute 1 node

Accessibility failures 1 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.

  • html-has-lang — `<html>` element does not have a `[lang]` attribute 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:44 AM UTC 100 796 ms 0 0 ms 115.2 kB 3/3 ±0 3,603 20.2s

Embed this score

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