Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize playingcardtarot.app
Oversized images waste 1.2MB of bandwidth and delay LCP by 6.2 seconds, significantly impacting load performance.
Resize images to match their display dimensions (e.g., 1024x1024 images displayed at 443x443). Implement responsive images using srcset attribute for different screen sizes. Increase compression levels or convert to more efficient formats like AVIF. Add explicit width and height attributes to prevent layout shifts.
A score of 31 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 critically low score of 31/100, indicating a very poor user experience. The biggest problem is render-blocking CSS files that are preventing the page from displaying content quickly, causing an estimated 2.2 second delay in both First Contentful Paint and Largest Contentful Paint. Additionally, oversized images are wasting over 1.2MB of bandwidth and further slowing down the page, while the site takes an unacceptable 17.5 seconds to become fully interactive. To dramatically improve performance, the site should defer or inline critical CSS, optimize and properly size images, and reduce the massive amount of main-thread work that's blocking user interactions.
Why It Matters:
CSS files are blocking initial page render, delaying LCP by 2.2 seconds and causing the massive performance bottleneck.
How to Fix:
Inline critical CSS for above-the-fold content directly in the HTML head. Load non-critical CSS files (suit-backgrounds.css, cards-3d.css, components.css) asynchronously using media='print' onload='this.media="all"' technique. Consider combining CSS files to reduce HTTP requests.
Why It Matters:
Excessive main thread work (32.6 seconds) creates a 4-second blocking time, making the page unresponsive to user interactions.
How to Fix:
Replace the heavy Tailwind CDN (127KB) with a custom build containing only used classes. Optimize JavaScript execution by breaking up long tasks using setTimeout or requestIdleCallback. Address the 108ms of forced reflows in theme-system.js by batching DOM reads and writes separately.
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
Poor cache policies on external scripts force repeated downloads, slowing repeat visits by 248 KiB.
330 KiB of unused JavaScript delays LCP by 400ms and blocks the main thread for 2 seconds.
Font loading delays are causing 650ms delay to First Contentful Paint and creating invisible text periods.
Missing width and height attributes on images cause layout shifts that hurt user experience and CLS scores.