LCP
Largest Contentful Paint
26.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused JavaScript Payload
How to optimize www2.telenet.be
Generic SiteScore: 33/100Analyzed January 2026
Reduce Unused JavaScript Payload
High Impact+20 points estimated
Why It Matters
Nearly 4MB of unused JavaScript is consuming network bandwidth and blocking the main thread for over 5 seconds.
How to Fix
Audit all JavaScript dependencies and remove unused libraries. Implement code splitting to load only necessary modules per page. Use tree shaking to eliminate dead code from bundles. Consider replacing heavy Angular Material components with lighter alternatives.
0Poor
What This Score Means
A score of 33 falls in the "Poor" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.
This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.
Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.
Core Web Vitals Analysis
INP
Interaction to Next Paint
261ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.07
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Telenet website has severe performance issues with a critically low score of 33/100. The biggest problem is an extremely slow Speed Index of 13.1 seconds, primarily caused by render-blocking CSS and JavaScript files that prevent content from appearing quickly. The site loads over 5.7MB of resources with massive amounts of unused JavaScript (3.9MB) and CSS (537KB), creating a painfully slow user experience where visitors wait over 26 seconds to see the main content. The most impactful fixes would be removing unused code, deferring non-critical resources, and optimizing the complex network dependency chains that are currently blocking the page from rendering efficiently.
Other Optimization Recommendations
Eliminate Render Blocking Resources
High Impact+25 points estimatedWhy It Matters:
Critical CSS and JavaScript files are blocking page render for 5.9 seconds, severely delaying both FCP and LCP.
How to Fix:
Inline critical CSS directly in the HTML head section. Defer non-critical CSS using media='print' then switching to 'all' on load. Move JavaScript files to load asynchronously or defer execution using async/defer attributes on script tags.
Optimize Network Dependency Chain
High Impact+18 points estimatedWhy It Matters:
Critical resources are loading sequentially in a 7.6-second chain instead of in parallel, creating unnecessary delays.
How to Fix:
Add preconnect hints for external domains like customer-web-foundation-wink-cdn.aem-modules-prod.awsprod.external.telenet.be. Preload critical fonts and CSS files. Move inline JavaScript that triggers resource loading to execute earlier in page load sequence.
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Fix Image Layout Shift Issues
Unsized images are causing 0.4 CLS score and poor visual stability during load.
Reduce Unused JavaScript Payload
645KB of unused JavaScript is wasting 1.6 seconds of load time and blocking LCP.
Eliminate Render-Blocking CSS Resources
Critical CSS files are blocking first paint and delaying LCP by 450ms.
Fix Element Render Delays
The LCP element has a 2.6-second render delay causing the 11.2-second LCP score.
Frequently Asked Questions
Keep Your Site Fast After Optimization
Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites