Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize digivate.com
The main hero section causes a 0.107 CLS score due to content moving after initial paint.
Add explicit dimensions to all images in the partner logos section using WordPress image size attributes. Reserve space for dynamically loaded content with CSS min-height properties. Ensure the hero section (#section1) has a defined height before content loads to prevent shifting.
A score of 60 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 60/100, placing it in the "needs improvement" category. The biggest problem is render-blocking resources, particularly a third-party cookie consent script from Termly that's delaying page content by over 2 seconds, causing your First Contentful Paint to reach 2.7 seconds and Largest Contentful Paint to hit a concerning 8.3 seconds. Additionally, the site is loading 93% unused CSS and has significant layout shifts affecting user experience. Deferring the Termly script, removing unused CSS from your theme files, and optimizing font loading could improve your score by 25+ points and dramatically speed up the initial page load.
Why It Matters:
Render-blocking CSS and scripts delay initial page rendering by 2.05 seconds and significantly impact FCP.
How to Fix:
Use a WordPress optimization plugin like WP Rocket to inline critical CSS for above-the-fold content. Defer loading of Gravity Forms CSS and JavaScript until needed. Move the Termly consent manager script to load asynchronously or after page interaction.
Why It Matters:
Custom fonts cause 60ms delay and contribute to layout shifts as fallback fonts load first.
How to Fix:
Add font-display: swap to all @font-face declarations in your WordPress theme's font-styles.css. Preload the most critical font file (Fredoka variable) using <link rel='preload'> in your theme's header.php. Implement font fallback metrics to match custom font dimensions.
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
Render-blocking CSS and JavaScript are delaying First Contentful Paint by 1.46 seconds.
Multiple redirects are adding 750ms delay to both LCP and FCP before the page even starts loading.
Poor cache lifetimes are wasting 349 KiB and delaying FCP/LCP by 600ms on repeat visits.
FontAwesome fonts cause 50ms delay in FCP due to missing font-display declarations.