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 ·

gerencialeite.com.br

https://gerencialeite.com.br/

95 95 100 100 2AXE CWV

Data from Aug 20, 2026, 10:32 PM UTC 2d old

Built Awesome #522 · 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.

Netlify Hosted by Netlify

Scores

95
Performance
no change
95
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.88 s 1.88 s 1.88 s
CLS Cumulative Layout Shift 0.040 0.040 0.040
TBT Total Blocking Time 220 ms 220 ms 220 ms
FCP First Contentful Paint 811 ms 811 ms 811 ms
Speed Index 811 ms 811 ms 811 ms
TTFB Time to First Byte 604 ms 604 ms 604 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.88 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 50 ms
resource load delay 10 ms
resource load duration 6 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 598 kB 598 kB 598 kB
Requests 23 23 23
Third-party Weight 336 kB 336 kB 336 kB
Third-party CPU 127 ms 127 ms 127 ms
Unused JS 134 kB 134 kB 134 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 336 kB · 3 req
image 252 kB · 15 req
document 4.9 kB · 1 req
stylesheet 4.1 kB · 1 req
other 752 B · 1 req
third party 336 kB · 4 req

Third parties 2 entities

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

Facebook 175 kB · 77 ms CPU
Google Tag Manager 161 kB · 49 ms CPU

Page health

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

Main thread work

script evaluation 435 ms
other 172 ms
style layout 112 ms
script parse compile 105 ms
paint composite render 15 ms
parse HTML 9 ms
garbage collection 8 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 1 rule, 299 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 link-in-text-block — Links must be distinguishable without relying on color 2 nodes

Accessibility failures 1 of 19 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.

  • link-in-text-block — Links rely on color to be distinguishable. 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 20, 2026, 10:32 PM UTC 95 1.88 s 0.040 220 ms 598 kB 3/3 ±22 2,238 24.9s

Embed this score

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