Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize myworks.software
Critical CSS and JavaScript files are blocking first paint by 3.66 seconds, severely impacting user experience.
Use Critical CSS plugin to inline above-the-fold styles. Move custom CSS files to load asynchronously using loadCSS library. Defer Elementor icons and Font Awesome CSS until after initial render.
A score of 39 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 severely poor performance with a score of just 39/100, making it extremely slow for users. The biggest problem is an excessive 15-second delay before the main content appears (Largest Contentful Paint), combined with over 500KB of unused JavaScript code that's unnecessarily downloaded but never used. The site is also loading nearly 4 seconds worth of render-blocking resources that prevent the page from displaying quickly, including poorly optimized CSS and JavaScript files from various WordPress plugins like Elementor. Addressing the unused JavaScript alone could save nearly 2 seconds of load time, while optimizing the render-blocking resources and unused CSS could dramatically improve the user experience and potentially boost the performance score by 40+ points.
Why It Matters:
497 KiB of unused JavaScript and 25 KiB of unused CSS are blocking critical rendering and delaying LCP by 1.9 seconds.
How to Fix:
Install Asset CleanUp Pro to disable unused plugins like HubSpot and Google Analytics on specific pages. Use WP Rocket to combine and minify remaining CSS/JS files. Remove duplicate Segment.io integrations causing 10 KiB waste.
Why It Matters:
Custom fonts are causing 30ms delays and potential layout shifts during text rendering.
How to Fix:
Add font-display: swap to DMSans font files in your theme's CSS. Preload critical fonts using <link rel='preload'> in wp_head. Use font metric overrides to prevent layout shifts during font swapping.
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.