speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time. Follow us on Mastodon or Bluesky.

Charts Compare Measurement runs Embed a score Open to Work

tottattoo.com

https://tottattoo.com/

–PERF 73A11Y 50BEST 91SEO ✗AXE –CWV

Ranks Overall #1,712 Built Awesome #1,098

Data from Oct 6, 2026, 12:51 PM UTC old Measured once a week · 15 runs since Aug 21, 2026

Elsewhere: PageSpeed Insights · Calibre · Treo · CrUX Vis · Tame the Bots · Wayback Machine

Lab data is measured using Lighthouse, Mobile mode unless otherwise specified. Field data is reported from Chrome UX Report (using p75 measurements).

Stack

Self-hosted · nginx Hosted by Self-hosted

Lighthouse Scores LAB Simulated

—
Performance
↓ -2 (-3.4%)
73
Accessibility
no change
50
Best Practices
no change
91
SEO
no change

Metrics LAB

No field data: the Chrome UX Report is not being collected for this project, so every figure below is from the Lighthouse run.

Metric Lab Simulated
Value Change / range Trend
LCP CWV (estimate) Largest Contentful Paint 4.31 s poor ↑ +1277 ms (+42%) significant 2.48 s – 4.31 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 0.018 good → no change 0.018 – 2.169
TBT Total Blocking Time 0 ms good → no change 0 ms – 0 ms
FCP First Contentful Paint 3.63 s poor ↑ +1974 ms (+119.3%) significant 1.65 s – 3.63 s
Speed Index — ↑ +2051 ms (+40.1%) 5.12 s – 7.17 s
TTFB Time to First Byte — ↓ -49 ms (-7.3%) 622 ms – 671 ms

LCP Subparts LAB Unthrottled

The subparts attribute LCP to your server, resource discovery, download, or rendering. Note that the Lab LCP shown above is a simulated throttled estimate.

resource load delay 1.31 s
element render delay 924 ms
time to first byte 96 ms
resource load duration 18 ms

Page weight

Metric Value Change / range Trend
Page Weight 834 kB ↑ +101.5 kB (+14.2%) 606 kB – 11.18 MB
Requests 37 → no change 21 – 137
Third-party Weight 127 kB ↑ +109.9 kB (+765.6%) significant 14.3 kB – 127 kB
Third-party CPU 48 ms ↑ +35 ms (+275.6%) 13 ms – 51 ms
Unused JS 56.3 kB ↑ +54.9 kB 0 B – 56.3 kB
Unused CSS 0 B → no change 0 B – 0 B

By resource type

Type Transfer Share Size Requests
image 79.4% 662 kB 17
script 16.8% 140 kB 10
document 2.1% 17.4 kB 3
font 0.8% 6.9 kB 1
stylesheet 0.7% 5.9 kB 2
other 0.2% 1.5 kB 3
Total 834 kB 37

Third parties 3 entities

Entity Transfer Size Main thread Simulated
51.la script 113 kB 9 ms
Baidu Analytics 12.2 kB 27 ms
bmip03.com 2.2 kB 11 ms
Total 127 kB 48 ms

Page health

Metric Value Change / range Trend
Main Thread Work 1.29 s ↑ +690 ms (+114.7%) 602 ms – 1.72 s
Long Tasks 1 → no change 1 – 1
DOM Elements 432 → no change 432 – 432
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 35 → no change 35 – 594
A11y Failures 6 → no change 6 – 6
A11y Failing Nodes 38 → no change 38 – 38

Main thread work

Task Time Share Duration Simulated
style layout 37% 473 ms
other 28% 362 ms
script evaluation 19% 244 ms
paint composite render 10% 129 ms
garbage collection 3% 37 ms
parse HTML 2% 28 ms
script parse compile 1% 19 ms
Total 1.29 s

Axe violations axe-core 4.13.0, full rule set

