Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize myworks.software
178 KiB of unused JavaScript is delaying LCP by 950ms, particularly from Google Tag Manager scripts.
Use Google Tag Manager's built-in triggers to load tracking scripts only when needed. Implement WP Rocket's JavaScript optimization to defer Google Analytics and GTM scripts. Remove or replace heavy tracking scripts with lighter alternatives like Plausible Analytics.
A score of 64 falls in the "Needs Improvement" 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 issues with a score of 64/100, struggling particularly with slow loading times that hurt user experience. The biggest problem is render-blocking CSS files that are delaying the initial page display by 2.4 seconds, combined with an extremely slow Largest Contentful Paint of 8.2 seconds. The site is also loading 178 KB of unused JavaScript from Google Analytics and Tag Manager scripts, which could be optimized or deferred. Fixing the render-blocking resources, optimizing font loading with proper font-display settings, and cleaning up unused code could potentially improve the score by 15-20 points and dramatically reduce load times.
Why It Matters:
Render-blocking CSS is delaying First Contentful Paint by 2.4 seconds, severely impacting user experience.
How to Fix:
Use WP Rocket or Autoptimize to inline critical CSS for above-the-fold content. Defer non-critical CSS like Font Awesome and Elementor widget styles using media='print' onload technique. Remove unused CSS from FontAwesome (99% unused) and minify remaining stylesheets.
Why It Matters:
Custom fonts are causing 30ms delay and potential layout shifts during font swap.
How to Fix:
Add font-display: swap to your DM Sans font declarations in Elementor. Preload critical font files (DMSans-Medium.ttf, DMSans-Bold.ttf) using WordPress wp_head hook. Use font metric overrides in CSS to prevent layout shifts during font loading.
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.