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 ·

profectus.lv

https://profectus.lv/

78 99 100 100 34AXE CWV

Data from Aug 21, 2026, 5:42 AM UTC 2d old

Built Awesome #925 · 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 Built with Eleventy
Cloudflare Hosted by Cloudflare

Scores

78
Performance
no change
99
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 4.51 s 4.51 s 4.51 s
CLS Cumulative Layout Shift 0.066 0.066 0.066
TBT Total Blocking Time 133 ms 133 ms 133 ms
FCP First Contentful Paint 2.75 s 2.75 s 2.75 s
Speed Index 2.75 s 2.75 s 2.75 s
TTFB Time to First Byte 470 ms 470 ms 470 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 4.51 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 104 ms
resource load delay 28 ms
resource load duration 21 ms
time to first byte 11 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 763 kB 763 kB 763 kB
Requests 25 25 25
Third-party Weight 469 kB 469 kB 469 kB
Third-party CPU 100 ms 100 ms 100 ms
Unused JS 138 kB 138 kB 138 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 324 kB · 5 req
image 281 kB · 8 req
font 147 kB · 6 req
document 7.8 kB · 1 req
other 3.3 kB · 4 req
stylesheet 529 B · 1 req
third party 469 kB · 10 req

Third parties 4 entities

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

Google Tag Manager 289 kB · 85 ms CPU
Google Fonts 147 kB · 0 ms CPU
Google Analytics 20.9 kB · 12 ms CPU
Cloudflare 11.5 kB · 3 ms CPU

Page health

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

Main thread work

script evaluation 395 ms
other 218 ms
style layout 167 ms
script parse compile 90 ms
paint composite render 52 ms
parse HTML 13 ms

Axe violations axe-core 4.13.0, full rule set

34 violating nodes across 3 rules, 856 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 svg-img-alt — <svg> elements with an img or image role must have alternative text 30 nodes
  • moderate region — All page content should be contained by landmarks 3 nodes
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 2 of 24 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.

  • svg-img-alt — SVG elements with an `img` role do not have an accessible text alternative 30 nodes
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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:42 AM UTC 78 4.51 s 0.066 133 ms 763 kB 3/3 ±14 2,495 24.6s

Embed this score

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