Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize yimeowragdoll.ca
The LCP image is not discoverable in initial HTML, preventing early loading optimization.
Move the hero image from background layers to a proper img element in Wix Editor. Add the image directly to your page section instead of using background media. Ensure the image appears in the initial HTML markup rather than being loaded via JavaScript after page render.
A score of 55 falls in the "Needs Improvement" 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 Wix site has poor performance with a score of 55/100, primarily caused by excessive JavaScript that's blocking the main thread for over 3 seconds. The biggest issue is duplicated JavaScript code (135 KiB of redundant modules) combined with 489 KiB of unused JavaScript, which is causing your Largest Contentful Paint to take 6.6 seconds - more than double the recommended time. Additionally, there's 118 KiB of unused CSS and unminified JavaScript files that could be compressed to save another 47 KiB. Optimizing these JavaScript and CSS files, removing duplicated code, and enabling better caching could potentially improve your performance score by 30+ points and dramatically speed up page loading for your visitors.
Why It Matters:
Duplicated JavaScript wastes 135 KiB and delays LCP by 300ms across multiple Wix widget bundles.
How to Fix:
Contact Wix support to report duplicate modules like @wix/image-kit appearing across 11 bundles. Use Wix's App Market alternatives for FAQ and profile card widgets that share fewer dependencies. Consider custom HTML components instead of multiple third-party widgets.
Why It Matters:
489 KiB of unused JavaScript increases main thread work to 3.0s and blocks user interactions.
How to Fix:
Remove or replace the FAQ widget (336KB, 61% unused) with Wix's native FAQ strip. Audit Google Tag Manager implementation to remove unused tracking codes. Use Wix's built-in analytics instead of multiple external tracking scripts to reduce the 200KB+ of wasted code.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Performance Analyses
92% of CSS (30KB) is unused, slowing down initial page rendering and wasting bandwidth.
Forced reflows are causing 37.3ms of blocking time, directly impacting user interaction responsiveness and INP scores.
The LCP image is not discoverable in the initial HTML document, delaying the largest contentful paint by preventing early resource loading.
489 KiB of unused JavaScript increases main thread work to 3.0s and blocks user interactions.
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.