Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize de.treated.com
LCP takes 9.3 seconds, which is severely impacting user experience and Core Web Vitals scores.
Optimize the largest contentful paint element by compressing hero images and implementing proper lazy loading. Use WordPress plugins like WP Rocket to enable critical CSS inlining. Preload the LCP image using <link rel='preload'> in your theme's header.php.
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 significant performance issues with a score of 64/100. The biggest problem is an extremely slow Largest Contentful Paint of 9.3 seconds, which means visitors wait far too long to see meaningful content. The main culprit is excessive JavaScript processing that blocks the main thread for 2.4 seconds, primarily from unminified scripts and unused code that totals 249 KB of wasted downloads. Additionally, poor caching strategies are forcing repeat downloads of resources that should be stored locally. Minifying JavaScript, removing unused code, and implementing proper caching could dramatically improve loading speeds and boost your performance score by 30+ points.
Why It Matters:
Main thread is blocked for 2.4 seconds by script evaluation, preventing user interactions and delaying Time to Interactive.
How to Fix:
Remove unused JavaScript (249 KiB detected) using Asset CleanUp Pro plugin. Minify remaining JavaScript files to save 16 KiB. Defer non-critical scripts like Google Tag Manager and cookie consent until after page load using wp_enqueue_script with defer attribute.
Why It Matters:
JavaScript is causing 68ms of forced reflows by querying geometric properties after DOM changes, degrading rendering performance.
How to Fix:
Review custom WordPress theme JavaScript for DOM queries after style changes. Batch DOM reads and writes separately. Use WordPress's jQuery properly by avoiding synchronous layout calculations in loops or event handlers.
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
The 664KB hero background image is delaying LCP by 1.6 seconds as it's not optimized or prioritized.
Over 2.4MB of unused JavaScript and 411KB of unused CSS are slowing LCP by 7+ seconds.
Critical CSS and JavaScript files are blocking initial page render, delaying FCP by 4.4 seconds.
Short cache durations force unnecessary re-downloads on repeat visits, slowing LCP by 150ms.