Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize icicilombard.com
Layout shifts of 0.214 are causing content to jump during page load, hurting user experience.
Add explicit width and height attributes to all images, especially the WhatsApp and logo images causing shifts. Reserve space for dynamic content with CSS aspect-ratio or min-height properties. Preload the Muli font using <link rel='preload'> to prevent text shifting when the font loads.
A score of 16 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 an extremely poor score of 16/100. The biggest problem is excessive JavaScript execution that blocks the main thread for nearly 8 seconds, causing the page to become interactive only after 32+ seconds - an unacceptable user experience. The site loads over 1.4MB of unused JavaScript code and suffers from major layout shifts (CLS of 0.214) as content loads, particularly affecting mobile users. Immediately reducing JavaScript bundle sizes, removing unused code, and implementing proper image sizing could potentially improve the performance score by 50+ points and dramatically reduce loading times from 30+ seconds to under 5 seconds.
Why It Matters:
1.4MB of unused JavaScript is blocking page rendering and delaying LCP by 7 seconds.
How to Fix:
Implement code splitting in your Angular builds to load only required modules per route. Remove unused polyfills for modern browsers - your ES5 polyfills bundle contains 66KB of unnecessary code. Use webpack-bundle-analyzer to identify and eliminate dead code from your main bundles.
Why It Matters:
7.9 seconds of main thread work creates 2.6 seconds of blocking time, preventing user interactions.
How to Fix:
Split large JavaScript tasks using setTimeout or requestIdleCallback to yield control back to the browser. Move heavy computation to Web Workers where possible. Defer non-critical third-party scripts like Facebook Pixel and analytics until after page load using async/defer attributes.
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.