Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize pupsncups.pages.dev
Images are severely oversized for their display dimensions, wasting 437 KiB and delaying page rendering.
Replace fixed image dimensions with responsive sizes using srcset attribute. Resize the favicon from 960x964 to 48x48 pixels for actual display size. Generate multiple image sizes (320w, 640w, 1024w) and serve appropriate dimensions based on viewport width.
A score of 0 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 website has severe performance issues with a score of 0/100, meaning it's extremely slow for users. The biggest problem is that the first content doesn't appear until 8.3 seconds, which is far beyond acceptable standards - users typically abandon sites that take longer than 3 seconds to load. The main culprits are oversized images that are wasting 437KB of bandwidth (like a logo that's 960x964 pixels but displayed at only 52x48) and render-blocking CSS and font files that prevent the page from showing content quickly. Additionally, there are forced reflows in the JavaScript causing 74ms of wasted processing time, which compounds the performance problems.
Why It Matters:
CSS and font files are blocking initial page render, preventing content from appearing quickly.
How to Fix:
Inline critical CSS for above-the-fold content directly in HTML head. Use font-display: swap for Google Fonts to show fallback text immediately. Defer non-critical CSS using media='print' then switching to 'all' onload.
Why It Matters:
JavaScript is causing 74ms of forced reflows, blocking the main thread and degrading user interactions.
How to Fix:
Batch DOM reads and writes to avoid layout thrashing. Cache geometric properties like offsetWidth instead of repeatedly querying them. Use CSS transforms instead of changing layout properties for animations.
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
JavaScript is causing 74ms of forced reflows, blocking the main thread and degrading user interactions.
CSS and font files are blocking initial page render, preventing content from appearing quickly.
JavaScript is causing 335ms of forced reflows, creating janky user experience and blocking interactions.
Over 1MB of unused JavaScript is delaying LCP by 1.5 seconds and blocking user interactions.