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 ·

barsan.kz

https://barsan.kz/

77 96 100 100 7AXE CWV

Data from Aug 20, 2026, 3:47 PM UTC 3d old

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

Eleventy 3.1.6 Built with Eleventy 3.1.6
Netlify Hosted by Netlify

Scores

77
Performance
no change
96
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.89 s 4.89 s 4.89 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 238 ms 238 ms 238 ms
FCP First Contentful Paint 1.67 s 1.67 s 1.67 s
Speed Index 1.87 s 1.87 s 1.87 s
TTFB Time to First Byte 617 ms 617 ms 617 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.89 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.

resource load delay 87 ms
element render delay 83 ms
resource load duration 12 ms
time to first byte 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.33 MB 1.33 MB 1.33 MB
Requests 34 34 34
Third-party Weight 312 kB 312 kB 312 kB
Third-party CPU 128 ms 128 ms 128 ms
Unused JS 171 kB 171 kB 171 kB
Unused CSS 18.7 kB 18.7 kB 18.7 kB

By resource type

font 742 kB · 7 req
script 362 kB · 11 req
image 169 kB · 5 req
stylesheet 26.3 kB · 2 req
other 24.0 kB · 5 req
document 11.6 kB · 1 req
third party 312 kB · 4 req

Third parties 2 entities

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

Google Tag Manager 309 kB · 126 ms CPU
ahrefs.com 3.1 kB · 2 ms CPU

Page health

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

Main thread work

script evaluation 517 ms
other 352 ms
style layout 295 ms
script parse compile 115 ms
paint composite render 37 ms
parse HTML 29 ms
garbage collection 28 ms

Axe violations axe-core 4.13.0, full rule set

7 violating nodes across 3 rules, 689 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 5 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 1 of 26 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. 5 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, 3:47 PM UTC 77 4.89 s 0 238 ms 1.33 MB 3/3 ±8 2,252 28.1s

Embed this score

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