Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize solsticehw.com
Oversized images waste 65KB of bandwidth and delay LCP by 300ms for logo and hero images.
Use WordPress's responsive image srcset properly sized for mobile viewports. Install ExactDN or ShortPixel to automatically serve correctly sized images. Add explicit width/height attributes to prevent layout shifts during image load.
A score of 65 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 65/100, primarily due to severe layout shift issues and slow loading times. The biggest problem is cumulative layout shift (CLS) caused by web fonts loading late, which makes content jump around as users try to read it, creating a frustrating experience. The site also suffers from a very slow Largest Contentful Paint of 6 seconds, meaning users wait too long to see the main content. To fix these issues, you should optimize font loading by using font-display: swap, reduce unused CSS and JavaScript (which could save 120+ KiB), and properly size images that are currently much larger than needed for their display dimensions.
Why It Matters:
Web fonts are causing 0.051 CLS layout shifts and blocking content rendering, directly impacting user experience.
How to Fix:
Add font-display: swap to your Google Fonts CSS imports. Use rel='preload' for critical Montserrat and Crimson Text fonts in your Divi theme. Consider hosting fonts locally to reduce network requests and FOUT.
Why It Matters:
73KB of unused JavaScript is delaying LCP by 450ms and blocking page interactivity.
How to Fix:
Use Divi's selective loading features to load only necessary modules. Install Asset CleanUp Pro to disable unused WordPress scripts. Split the large scripts.min.js file to load only required functionality per page.
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
LCP element has a 2-second resource load delay, indicating poor resource prioritization and server response time.
Font loading delays are causing 2.1 seconds of render blocking, preventing content from displaying quickly.
CSS and JavaScript files are blocking page render for 3.7 seconds, severely delaying First Contentful Paint.
Static assets like fonts and images have no cache headers, forcing unnecessary re-downloads and adding 7.2 seconds to LCP on repeat visits.