Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize myworks.software
Render-blocking CSS delays First Contentful Paint by 3.4 seconds, preventing users from seeing any content.
Use Autoptimize or WP Rocket to inline critical CSS and defer non-critical stylesheets. Remove unused FontAwesome CSS (99% unused) and replace with icon fonts or SVGs. Combine multiple custom CSS files into a single optimized file.
A score of 38 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 score of just 38/100. The biggest problem is excessive JavaScript execution time (2.2 seconds), which is blocking the main thread and making the site extremely slow to become interactive - taking a staggering 24.2 seconds. The site is loading massive amounts of unused JavaScript (496 KiB wasted) from Google Analytics, HubSpot chat, and various WordPress plugins, while also suffering from render-blocking CSS files that delay initial page rendering by 3.4 seconds. Reducing JavaScript payloads, minifying code, and deferring non-critical scripts could dramatically improve performance and cut loading times by more than half.
Why It Matters:
JavaScript execution takes 2.2 seconds and blocks the main thread for 4.0 seconds, severely delaying user interactions and causing a TBT of 760ms.
How to Fix:
Remove or defer the EmbedSocial widget that's consuming 299ms execution time. Use WP Rocket to defer jQuery and non-critical scripts until after page load. Consider removing unused plugins like JetWidgets that add significant JS overhead.
Why It Matters:
Custom fonts without font-display cause 105ms delay and contribute to layout shifts affecting user experience.
How to Fix:
Add font-display: swap to all @font-face declarations in your theme's CSS. Preload critical fonts (DMSans-Bold.ttf, DMSans-Medium.ttf) using <link rel='preload'> in your WordPress theme's header.php. Consider using system fonts as fallbacks to reduce layout shift.
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.