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 ·

thepugautomatic.com

https://thepugautomatic.com/

100 88 100 100 CWV 1.1kAXE

Data from Aug 21, 2026, 4:40 PM UTC — 2h old.

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

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.

Netlify Hosted by Netlify

Scores

100
Performance
no change
88
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 1.35 s 1.35 s 1.35 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 972 ms 972 ms 972 ms
Speed Index 972 ms 972 ms 972 ms
TTFB Time to First Byte 603 ms 603 ms 603 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 41 ms
resource load delay 11 ms
resource load duration 7 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 84.1 kB 84.1 kB 84.1 kB
Requests 4 4 4
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 63.8 kB · 1 req
document 16.8 kB · 1 req
stylesheet 2.5 kB · 1 req

Page health

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

Main thread work

other 98 ms
style layout 80 ms
paint composite render 19 ms
parse HTML 16 ms
script evaluation 9 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

1073 violating nodes across 3 rules, 4133 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 1071 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 2 of 14 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. 1071 nodes
  • landmark-one-main — Document does not have a main landmark. 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, 4:40 PM UTC 100 1.35 s 0 0 ms 84.1 kB 3/3 ±0 2,491 39.9s

Embed this score

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