Performance
· 15 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.
1.12 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.37 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
56 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.010
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.46 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.
2.25 s
Page Load Progression
DPage Weight BudgetAction2.3 MB transferred, 161 requestsFIX
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
Subset fonts to include only used characters, or switch to system font stacks.
Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).
Source: web.dev font loading
Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Source: web.dev
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
DJS BundlesAction59 scripts, 495 KB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://t.contentsquare.net/uxa/7db1afeaecaa7.js?2026-3-22 | 156 KB | 111 KB (72%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-9ETQKR539E&cx=c>m=4e64k1 | 174 KB | 67 KB (38%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=AW-11113079898&cx=c>m=4e64k1 | 145 KB | 64 KB (44%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?id=AW-1064956115&cx=c>m=4e64k1 | 146 KB | 64 KB (44%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-WC3GM72 | 121 KB | 62 KB (51%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtag/js?2026-3-22 | 85 KB | 53 KB (63%) | ✓ | 3rd |
| https://connect.facebook.net/en_US/fbevents.js | 97 KB | 47 KB (49%) | ✓ | 3rd |
| https://www.easeus.com/default/js/sensorsdata/sensors.min.nogif.js?2026-3-22 | 49 KB | 26 KB (53%) | ✓ | 3rd |
| https://www.easeus.com/default/js/sensorsdata/abtest.min.js?2026-3-22 | 15 KB | — | ✓ | 3rd |
| https://cdn.tangoo.it/aud/clientjs/10072.js? | 3 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
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
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
FPage Weight InventoryAction161 resources · 2.3 MB · 495 KB savings availableFIX
~494.6 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 161 resources | 2.3 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CImage OptimizationAction58 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
CJS Execution CostAction1071ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.easeus.com/default/js/globle.js?11 | 344ms | 122ms | 1ms | 3rd |
| https://www.easeus.com/ | 223ms | 1ms | 0ms | 3rd |
| Unattributable | 184ms | 8ms | 0ms | 3rd |
| https://webtrafficsource.com/track/code.js | 166ms | 160ms | 0ms | 3rd |
| https://www.easeus.com/default/js/other.js?11 | 79ms | 63ms | 4ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=AW-11113079898&cx=c>m=4e64k1 | 74ms | 67ms | 7ms | 3rd |
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+Font Loading4 fonts (229 KB)PASS
Web fonts
4
229 KB total
Render-blocking
0
of 4
Dominant font-display
swap
Most common across fonts
Font loading timeline
- Convert to woff2 for ~30% smaller file size
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
Optimization checklist
- Preload critical fonts (priority=high)
- Use woff2 format for all fonts
- Set font-display to swap, optional, or fallback
- Subset large fonts (≤100 KB each)
Fixing the unchecked items could save ~115 KB and ~230 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
Network Waterfall161 requests over 4971msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.easeus.com www.easeus.com | Other | 344ms | 12 KB | — | €2/mo | Costly |
www.easeus.com www.easeus.com | Other | 223ms | 22 KB | — | €1/mo | Costly |
Unattributable Unattributable | Other | 184ms | 0 KB | — | €1/mo | Optional |
webtrafficsource.com webtrafficsource.com | Other | 166ms | 21 KB | — | €1/mo | Optional |
www.easeus.com www.easeus.com | Other | 79ms | 34 KB | — | €0/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 74ms | 145 KB | 44% | €0/mo | Optional |
These scripts may cost more than they're worth
- www.easeus.com adds 344ms and costs ~€2/month
- www.easeus.com adds 223ms and costs ~€1/month
100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
When third-party JS execution time exceeds your own, performance gains from frontend work are capped by code you don't own.
Learn more ▾ ▴
Every millisecond of third-party JS competes with your own for main-thread time. If their share is bigger than yours, optimization on your code base barely moves the needle. Audit, defer, or remove third-parties before further frontend optimization. Use Lighthouse's third-party audit to identify the worst offenders.
Source: web.dev
www.easeus.com takes 344ms 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
www.easeus.com takes 223ms 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