Remove Unused CSS and JavaScript

How to optimize clinicacedron.com

WordPress SiteScore: 68/100Analyzed March 2026Re-analyze this site

Remove Unused CSS and JavaScript

High Impact+18 points estimated

Why It Matters

Unused code accounts for 183 KiB of wasted resources, delaying FCP by 300ms and blocking rendering.

How to Fix

Use Asset CleanUp Pro to disable unused Elementor widgets and FontAwesome icons. Remove redundant font-awesome CSS files (3 versions detected). Implement tree shaking for JavaScript modules or use WP Rocket's unused CSS removal feature.

0Needs Improvement

What This Score Means

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

5.9s
Poor

Good: < 2.5s

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

INP

Interaction to Next Paint

151ms
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 WordPress site has poor performance with a score of 68/100, primarily due to inefficient resource loading and bloated CSS/JavaScript files. The biggest problem is the excessive network dependency chain that takes over 4 seconds to complete, along with 36KB of unused CSS (mostly from Font Awesome libraries) that's blocking the initial page render. The site is also loading 145KB of unused JavaScript from Google Analytics and other scripts, while multiple duplicate Font Awesome files are being loaded unnecessarily. Consolidating and minifying CSS files, removing unused code, and optimizing the resource loading sequence could improve the score by 15-20 points and significantly reduce the 5.9-second load time.

Other Optimization Recommendations

Fix Critical Rendering Path Issues

High Impact+15 points estimated

Why It Matters:

Render-blocking resources delay FCP by 4.3 seconds, severely impacting user experience and Core Web Vitals.

How to Fix:

Defer non-critical Elementor CSS files using rel='preload' with onload callback. Move frontend-modules.min.js to load after HTML parsing. Inline critical CSS for above-the-fold content using Critical CSS plugins like WP Rocket or Autoptimize.

Optimize Images and Font Loading

Medium Impact+8 points estimated

Why It Matters:

Oversized images waste 65 KiB and missing font-display causes 310ms rendering delays.

How to Fix:

Resize the logo image from 768x622 to actual display size (128x103) and convert to WebP format. Add font-display: swap to FontAwesome fonts in Elementor settings. Use fetchpriority='high' on the LCP element which appears to be a video background section.

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 WordPress Speed Tests

WordPress Performance Resources

Frequently Asked Questions