LCP
Largest Contentful Paint
18.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Font and CSS Loading
How to optimize myworks.software
WordPress SiteScore: 44/100Analyzed December 2025
Optimize Font and CSS Loading
Medium Impact+12 points estimated
Why It Matters
Font blocking and massive unused CSS (25KB) are delaying FCP by 3.85 seconds.
How to Fix
Add font-display: swap to all @font-face declarations in your theme. Remove unused Font Awesome CSS from Elementor settings. Use Autoptimize or WP Rocket to inline critical CSS and defer non-critical stylesheets.
0Poor
What This Score Means
A score of 44 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
229ms
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 44/100 and faces severe loading issues. The biggest problem is an extremely slow Largest Contentful Paint of 18 seconds, primarily caused by a massive 3.8-second delay in rendering the main banner image after it loads. The site is also weighed down by 3MB+ of network data, with excessive unused JavaScript (500KB) and CSS (25KB) from plugins like Elementor and tracking scripts. Reducing plugin bloat, optimizing the main banner image, and removing unused code could dramatically improve loading speeds and user experience by 10+ seconds.
Other Optimization Recommendations
Fix Critical Element Render Delay
High Impact+25 points estimatedWhy It Matters:
The LCP element (home banner image) has a massive 3.8 second render delay causing the 18-second LCP.
How to Fix:
Add explicit width='412' and height='241' attributes to the banner image. Ensure the image is preloaded with <link rel='preload' as='image' href='home-banner-pic-1.webp'>. Remove any CSS or JavaScript that might be blocking the image rendering in Elementor.
Reduce Unused JavaScript Payload
High Impact+18 points estimatedWhy It Matters:
500KB of unused JavaScript is blocking the main thread and delaying LCP by 1.65 seconds.
How to Fix:
Remove or defer HubSpot chat widget (110KB unused) until user interaction. Optimize Google Tag Manager by removing unused tags and triggers. Use WP Rocket's 'Delay JavaScript Execution' feature for non-critical scripts like analytics.
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