Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize mariawarszawa.com
142 KiB in image savings can improve LCP by 450ms through modern formats.
Install ShortPixel or Imagify to automatically convert images to WebP/AVIF format. Resize the oversized logo from 789x316 to actual display size of 210x84. Add fetchpriority='high' to above-the-fold service images to prioritize loading.
A score of 38 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 WordPress site has severely poor performance with a score of only 38/100. The biggest problem is extremely slow loading times - it takes 7.6 seconds just to show the first content and 11.1 seconds to fully load the main visual element, which is far beyond acceptable standards. The site is overwhelmed by excessive JavaScript (775 KiB of unused code), unoptimized images (142 KiB savings available), and massive amounts of unused CSS (123 KiB that could be removed). Fixing these JavaScript and CSS bloat issues alone could improve loading times by several seconds and dramatically enhance user experience, as the current performance would frustrate most visitors who expect pages to load within 2-3 seconds.
Why It Matters:
775 KiB of unused JavaScript is blocking page load and delaying LCP by 1.7 seconds.
How to Fix:
Remove or defer the booking engine script if not needed on homepage. Use WP Asset CleanUp to conditionally load Stripe and Google Maps only on booking pages. Consider code splitting for the main booking script to load only required components.
Why It Matters:
123 KiB of unused CSS is render-blocking and delaying FCP by 750ms.
How to Fix:
Install Autoptimize or WP Rocket to remove unused CSS from theme.css and Font Awesome. Use PurgeCSS to eliminate 92% of unused theme styles. Conditionally load the booking engine CSS only on relevant pages.
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 WordPress Speed Tests
123 KiB of unused CSS is render-blocking and delaying FCP by 750ms.
775 KiB of unused JavaScript is blocking page load and delaying LCP by 1.7 seconds.
Main thread blocked for 4 seconds by heavy JavaScript preventing user interactions.
Critical CSS blocks First Contentful Paint by 2.5 seconds preventing content visibility.