Remove Unused JavaScript Code

How to optimize dezifoster.com

Generic SiteScore: 64/100Analyzed March 2026Re-analyze this site

Remove Unused JavaScript Code

High Impact+10 points estimated

Why It Matters

96KB of unused JavaScript delays LCP by 450ms and blocks page interactivity.

How to Fix

Defer Google Analytics loading until after page load using gtag's config with send_page_view: false. Replace full Swiper bundle with custom build containing only needed modules. Minify all JavaScript files including Bootstrap, Swiper, and Isotope libraries to save additional 47KB.

0Needs Improvement

What This Score Means

A score of 64 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

6.5s
Poor

Good: < 2.5s

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

INP

Interaction to Next Paint

69ms
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 poor performance issues with a score of 64/100, primarily caused by an extremely slow Largest Contentful Paint of 6.5 seconds - nearly triple the recommended threshold. The biggest problems are render-blocking CSS that delays initial page display by 300ms, along with 96KB of unused JavaScript and 70KB of unused CSS that are unnecessarily slowing down the site. Additionally, images are poorly optimized and oversized, wasting 108KB of bandwidth, while unminified JavaScript files add another 46KB of bloat. Addressing these issues by optimizing the CSS delivery, removing unused code, and properly sizing/compressing images could dramatically improve the performance score and cut loading times in half.

Other Optimization Recommendations

Eliminate Render Blocking CSS

High Impact+12 points estimated

Why It Matters:

The main CSS file blocks rendering for 2.2 seconds, delaying both FCP and LCP by 300ms.

How to Fix:

Split styles.pure.css into critical above-the-fold CSS (inline in <head>) and non-critical CSS (load with media='print' then switch to 'all'). Use tools like Critical or PurgeCSS to identify critical styles. Remove 90% unused CSS from Font Awesome by using only required icons.

Optimize Image Delivery Performance

Medium Impact+8 points estimated

Why It Matters:

Poor image optimization wastes 108KB bandwidth and delays LCP by 150ms.

How to Fix:

Compress the hero banner image more aggressively while maintaining quality. Serve responsive images using srcset attribute for different screen sizes. Add explicit width and height attributes to all images to prevent layout shifts. Convert remaining JPG images to WebP format.

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