Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize myworks.software
Unsized images cause layout shifts and oversized images waste 52 KiB of bandwidth affecting LCP.
Add explicit width and height attributes to all images in Elementor widgets and WordPress posts. Use ShortPixel or Smush to automatically resize images to match their display dimensions. Enable responsive images with proper srcset attributes in your WordPress theme.
A score of 66 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This WordPress site has poor performance with a score of 66/100. The biggest problem is excessive unused CSS and JavaScript that's blocking the initial page render, delaying your First Contentful Paint to 3.5 seconds and making the site feel unresponsive for over 23 seconds. The site is loading 501 KiB of unused JavaScript and 25 KiB of unused CSS (especially from Font Awesome libraries that are 99% unused), while render-blocking resources are adding an estimated 2.2 seconds to load times. Cleaning up unused code, properly minifying assets, and deferring non-critical scripts could potentially improve your performance score by 25+ points and dramatically speed up the user experience.
Why It Matters:
501 KiB of unused JavaScript and 25 KiB of unused CSS are blocking rendering and delaying FCP by 150ms.
How to Fix:
Use Asset CleanUp Pro to disable unused FontAwesome CSS files on pages that don't need icons. Remove or defer Google Tag Manager and Facebook Pixel scripts until after page load. Audit Elementor widgets and remove unused ones to reduce bundle size.
Why It Matters:
Custom fonts are causing 100ms delay to FCP and creating invisible text during load.
How to Fix:
Add font-display: swap to your DMSans font declarations in WordPress Customizer or theme files. Preload the most critical font weights using <link rel='preload' as='font'> in your theme's header.php. Consider using system fonts as fallbacks with similar metrics.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
Custom fonts block text rendering for 880ms, delaying FCP and creating poor user experience.
LCP element has 7.5 second resource load delay because it's not discoverable from initial HTML.
Unused assets waste 130KB of bandwidth and delay FCP by 1.05 seconds, severely impacting Core Web Vitals.
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
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.