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 ·

almanac.chinesetaipeitouch.com/en

https://almanac.chinesetaipeitouch.com/en

100 81 100 100 9AXE CWV

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

Built Awesome #900 · 1 measurement · since Aug 20, 2026

This URL redirects to https://almanac.chinesetaipeitouch.com/en/.

A trailing slash only, so both forms are treated as one site rather than two — one history, measured once. Lighthouse follows the redirect, so the numbers below describe the canonical page; the only cost is an extra hop on each run.

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

100
Performance
no change
81
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 792 ms 792 ms 792 ms
CLS Cumulative Layout Shift 0.055 0.055 0.055
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 792 ms 792 ms 792 ms
Speed Index 792 ms 792 ms 792 ms
TTFB Time to First Byte 609 ms 609 ms 609 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 792 ms above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

time to first byte 46 ms
element render delay 43 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 231 kB 231 kB 231 kB
Requests 11 11 11
Third-party Weight 220 kB 220 kB 220 kB
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 0 B 0 B 0 B
Unused CSS 100 kB 100 kB 100 kB

By resource type

font 120 kB · 3 req
stylesheet 103 kB · 2 req
other 5.6 kB · 5 req
document 2.1 kB · 1 req
third party 220 kB · 4 req

Third parties 1 entities

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

Google Fonts 220 kB · 0 ms CPU

Page health

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

Main thread work

style layout 116 ms
other 96 ms
paint composite render 29 ms
parse HTML 23 ms
script evaluation 11 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

9 violating nodes across 5 rules, 532 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.

  • minor empty-table-header — Table header text should not be empty 4 nodes
  • moderate region — All page content should be contained by landmarks 2 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node

Accessibility failures 4 of 16 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. 1 node
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 1 node
  • landmark-one-main — Document does not have a main landmark. 1 node
  • td-has-header — `<td>` elements in a large `<table>` do not have table headers. 1 node

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:40 PM UTC 100 792 ms 0.055 0 ms 231 kB 3/3 ±17 2,326 22.7s

Embed this score

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