Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize 9dfddc46.a4bc.4b07.b53b.c830f68046c9.00.142wvhwqhxbbh.spock.replit.dev
Framer Motion animations cause 107ms of forced layout recalculations, blocking user interactions and degrading performance.
Replace geometric property queries with transform-based animations that don't trigger reflows. Use CSS transforms and opacity changes instead of width/height animations. Consider reducing animation complexity or using CSS animations for simple transitions.
A score of 49 falls in the "Poor" 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 development site has poor performance with a score of 49/100, primarily due to excessive JavaScript that's blocking the page from becoming interactive for over 25 seconds. The biggest culprits are oversized libraries like Lucide React icons (1MB) and React DOM that contain mostly unused code, plus unminified JavaScript files that could be 1.4MB smaller. The site is also suffering from render-blocking scripts and forced reflows caused by the Framer Motion animation library, which delays the first content paint by nearly 14 seconds. Minifying JavaScript, removing unused code, and optimizing the large image files could dramatically improve performance and reduce load times by several seconds.
Why It Matters:
Render blocking scripts delay First Contentful Paint by 350ms, preventing users from seeing content immediately.
How to Fix:
Move the Replit banner script to load asynchronously by adding async/defer attributes. Inline critical CSS for Google Fonts or preload the font files. Remove or defer the banner script entirely in production builds since it adds 1.2 seconds of blocking time.
Why It Matters:
Unused JavaScript wastes 1,070 KiB and unminified code adds 1,470 KiB, significantly delaying LCP by 6+ seconds.
How to Fix:
Enable Vite's production build with minification for deployment. Implement code splitting to load only necessary components initially. Remove unused TanStack Query features (87% unused) and Framer Motion animations (55% unused) through tree-shaking or selective imports.
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 Generic Speed Tests
Large font files (466KB fa-thin-100.woff2, 328KB fa-solid-900.woff2) delay FCP by 100ms and cause layout shifts.
Plugin.min.js contains 63KB of unused code and blocks main thread, causing poor user experience and delayed interactivity.
Critical CSS files are blocking page render for 9.4 seconds, severely delaying FCP and LCP by 9.45 seconds.
Oversized images waste 425 KiB and missing width/height attributes can cause layout shifts affecting CLS.