Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize myworks.software
JavaScript execution is blocking the main thread for 3.1 seconds, causing a 22.9 second Time to Interactive.
Remove unused JavaScript from Google Tag Manager and HubSpot visitor tracking (500KB+ waste detected). Use Asset CleanUp Pro to conditionally load Elementor scripts only on pages that need them. Defer third-party scripts until user interaction.
A score of 47 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 47/100. The biggest problem is excessive JavaScript blocking the page, causing an extremely slow First Contentful Paint of 8.1 seconds and making the page unusable for nearly 23 seconds. The site is loading too much unused JavaScript (500KB can be removed), has render-blocking CSS files, and suffers from inefficient caching that wastes 422KB of data. Reducing JavaScript payloads, deferring non-critical scripts, and implementing proper caching could improve the score by 30+ points and dramatically enhance user experience.
Why It Matters:
Critical CSS and JavaScript files are blocking page rendering for 3.5 seconds, severely delaying First Contentful Paint.
How to Fix:
Use WP Rocket or Autoptimize to defer non-critical CSS and JavaScript. Inline critical CSS for above-the-fold content. Move FontAwesome and Elementor CSS to load asynchronously since they're blocking render with minimal usage.
Why It Matters:
Custom fonts are causing layout shifts and blocking text rendering, adding 30ms to First Contentful Paint.
How to Fix:
Add font-display: swap to your DMSans font declarations in WordPress Customizer. Preload critical font files (DMSans-Medium.ttf and DMSans-Bold.ttf) using <link rel='preload'> in your theme's header.php. Consider using font metric overrides to prevent layout shifts.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
Web fonts cause 255ms delay and layout shifts, blocking text rendering and hurting Core Web Vitals.
1,307 KiB of unused JavaScript blocks rendering for 7.6 seconds, dramatically slowing LCP and user interactions.
Images without dimensions cause 0.226 CLS score, severely impacting user experience as content jumps during loading.
Poor caching wastes 423KB on repeat visits and delays LCP by 1.1 seconds for returning users.
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.