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 delays LCP by 2.25 seconds and blocks user interactions.
Remove or defer HubSpot chat widget (110 KiB unused) until user interaction. Optimize Google Analytics by switching to gtag and removing duplicate GTM implementations. Use WP Asset CleanUp to disable unused Elementor modules on specific pages.
A score of 36 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 severe performance issues with a critically low score of 36/100. The biggest problem is excessive JavaScript execution taking 2.8 seconds, combined with massive render-blocking resources that delay page rendering by 2.7 seconds - causing your Largest Contentful Paint to suffer at 13.9 seconds (should be under 2.5s). The site is loading 497 KiB of unused JavaScript and has poor caching policies, creating a sluggish user experience. Reducing JavaScript bloat, eliminating render-blocking resources, and implementing proper caching could dramatically improve your score by 40+ points and make your site significantly faster for users.
Why It Matters:
Render blocking CSS and JavaScript delays FCP by 2.65 seconds, preventing users from seeing content.
How to Fix:
Install WP Rocket to defer non-critical CSS and JavaScript. Remove unused Font Awesome icons (99% unused) by using specific icon classes only. Inline critical CSS for above-the-fold content using plugins like Critical CSS.
Why It Matters:
Long dependency chains create a 2.47 second waterfall that delays page rendering completion.
How to Fix:
Add preconnect links for external domains: status.myworks.software, embedsocial.com, and data.gosquared.com. Bundle and minify multiple small CSS/JS files from Elementor plugins. Use WP Rocket's file optimization to reduce HTTP requests from 50+ to under 10.
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.