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 ·

tylersticka.com

https://tylersticka.com/

100 100 100 100 0AXE CWV

Data from Aug 21, 2026, 9:46 AM UTC 2d old

Built Awesome #57 · 1 measurement · since Aug 21, 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.

Eleventy 3.1.6 Built with Eleventy 3.1.6
Self-hosted · Apache Hosted by Self-hosted

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 1.54 s good
INP no data
CLS 0 good

Scores

100
Performance
no change
100
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.46 s 1.46 s 1.46 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.01 s 1.01 s 1.01 s
Speed Index 1.01 s 1.01 s 1.01 s
TTFB Time to First Byte 713 ms 713 ms 713 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.46 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 163 ms
time to first byte 114 ms

Field data Chrome UX Report, origin-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.54 s good 89.9% good
CLS CWV 0 good 99.3% good
FCP 1.52 s good 82.2% good
TTFB 1.05 s needs-improvement 58.5% good

Lab vs field

Lab LCP 1.46 s · field p75 1.54 s · real users are 1.05× slower than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.67 s 0 1.54 s 1.09 s
2026-08-08
2026-08-01
2026-07-25
2026-07-18
2026-07-11
2026-07-04
2026-06-27
2026-06-20
2026-06-13
2026-06-06
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 115 kB 115 kB 115 kB
Requests 13 13 13
Third-party Weight 0 B 0 B 0 B
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 21.5 kB 21.5 kB 21.5 kB
Unused CSS 0 B 0 B 0 B

By resource type

font 54.3 kB · 2 req
script 39.9 kB · 2 req
document 9.9 kB · 1 req
stylesheet 7.7 kB · 1 req
other 2.9 kB · 4 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 276 ms 276 ms 276 ms
Long Tasks 0 0 0
DOM Elements 227 227 227
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

other 118 ms
style layout 68 ms
script evaluation 66 ms
parse HTML 12 ms
paint composite render 10 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 332 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 21, 2026, 9:46 AM UTC 100 1.46 s 0 0 ms 115 kB 3/3 ±0 2,342 24.2s

Embed this score

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