Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize fansframe.com
81KB of unused JavaScript in Alpine.js modules wastes bandwidth and slows parsing without improving functionality.
Audit your Alpine.js usage and remove unused plugins like @alpinejs/sort, @alpinejs/anchor, and @alpinejs/focus if not needed. Use tree-shaking or create a custom Alpine build with only required components. Consider lazy-loading Alpine components that aren't immediately visible.
A score of 98 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 98/100, indicating a very well-optimized site. The biggest issue is render-blocking JavaScript and CSS files that are delaying the initial page display by 260 milliseconds, particularly the Livewire JavaScript framework and cookie consent scripts. The site is using Alpine.js with several modules, but much of the JavaScript code (81 KiB) isn't being used and could be removed or deferred. To achieve a perfect score, consider deferring non-critical JavaScript like the cookie consent scripts and removing unused Alpine.js modules to eliminate the render-blocking delays.
Why It Matters:
Render blocking requests delay LCP and FCP by 250ms, preventing users from seeing content quickly.
How to Fix:
Move the cookieconsent CSS to inline critical styles or defer it until after page load. Defer the cookieconsent JavaScript using async/defer attributes. Consider self-hosting these files to reduce third-party dependency chains.
Why It Matters:
Unnecessary preconnect to fonts.bunny.net wastes browser resources and creates false network priorities.
How to Fix:
Remove the preconnect link to https://fonts.bunny.net from your HTML head section since no requests are made to this origin. If you plan to use fonts from this CDN, ensure they're actually loaded on the 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.