LCP
Largest Contentful Paint
15.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Main Thread Work
How to optimize myworks.software
WordPress SiteScore: 47/100Analyzed December 2025
Reduce Main Thread Work
High Impact+20 points estimated
Why It Matters
JavaScript execution is blocking the main thread for 3.1 seconds, causing a 22.9 second Time to Interactive.
How to Fix
Remove unused JavaScript from Google Tag Manager and HubSpot visitor tracking (500KB+ waste detected). Use Asset CleanUp Pro to conditionally load Elementor scripts only on pages that need them. Defer third-party scripts until user interaction.
0Poor
What This Score Means
A score of 47 falls in the "Poor" 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
INP
Interaction to Next Paint
232ms
Needs Improvement
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 47/100. The biggest problem is excessive JavaScript blocking the page, causing an extremely slow First Contentful Paint of 8.1 seconds and making the page unusable for nearly 23 seconds. The site is loading too much unused JavaScript (500KB can be removed), has render-blocking CSS files, and suffers from inefficient caching that wastes 422KB of data. Reducing JavaScript payloads, deferring non-critical scripts, and implementing proper caching could improve the score by 30+ points and dramatically enhance user experience.
Other Optimization Recommendations
Eliminate Render Blocking Resources
High Impact+25 points estimatedWhy It Matters:
Critical CSS and JavaScript files are blocking page rendering for 3.5 seconds, severely delaying First Contentful Paint.
How to Fix:
Use WP Rocket or Autoptimize to defer non-critical CSS and JavaScript. Inline critical CSS for above-the-fold content. Move FontAwesome and Elementor CSS to load asynchronously since they're blocking render with minimal usage.
Optimize Font Loading Strategy
Medium Impact+8 points estimatedWhy It Matters:
Custom fonts are causing layout shifts and blocking text rendering, adding 30ms to First Contentful Paint.
How to Fix:
Add font-display: swap to your DMSans font declarations in WordPress Customizer. Preload critical font files (DMSans-Medium.ttf and DMSans-Bold.ttf) using <link rel='preload'> in your theme's header.php. Consider using font metric overrides to prevent layout shifts.
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More WordPress Speed Tests
WordPress Performance Resources
Fix Font Display Strategy
Custom fonts block text rendering for 880ms, delaying FCP and creating poor user experience.
Optimize LCP Element Discovery
LCP element has 7.5 second resource load delay because it's not discoverable from initial HTML.
Remove Unused CSS and JavaScript
Unused assets waste 130KB of bandwidth and delay FCP by 1.05 seconds, severely impacting Core Web Vitals.
Eliminate Render Blocking CSS Files
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
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