Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize myworks.software
497 KiB of unused JavaScript is blocking your page load and delaying LCP by 2.1 seconds.
Remove or defer non-essential plugins like HubSpot chat widget and unused Google Tag Manager scripts. Use WP Rocket's 'Remove Unused CSS/JS' feature. Consider replacing heavy tracking scripts with lighter alternatives like Google Analytics 4.
A score of 45 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 critically low score of 45/100. The biggest problem is excessive unused JavaScript that's wasting nearly 500 KiB of data and delaying page interactivity by over 2 seconds, with major culprits being HubSpot chat widgets and Google Tag Manager scripts. The site takes an alarming 17 seconds for the largest content to appear and 23 seconds to become fully interactive, which will frustrate users and hurt search rankings. Removing unused JavaScript, optimizing third-party scripts, and addressing render-blocking resources could dramatically improve performance by 3-4 seconds and boost the score by 30+ points.
Why It Matters:
jQuery and CSS files are blocking initial page render for 3.45 seconds, significantly delaying First Contentful Paint.
How to Fix:
Move jQuery to load asynchronously using WordPress's wp_enqueue_script with defer attribute. Inline critical CSS for above-the-fold content. Use WP Rocket's 'Optimize CSS Delivery' to defer non-critical stylesheets.
Why It Matters:
Custom fonts are causing 50ms delays and potential layout shifts during text rendering.
How to Fix:
Add font-display: swap to your DM Sans font declarations in WordPress Customizer. Preload critical fonts using <link rel='preload'> in your theme's header.php. Consider using system fonts as fallbacks with similar metrics to reduce CLS.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
52KB of unused CSS and 74KB of unused JavaScript increase page weight and slow down parsing without providing value.
The header logo is 51KB larger than needed and wastes bandwidth while potentially delaying LCP.
Web fonts cause significant layout shifts (CLS: 0.139) and delay content rendering, directly impacting user experience.
84% of your CSS (52KB) and 66% of Divi JavaScript (74KB) is unused, slowing down page load times.