speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

blog.dermah.com

https://blog.dermah.com/

99 100 77 100 0AXE CWV

Data from Aug 20, 2026, 7:08 PM UTC 3d old

Built Awesome #611 · 1 measurement · since Aug 20, 2026

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.

Amazon S3 Hosted by Amazon S3

Scores

99
Performance
no change
100
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.71 s 1.71 s 1.71 s
CLS Cumulative Layout Shift 0.013 0.013 0.013
TBT Total Blocking Time 83 ms 83 ms 83 ms
FCP First Contentful Paint 1.51 s 1.51 s 1.51 s
Speed Index 1.51 s 1.51 s 1.51 s
TTFB Time to First Byte 605 ms 605 ms 605 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.71 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 53 ms
time to first byte 27 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 430 kB 430 kB 430 kB
Requests 12 12 12
Third-party Weight 358 kB 358 kB 358 kB
Third-party CPU 92 ms 92 ms 92 ms
Unused JS 138 kB 138 kB 138 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 326 kB · 4 req
image 38.4 kB · 1 req
font 31.8 kB · 2 req
document 4.9 kB · 1 req
stylesheet 2.9 kB · 2 req
other 620 B · 1 req
third party 358 kB · 8 req

Third parties 4 entities

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

Google Tag Manager 287 kB · 70 ms CPU
Adobe TypeKit 32.0 kB · 0 ms CPU
Google Analytics 20.9 kB · 10 ms CPU
StatCounter 18.5 kB · 12 ms CPU

Page health

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

Main thread work

script evaluation 408 ms
other 128 ms
style layout 98 ms
script parse compile 75 ms
paint composite render 70 ms
parse HTML 7 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 244 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.

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:08 PM UTC 99 1.71 s 0.013 83 ms 430 kB 3/3 ±24 2,475 28.6s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show blog.dermah.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://blog.dermah.com/"></speedlify2-score>