35 violating nodes across 5 rules, 797 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 28 nodes
    Offending elements (5 of 28)
    1. .episode-item.click-feedback:nth-child(1) > .ep-date
      <span class="ep-date">2024-01</span>
    2. .episode-item.click-feedback:nth-child(2) > .ep-date
      <span class="ep-date">2024-01</span>
    3. .episode-item.click-feedback:nth-child(3) > .ep-date
      <span class="ep-date">2024-01</span>
    4. .episode-item.click-feedback:nth-child(4) > .ep-date
      <span class="ep-date">2024-01</span>
    5. .episode-item.click-feedback:nth-child(5) > .ep-date
      <span class="ep-date">2024-02</span>
  • critical button-name — Buttons must have discernible text 3 nodes
    Offending elements
    1. button[data-index="0"]
      <button class="" data-index="0"></button>
    2. button[data-index="1"]
      <button data-index="1" class=""></button>
    3. #bannerDots > .active[data-index="2"]
      <button data-index="2" class="active"></button>
  • moderate meta-viewport — Zooming and scaling must not be disabled 2 nodes
    Offending elements
    1. meta[name="viewport"]:nth-child(3)
      <meta name="viewport" content="width=device-width,initial-scale=1.0,maximum-scale=1.0,user-scalable=0">
    2. meta[name="viewport"]:nth-child(5)
      <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.5, user-scalable=yes">
  • serious frame-title — Frames must have an accessible name 1 node
    Offending element
    1. #warpperId
      <iframe width="100%" height="100%" id="warpperId" src="https://bdx4.t7gpdo9vhx.cc"> </iframe>
  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node
    Offending element
    1. .footer-bottom > a[href$="#banner"]
      <a href="#banner">回到顶部</a>

Accessibility failures 6 of 25 audits

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 28 nodes
  • button-name — Buttons do not have an accessible name 3 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 3 nodes
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 2 nodes
  • frame-title — `<frame>` or `<iframe>` elements do not have a title 1 node
  • link-in-text-block — Links rely on color to be distinguishable. 1 node

Best Practices failures 5 of 19 audits

  • deprecations — Uses deprecated APIs 1 item
  • third-party-cookies — Uses third-party cookies 1 item
  • doctype — Page lacks the HTML doctype, thus triggering quirks-mode
  • errors-in-console — Browser errors were logged to the console 2 items
  • inspector-issues — Issues were logged in the `Issues` panel in Chrome Devtools 1 item

SEO failures 1 of 8 audits

  • meta-description — Document does not have a meta description

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 2 console errors

Measurement log

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 6, 2026, 12:51 PM UTC 4.31 s 0.018 0 ms 834 kB 3/3 — 2,430 -2% 142.7s Wayback
Sep 29, 2026, 4:55 AM UTC 3.04 s 0.018 0 ms 730 kB 3/3 — 2,897 +17% 37.9s Wayback
Sep 22, 2026, 3:31 AM UTC 57 3.54 s 2.169 0 ms 11.18 MB 3/3 ±25 2,912 +17% 80s Wayback
Sep 14, 2026, 9:35 PM UTC 59 3.84 s 0.964 0 ms 7.90 MB 3/3 ±28 2,326 -6% 53.9s Wayback
Sep 7, 2026, 7:04 PM UTC 63 2.64 s 2.142 0 ms 10.73 MB 3/3 ±14 2,461 -1% 38.2s Wayback
Aug 31, 2026, 6:06 PM UTC 2.48 s 0.018 0 ms 606 kB 3/3 — 2,488 0% 29.9s Wayback
Aug 26, 2026, 10:34 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.3s
Aug 25, 2026, 9:42 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 15.9s
Aug 24, 2026, 9:05 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16s
Aug 23, 2026, 8:36 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 15.9s
Aug 22, 2026, 4:22 PM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 15.9s
Aug 22, 2026, 7:32 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16s
Aug 22, 2026, 1:11 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16s
Aug 21, 2026, 5:10 PM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 15.8s
Aug 21, 2026, 9:43 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.3s

Embed this score

Use this web component to show tottattoo.com's scores on any website, updated whenever this instance re-measures. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://tottattoo.com/"></speedlify2-score>