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 ·

optifolio.vercel.app

https://optifolio.vercel.app/

100 100 100 100 CWV 2AXE

Data from Aug 21, 2026, 5:38 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
Vercel Hosted by Vercel

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.54 s 1.54 s 1.54 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 814 ms 814 ms 814 ms
Speed Index 814 ms 814 ms 814 ms
TTFB Time to First Byte 618 ms 618 ms 618 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 69 ms
time to first byte 15 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 17.0 kB 17.0 kB 17.0 kB
Requests 6 6 6
Third-party Weight 2.8 kB 2.8 kB 2.8 kB
Third-party CPU 1 ms 1 ms 1 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

document 5.4 kB · 1 req
image 5.3 kB · 2 req
stylesheet 3.5 kB · 1 req
script 1.8 kB · 1 req
font 967 B · 1 req
third party 2.8 kB · 2 req

Third parties 2 entities

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

Unpkg 1.8 kB · 1 ms CPU
Google Fonts 967 B · 0 ms CPU

Page health

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

Main thread work

other 134 ms
style layout 85 ms
paint composite render 20 ms
script evaluation 15 ms
parse HTML 8 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 1 rule, 422 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 2 nodes

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:38 AM UTC 100 1.54 s 0 0 ms 17.0 kB 3/3 ±2 2,423 23s

Embed this score

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