LCP
Largest Contentful Paint
5.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking Resources
How to optimize mooninvoice.com
Eliminate Render Blocking Resources
High Impact+25 points estimated
Why It Matters
CSS and JavaScript files are blocking initial page render, delaying FCP by 650ms and contributing to the poor 2.7s FCP score.
How to Fix
Use a WordPress optimization plugin like WP Rocket or LiteSpeed Cache to automatically inline critical CSS. Defer non-critical JavaScript files including ua-parser.js and move them to load after page content. Minify and combine CSS files to reduce the number of blocking requests.
0Needs Improvement
What This Score Means
A score of 59 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
191ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This WordPress site has poor performance issues with a score of 59/100. The biggest problem is extremely slow JavaScript execution taking 2.5 seconds, which causes an alarming 20-second delay before the page becomes fully interactive. The site is also suffering from render-blocking resources that delay initial page display by 650ms and oversized images that waste 637KB of bandwidth. Reducing JavaScript execution time, deferring non-critical scripts, and optimizing image sizes could improve your score by 30+ points and dramatically reduce the painfully long wait time users currently experience.
Other Optimization Recommendations
Optimize Images for Performance
High Impact+20 points estimatedWhy It Matters:
Oversized images waste 637KB of bandwidth and the hero banner alone is 4600x2251 pixels when only 668x327 is displayed.
How to Fix:
Install ShortPixel or Smush to automatically compress and resize images. Create responsive image sets using WordPress's built-in srcset functionality. Convert PNG badge images to WebP format for 60-80% size reduction. Set proper dimensions in your theme's image elements.
Reduce JavaScript Execution Time
High Impact+15 points estimatedWhy It Matters:
JavaScript execution takes 2.5 seconds and blocks the main thread for 600ms, severely impacting interactivity with a 20-second TTI.
How to Fix:
Remove or defer the heavy ContentSquare tracking script (737ms execution time) until after page load. Audit WordPress plugins for unused JavaScript and remove unnecessary ones. Use code splitting to load only essential JavaScript initially, deferring analytics and tracking scripts.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More WordPress Speed Tests
WordPress Performance Resources
Implement Better Caching Strategy
Poor cache lifetimes waste 1,106 KiB on repeat visits and delay LCP by 1.1 seconds for returning users.
Remove Unused JavaScript and CSS
602 KiB of unused JavaScript and 112 KiB of unused CSS are blocking rendering and delaying LCP by 4.6 seconds.
Optimize Image Formats and Compression
Images are causing a 750ms LCP delay and waste 210 KiB, directly impacting your largest contentful paint performance.
Remove Unused JavaScript Resources
Unused JavaScript is adding 1.2MB of dead code that blocks rendering and increases Total Blocking Time.