Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize fansframe.com
The LCP image isn't discoverable in initial HTML and uses lazy loading, preventing fast loading of critical content.
Add fetchpriority='high' to your LCP image element (img.w-full in the carousel). Remove loading='lazy' from above-the-fold images. Ensure the LCP image source is directly in HTML rather than loaded via JavaScript to enable early discovery by the browser.
A score of 69 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 69/100, indicating significant issues that are slowing down the user experience. The biggest problem is excessive unused JavaScript (388 KiB) that's blocking the page from loading efficiently, causing the First Contentful Paint to take 4.3 seconds and Largest Contentful Paint to reach 4.8 seconds - both well above Google's recommended thresholds. The site is also loading nearly 19 KiB of unused CSS and has render-blocking resources that could save almost 1 second if properly optimized. Removing unused code, implementing proper lazy loading for the main hero image, and deferring non-critical JavaScript could dramatically improve load times and boost the performance score by 20-30 points.
Why It Matters:
Unused JavaScript wastes 397KB and delays LCP by 2.1 seconds, severely impacting page load performance.
How to Fix:
Audit your JavaScript bundle to identify unused code, especially in Alpine.js modules (@alpinejs/sort, @alpinejs/anchor, @alpinejs/focus). Use tree shaking with Vite to eliminate dead code. Consider lazy loading Livewire components that aren't immediately needed on page load.
Why It Matters:
Render blocking scripts delay First Contentful Paint by nearly 1 second, slowing initial page rendering.
How to Fix:
Defer cookieconsent.min.js loading using async or defer attributes since it's not critical for initial render. Move Livewire initialization to load after DOM content. Inline critical CSS from cookieconsent.min.css or load it asynchronously with media='print' onload technique.
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.