Performance
· 26 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.Performance-focused optimization plan with CWV assessment, top offenders, and time estimates
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
957 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.57 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
333 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.115
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.12 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
5.97 s
Page Load Progression
DThird-Party ImpactAction98% third-party, 0 ms blockingFIX
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CImage OptimizationAction22 images, 0 KB saveableREVIEW
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
CJS Execution CostAction1661ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://porncrash.net/ | 448ms | 27ms | 2ms | 1st |
| Unattributable | 387ms | 96ms | 0ms | 1st |
| https://www.googletagmanager.com/gtag/js?id=G-P3LGLF88WZ&cx=c>m=4e67m0 | 340ms | 257ms | 74ms | 3rd |
| https://scripts.clarity.ms/0.8.67/clarity.js | 244ms | 213ms | 12ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=UA-130225113-1 | 242ms | 174ms | 66ms | 3rd |
BJS Bundles5 scripts, 137 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtag/js?id=G-P3LGLF88WZ&cx=c>m=4e67m0 | 156 KB | 69 KB (44%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=UA-130225113-1 | 117 KB | 68 KB (58%) | ✓ | 3rd |
| https://porncrash.net/js/request.js?version=1.0.29 | 1 KB | — | ✓ | 1st |
| https://www.clarity.ms/tag/4quw06rlpl | 1 KB | — | ✓ | 3rd |
| https://scripts.clarity.ms/0.8.67/clarity.js | 25 KB | — | ✓ | 3rd |
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
BHTTP/3 (QUIC)HTTP/3 not advertisedREVIEW
BCompression AlgorithmMain response uses gzip; brotli would be ~20% smallerREVIEW
BMain HTML Cache-ControlNo Cache-Control header on main HTML responseREVIEW
BServer-Timing ObservabilityNo Server-Timing header foundREVIEW
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
APage Weight Budget729 KB transferred, 35 requestsPASS
A+Text CompressionAll text resources are compressedPASS
A+Font LoadingNo web fonts (system fonts)PASS
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
A+LCP Image PreloadLCP preload audit not availablePASS
A+Server Response Intelligence2 server-response signal(s) detectedPASS
APage Weight Inventory35 resources · 729 KB · 137 KB savings availablePASS
~137.3 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 35 resources | 728.8 KiB | ||||||
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
A+JavaScript BlockingNo render-blocking JS or document.write usage detectedPASS
A+CSS Performance DepthNo CSS performance depth issues detectedPASS
Network Waterfall35 requests over 1650msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
Google Tag Manager www.googletagmanager.com | Tag Manager | 340ms | 156 KB | 44% | $5/mo | Costly |
Microsoft Clarity scripts.clarity.ms | Session Replay | 244ms | 25 KB | — | $3/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 242ms | 117 KB | 58% | $3/mo | Costly |
These scripts may cost more than they're worth
- Google Tag Manager adds 340ms and costs ~$5/month
- Microsoft Clarity adds 244ms and costs ~$3/month
- Google Tag Manager adds 242ms and costs ~$3/month
50% of JavaScript execution time comes from third-party scripts.
Third-party scripts (analytics, ads, social, A/B testing) often dominate execution time — every one is a perf-and-privacy tax.
Learn more ▾ ▴
Each third-party script is a black box: you don't control when it loads, what it executes, or how much it grows. They often account for a major share of total blocking time on average sites (HTTP Archive's Web Almanac documents the trend). Audit which ones you actually need, defer the rest, and use facade patterns (lite-youtube, lite-vimeo) for embedded media.
Source: web.dev / HTTP Archive Web Almanac
Google Tag Manager takes 340ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Microsoft Clarity takes 244ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Google Tag Manager takes 242ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
58% of Google Tag Manager's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
Real-User Performance (CrUX)Field metrics from the Chrome User Experience ReportINFO
Chrome User Experience (CrUX)
Real-user metrics from the Chrome UX Report (2026-06-26 — 2026-07-23)
LCP (p75)
910 ms
96% good
INP (p75)
75 ms
98% good
CLS (p75)
0.000
89% good
FCP (p75)
657 ms
TTFB (p75)
740 ms