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.02 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.90 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.39 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.
1.90 s
Page Load Progression
375 ms
750 ms 1.1 s
1.5 s 1.9 s 2.2 s 2.6 s 3.0 sDJS BundlesAction17 scripts, 316 KB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 362 KB | 242 KB (67%) | ✓ | 3rd |
| https://connect.facebook.net/fr_FR/all.js?hash=90dd75f125d41f77fc05070a2cbe36fa | 83 KB | 54 KB (65%) | ✓ | 3rd |
| https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js | 33 KB | 20 KB (62%) | ✓ | 3rd |
| https://www.wampserver.com/wp-includes/js/wp-embed.min.js?ver=5.4.19 | 1 KB | — | ✓ | 1st |
| https://www.wampserver.com/wp-content/themes/wampserver/js/NewYearCard2014/js/jquery.NiceModal.js | 1 KB | — | ✓ | 1st |
| https://www.wampserver.com/wp-content/themes/wampserver/js/jquery.fancybox-1.3.4.pack.js | 5 KB | — | ✓ | 1st |
| https://www.wampserver.com/wp-content/themes/wampserver/js/lancement.js | 1 KB | — | ✓ | 1st |
| https://www.wampserver.com/wp-content/themes/wampserver/js/telechargement.js | 1 KB | — | ✓ | 1st |
| https://www.wampserver.com/wp-content/plugins/sitepress-multilingual-cms/res/js/sitepress.js | 1 KB | — | ✓ | 1st |
| https://www.wampserver.com/wp-content/themes/wampserver/js/NewYearCard2014/lib/jquery-cookie/jquery.cookie.js | 1 KB | — | ✓ | 1st |
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
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BPage Weight Budget1.1 MB transferred, 51 requestsREVIEW
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
BThird-Party Impact42% third-party, 0 ms blockingREVIEW
CImage OptimizationAction21 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
BPage Weight Inventory51 resources · 1.1 MB · 316 KB savings availableREVIEW
~316.1 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 51 resources | 1.1 MiB | ||||||
A+Text CompressionAll text resources are compressedPASS
A+JS Execution Cost125ms total JS executionPASS
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.wampserver.com/ | 65ms | 19ms | 1ms | 1st |
| Unattributable | 60ms | 2ms | 0ms | 3rd |
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+Green HostingWhether the site is served from green-energy infrastructurePASS
Green Hosting
This site is hosted on green energy infrastructure
Provider: OVHcloud
Network Waterfall51 requests over 1353msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
Unattributable Unattributable | Other | 60ms | 0 KB | — | €0/mo | Optional |
48% 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