Reduce Unused JavaScript Execution

How to optimize myworks.software

WordPress SiteScore: 64/100Analyzed December 2025

Reduce Unused JavaScript Execution

High Impact+18 points estimated

Why It Matters

178 KiB of unused JavaScript is delaying LCP by 950ms, particularly from Google Tag Manager scripts.

How to Fix

Use Google Tag Manager's built-in triggers to load tracking scripts only when needed. Implement WP Rocket's JavaScript optimization to defer Google Analytics and GTM scripts. Remove or replace heavy tracking scripts with lighter alternatives like Plausible Analytics.

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

8.2s
Poor

Good: < 2.5s

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

INP

Interaction to Next Paint

146ms
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 issues with a score of 64/100, struggling particularly with slow loading times that hurt user experience. The biggest problem is render-blocking CSS files that are delaying the initial page display by 2.4 seconds, combined with an extremely slow Largest Contentful Paint of 8.2 seconds. The site is also loading 178 KB of unused JavaScript from Google Analytics and Tag Manager scripts, which could be optimized or deferred. Fixing the render-blocking resources, optimizing font loading with proper font-display settings, and cleaning up unused code could potentially improve the score by 15-20 points and dramatically reduce load times.

Other Optimization Recommendations

Eliminate Render-Blocking CSS Resources

High Impact+25 points estimated

Why It Matters:

Render-blocking CSS is delaying First Contentful Paint by 2.4 seconds, severely impacting user experience.

How to Fix:

Use WP Rocket or Autoptimize to inline critical CSS for above-the-fold content. Defer non-critical CSS like Font Awesome and Elementor widget styles using media='print' onload technique. Remove unused CSS from FontAwesome (99% unused) and minify remaining stylesheets.

Optimize Font Loading Strategy

Medium Impact+8 points estimated

Why It Matters:

Custom fonts are causing 30ms delay and potential layout shifts during font swap.

How to Fix:

Add font-display: swap to your DM Sans font declarations in Elementor. Preload critical font files (DMSans-Medium.ttf, DMSans-Bold.ttf) using WordPress wp_head hook. Use font metric overrides in CSS to prevent layout shifts during font loading.

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

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