Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize zeno.pm
Render-blocking CSS and JavaScript delay First Contentful Paint by 1.45 seconds and prevent users from seeing content.
Inline critical CSS directly in the HTML head section. Defer jQuery loading using async/defer attributes or load it after page content. Use WP Rocket or Autoptimize plugin to automatically optimize CSS delivery and combine files.
A score of 92 falls in the "Good" 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 strong performance with a score of 92/100, but suffers from poor interactivity with a Time to Interactive of 7.2 seconds. The biggest issue is render-blocking resources (jQuery and CSS files) that are delaying the initial page load by an estimated 1.4 seconds. The site is also bloated with an 18MB total payload, largely due to video files, and contains 37KB of unused CSS (93% waste) plus 323KB of unused JavaScript. Quick wins include deferring or inlining critical resources, removing unused code, and adding proper dimensions to images to prevent layout shifts.
Why It Matters:
The hero image has a 1.49 second resource load delay, significantly impacting Largest Contentful Paint performance.
How to Fix:
Add fetchpriority='high' attribute to the hero image (lines.svg). Preload the LCP image using <link rel='preload' as='image'> in the HTML head. Consider using a CDN like Cloudflare or MaxCDN for faster image delivery.
Why It Matters:
93% of CSS (37 KiB) and 323 KiB of JavaScript are unused, wasting bandwidth and slowing page load.
How to Fix:
Install Asset CleanUp or Perfmatters plugin to disable unused WordPress features and scripts. Use PurgeCSS to remove unused CSS rules from your combined stylesheet. Audit Google Tag Manager implementation and remove unnecessary tracking scripts.
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.