Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize monfrancis.com
Short cache lifetimes waste 236KB on repeat visits, slowing down returning users.
In LiteSpeed Cache settings, increase 'Browser Cache TTL' to 1 year for images and CSS files. Add cache headers for your CDN images at imagedelivery.net. Configure your hosting provider to serve static assets with longer cache-control headers.
A score of 0 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 0/100, indicating critical problems that need immediate attention. The biggest issue is render-blocking CSS resources that are preventing the page from displaying content quickly, combined with a very slow Speed Index of 5.7 seconds - meaning users wait nearly 6 seconds to see meaningful content. The site also suffers from inefficient caching policies that could save 236 KB of data on repeat visits, and images without proper dimensions that could cause layout shifts. Fixing the render-blocking CSS, optimizing image loading, and implementing better caching strategies are essential first steps to make this site usable for visitors.
Why It Matters:
Critical CSS is blocking initial page render and delaying LCP significantly.
How to Fix:
Use LiteSpeed Cache's 'Critical CSS' feature to inline above-the-fold styles. Enable 'Load CSS Asynchronously' in LiteSpeed settings. Consider splitting the 106KB CSS file into critical and non-critical parts using tools like Critical or Critters.
Why It Matters:
Missing image dimensions cause layout shifts and the lazy-loaded images lack proper sizing attributes.
How to Fix:
Add explicit width and height attributes to all img elements in your Elementor templates. Use WordPress's add_image_size() function to define consistent dimensions. Enable 'Preserve Image Dimensions' in LiteSpeed Cache settings to maintain aspect ratios during 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.
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.