Reduce Unused JavaScript and CSS

How to optimize esimconnect.diploy.in

Generic SiteScore: 54/100Analyzed February 2026

Reduce Unused JavaScript and CSS

High Impact+15 points estimated

Why It Matters

1.5MB of unused JavaScript and 240KB of unused CSS are unnecessarily increasing page load time.

How to Fix

Implement code splitting to load only necessary JavaScript chunks per route. Use tree shaking to eliminate dead code from bundles. Split CSS by components and load only required styles for each page. Consider lazy loading non-critical features like payment widgets.

0Needs Improvement

What This Score Means

A score of 54 falls in the "Needs Improvement" 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

LCP

Largest Contentful Paint

20.6s
Poor

Good: < 2.5s

Measures how long it takes for the main content to appear on screen

INP

Interaction to Next Paint

113ms
Good

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.00
Good

Good: < 0.1

Measures visual stability - how much content shifts during page load

AI Performance Analysis

This generic website has poor performance with a score of 54/100, indicating significant issues that harm user experience. The biggest problem is extremely slow page rendering, with the Largest Contentful Paint taking 20.6 seconds and Time to Interactive reaching 24.1 seconds - both far exceeding acceptable limits. The site is bloated with a 6.9MB total payload, dominated by oversized images (1.7MB for a single image) and 1.5MB of largely unused JavaScript that's blocking the initial render. The most impactful fixes would be optimizing and properly sizing images, removing or deferring unused JavaScript, and eliminating render-blocking resources, which together could save over 8 seconds of load time and dramatically improve the user experience.

Other Optimization Recommendations

Eliminate Render Blocking Resources

High Impact+25 points estimated

Why It Matters:

Critical CSS and JavaScript files are blocking initial page render, delaying both FCP by 14.3s and LCP by 20.6s.

How to Fix:

Defer non-critical CSS by adding media='print' onload="this.media='all'" to stylesheets. Move Razorpay and PayPal scripts to load asynchronously using async attribute. Inline critical CSS for above-the-fold content directly in HTML head.

Fix Element Render Delay

High Impact+20 points estimated

Why It Matters:

The LCP element (H1 heading) has a massive 10.5 second render delay, indicating JavaScript is blocking content display.

How to Fix:

Remove JavaScript dependencies from hero section rendering by pre-rendering the H1 content in server-side HTML. Eliminate opacity animations or transforms that delay visibility. Move any data fetching for hero content to occur after initial render.

Want to Analyze YOUR Website?

Get AI-powered performance insights with actionable fixes in 30 seconds

More Generic Speed Tests

Generic Performance Resources

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