Remove Unused JavaScript Code

How to optimize sbmtm.in

Generic SiteScore: 94/100Analyzed May 2026Re-analyze this site

Remove Unused JavaScript Code

Medium Impact+10 points estimated

Why It Matters

Nearly 50% of your main JavaScript bundle (43KB) goes unused, slowing down parse and execution time.

How to Fix

Use webpack-bundle-analyzer or similar tools to identify unused code in index-DTaN5bNW.js. Implement code splitting to load only necessary JavaScript for the contact page. Consider lazy loading non-critical features that aren't immediately needed.

0Good

What This Score Means

A score of 94 falls in the "Good" 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

2.4s
Good

Good: < 2.5s

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

INP

Interaction to Next Paint

16ms
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 website has good performance with a score of 94/100, but there's significant room for improvement in loading speed. The biggest issue is render-blocking CSS and font files that are delaying the first content from appearing, causing a slow First Contentful Paint of 2.4 seconds and potentially saving over 1 second if fixed. The site is also loading nearly 43KB of unused JavaScript code that could be removed or deferred to reduce bandwidth waste. To boost performance further, prioritize inlining critical CSS, using font-display: swap for Google Fonts, and removing or code-splitting the unused JavaScript portions.

Other Optimization Recommendations

Eliminate Render Blocking Resources

High Impact+25 points estimated

Why It Matters:

CSS and font files are blocking initial page render, delaying both FCP and LCP by 1,050ms.

How to Fix:

Inline critical CSS for above-the-fold content directly in the HTML head. Add preload hints for the Google Fonts CSS file using <link rel='preload' href='https://fonts.googleapis.com/css2...' as='style'>. Use font-display: swap in your CSS to prevent invisible text during font load.

Extend Asset Cache Lifetimes

Low Impact+3 points estimated

Why It Matters:

Short cache duration forces repeat visitors to re-download 9KB of static assets unnecessarily.

How to Fix:

Configure your server to set longer cache headers for static assets (CSS/JS files). Add versioning or cache-busting query parameters to your build process. Set cache-control headers to at least 1 year for immutable assets while using ETags for validation.

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

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