Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize echannel.wf.icicilombard.com
Layout shifts (CLS 0.269) create poor user experience as content jumps during page load.
Add explicit width and height attributes to garage.png and benefits_cover_icon.png images. Reserve space for dynamically loaded Angular components with CSS min-height. Preload the Muli font family to prevent text reflow during font loading.
A score of 12 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This ICICI Lombard two-wheeler insurance page has severe performance issues with a critically low score of 12/100. The biggest problem is an enormous amount of unused JavaScript code (1,665 KiB) that's blocking the page from rendering, causing the First Contentful Paint to take a devastating 8.0 seconds and Largest Contentful Paint to reach 32.3 seconds. The site is also loading 253 KiB of unused CSS and has unminified JavaScript files wasting another 68 KiB. Immediately removing or deferring unused JavaScript, minifying all code files, and eliminating render-blocking resources could potentially improve the performance score by 60+ points and reduce load times by over 20 seconds, dramatically improving the user experience for customers trying to get insurance quotes.
Why It Matters:
Unused resources waste 1.9MB bandwidth and delay LCP by 9.6 seconds, severely impacting page load performance.
How to Fix:
Analyze bundle composition and remove unused Angular modules from main-24c25f5dd4dc1cf33c35.js (221KB unused). Split vendor bundles to load only required libraries. Use tree-shaking in your build process to eliminate dead code from motorcommonangular and twangular modules.
Why It Matters:
86KB of legacy polyfills serve unnecessary code to modern browsers, adding 950ms to load time.
How to Fix:
Configure Angular build to target modern browsers (ES2017+) and remove polyfills-es5 bundle. Use differential loading to serve modern JS to capable browsers. Update browserslist configuration to exclude legacy browsers if not required.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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.