Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize fansframe.com
Cookie consent script creates a 738ms dependency chain by making requests to ipinfo.io, blocking critical rendering.
Replace the current cookie consent implementation with a lighter solution that doesn't require external API calls. Remove the unused preconnect to fonts.bunny.net to avoid wasted DNS lookups. Consider self-hosting the cookie consent files to eliminate third-party dependencies.
A score of 94 falls in the "Good" 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 excellent performance with a score of 94/100, but there's still room for improvement. The biggest issue is render-blocking JavaScript and CSS files that are delaying when users first see content, potentially saving 850ms if addressed properly. The main culprits are the Livewire JavaScript framework file and cookie consent scripts that are blocking the initial page render. To boost performance further, consider deferring or inlining these scripts, and reducing the 82KB of unused JavaScript code that's currently being downloaded but not executed.
Why It Matters:
Render blocking scripts delay LCP and FCP by 850ms, significantly impacting page load speed.
How to Fix:
Move the Livewire JavaScript (94KB) and cookie consent scripts to load after initial page render using async or defer attributes. Inline critical CSS for cookie consent instead of loading external stylesheet. Consider lazy loading the cookie consent functionality until user interaction.
Why It Matters:
89% of the Livewire bundle (83KB) is unused, wasting bandwidth and slowing FCP by 350ms.
How to Fix:
Configure your build process to tree-shake unused Alpine.js modules (@alpinejs/sort, @alpinejs/anchor, @alpinejs/focus). Use dynamic imports for Alpine.js components that aren't needed on initial page load. Consider code splitting to load only required functionality per page.
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.