Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize myworks.software
Your hero image is 64% larger than needed and lacks proper dimensions, causing layout shifts.
Add explicit width='412' height='241' attributes to your hero image. Use WordPress responsive image srcset to serve appropriately sized images. Install ShortPixel to automatically generate and serve optimized image sizes.
A score of 42 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.
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 42/100, indicating significant loading issues that will frustrate users. The biggest problem is excessive unused JavaScript (498 KiB wasted), particularly from third-party scripts like Facebook tracking, Google Tag Manager, and HubSpot chat widget, which is severely delaying page interactivity with a 17.2-second Largest Contentful Paint. The site is also suffering from render-blocking resources that delay initial paint by over 3 seconds and legacy JavaScript that adds unnecessary overhead. Removing or optimizing these unused scripts, implementing proper caching strategies, and addressing the oversized images could potentially improve the performance score by 30+ points and dramatically reduce loading times from the current 23+ seconds to interactive.
Why It Matters:
498 KiB of unused JavaScript is blocking page load and delaying LCP by 2.4 seconds.
How to Fix:
Use Asset CleanUp Pro to disable HubSpot chat widget on non-essential pages. Defer Google Tag Manager loading until after user interaction. Remove or optimize Elementor unused modules by disabling unnecessary widgets in Elementor settings.
Why It Matters:
Legacy JavaScript polyfills waste 22 KiB and modern browsers don't need these transformations.
How to Fix:
Update your build process to target modern browsers (ES2017+) instead of legacy ones. Configure Facebook Pixel to load the modern version for supported browsers. Use WordPress plugins like WP Rocket to enable modern JavaScript delivery.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
Images lack proper sizing causing layout shifts and use outdated formats, wasting 161 KiB and hurting user experience.
251 KiB of unused JavaScript and 64 KiB of unused CSS waste bandwidth and slow parsing, directly impacting load times.
Render blocking CSS and JavaScript delay LCP and FCP by 2.35 seconds, significantly impacting page load performance.
Google Tag Manager script contains 56KB of unused code, increasing parse time unnecessarily.
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.