Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize reyvivas.com
Your signature PNG is oversized (737x294 served at 180x72) and unoptimized, wasting 45KB and slowing LCP.
Resize the signature.png to exact display dimensions (180x72). Convert to WebP format for better compression. Since it already has fetchpriority='high', ensure it's properly sized and compressed to maximize the priority hint effectiveness.
A score of 66 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 website has poor performance with a score of 66/100, primarily due to extremely slow loading times that take over 12 seconds for the page to become fully interactive. The biggest issue is excessive JavaScript execution (5.5 seconds) combined with large video files totaling over 21MB, which creates enormous network payloads that cost users real money on mobile data. The main signature image is also inefficiently optimized, being 4x larger than needed and not using modern formats like WebP. Reducing JavaScript complexity, compressing or lazy-loading the videos, and properly sizing/optimizing images could dramatically improve performance and user experience.
Why It Matters:
Your main script file (script.min.js) blocks the main thread for 5.5 seconds, severely delaying page interactivity and LCP.
How to Fix:
Split your JavaScript bundle into critical and non-critical parts. Load only essential code synchronously and defer the rest using dynamic imports or async loading. Consider code splitting to reduce the initial bundle size from its current large payload.
Why It Matters:
The LCP element has a 1.5-second render delay, contributing significantly to the poor 12.6-second LCP score.
How to Fix:
Move critical CSS inline to eliminate render-blocking stylesheets. Remove the loading screen that contains your LCP image, as it delays actual content visibility. Preload critical resources and optimize the critical rendering path to reduce element render delay.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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.