LCP
Largest Contentful Paint
9.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix LCP Slider Image Loading
How to optimize bulgakovaphoto.com
Fix LCP Slider Image Loading
High Impact+25 points estimated
Why It Matters
The hero slider image has a massive 2.2 second resource load delay causing LCP of 9.9 seconds.
How to Fix
Preload the hero slider background image by adding <link rel='preload' as='image' href='hero-image.jpg'> in your theme's header.php. Remove lazy loading from the LCP element and add fetchpriority='high' to the slider container. Consider using a static hero image instead of JavaScript-loaded background images.
0Needs Improvement
What This Score Means
A score of 66 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
117ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This WordPress photography site has poor performance with a score of 66/100, primarily due to an extremely slow Largest Contentful Paint of 9.9 seconds. The biggest issue is a massive 2.2-second delay in loading the hero slideshow image, caused by the image not being discoverable in the initial HTML and lack of proper prioritization. The site is also bloated with 132 KiB of unused JavaScript, 92 KiB of unused CSS, and oversized images that waste 158 KiB of bandwidth. To improve performance significantly, prioritize the hero image with fetchpriority="high", optimize and properly size images, and remove unused code from the theme and plugins.
Other Optimization Recommendations
Optimize and Resize Portfolio Images
High Impact+18 points estimatedWhy It Matters:
Portfolio images waste 158KB with oversized dimensions and poor compression, directly impacting LCP by 650ms.
How to Fix:
Install ShortPixel or Imagify WordPress plugin to automatically compress images by 60%. Use responsive image sizes in your portfolio grid - resize 845x684px images to match their 613x496px display size. Enable WebP conversion in your optimization plugin settings.
Remove Unused CSS and JavaScript
Medium Impact+12 points estimatedWhy It Matters:
132KB of unused JavaScript and 92KB of unused CSS are unnecessarily blocking page rendering.
How to Fix:
Install Asset CleanUp Pro to disable unused scripts per page. Remove the Buttonizer widget if not essential (78KB savings). Audit your Enfold theme settings to disable unused features. Use WP Rocket's file optimization to minify and combine remaining assets.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More WordPress Speed Tests
WordPress Performance Resources
Optimize LCP Image Discovery
Your LCP element is not discoverable in initial HTML and lacks priority hints, preventing early loading optimization.
Remove Unused JavaScript Code
628 KiB of unused JavaScript wastes bandwidth and increases execution time, with reCAPTCHA alone contributing 571 KiB of waste.
Eliminate Render-Blocking JavaScript Resources
Render-blocking scripts delay First Contentful Paint by 8.7 seconds, severely impacting your LCP of 15.3 seconds.
Reduce Render-Blocking Resources
Critical CSS and JavaScript files are blocking initial page render for 3.4 seconds, severely delaying First Contentful Paint.