Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize myworks.software
498 KiB of unused JavaScript and 25 KiB of unused CSS are blocking critical rendering and delaying LCP by 5.2 seconds.
Remove unnecessary WordPress plugins or replace heavy ones with lighter alternatives. Use Asset CleanUp Pro to disable unused scripts/styles per page. Specifically audit HubSpot chat widget, Google Tag Manager, and Font Awesome libraries for actual usage.
A score of 55 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 with a score of 55/100. The biggest problem is excessively slow loading times, with your Largest Contentful Paint taking 5.2 seconds when it should be under 2.5 seconds, and Time to Interactive reaching a painful 24 seconds. The main culprits are massive amounts of unused JavaScript (498 KiB wasted) and CSS (25 KiB wasted), plus render-blocking resources that delay initial page display by over 3 seconds. Cleaning up unused code, optimizing your numerous WordPress plugins and theme files, and implementing proper resource loading strategies could easily improve your score by 30+ points and dramatically speed up your site for users.
Why It Matters:
Critical CSS files are blocking initial page render, delaying First Contentful Paint by 3.1 seconds.
How to Fix:
Install WP Rocket or Autoptimize to inline critical CSS and defer non-essential stylesheets. Move table-addons CSS and sticky module CSS to load after initial render. Combine multiple small CSS files into fewer requests.
Why It Matters:
Custom fonts without proper display settings cause 40ms delays and potential layout shifts affecting user experience.
How to Fix:
Add font-display: swap to all @font-face declarations for DMSans fonts. Preload critical font files using <link rel='preload'> in WordPress header. Consider using system fonts as fallbacks with matching metrics to minimize layout shifts.
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.