LCP
Largest Contentful Paint
21.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Code
How to optimize cherykecskemet.hu
Remove Unused JavaScript Code
High Impact+18 points estimated
Why It Matters
223 KiB of unused JavaScript is delaying LCP by 1.75 seconds, primarily from Google Maps API and Swiper carousel.
How to Fix
Conditionally load Google Maps API only on pages that need it using wp_enqueue_script with page conditions. Remove unused Swiper.js features by using custom build or switch to lighter carousel alternatives. Use WP Asset CleanUp to disable scripts on pages that don't need them.
0Needs Improvement
What This Score Means
A score of 54 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
305ms
Needs Improvement
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 site has poor performance with a score of 54/100, indicating significant user experience issues. The biggest problem is excessive unused JavaScript, particularly from Google Maps API and carousel components, which is wasting 223 KiB and delaying page loading by 1.75 seconds. The site also suffers from render-blocking CSS files that prevent content from appearing quickly, contributing to a painfully slow Largest Contentful Paint of 21.9 seconds. Removing unused JavaScript, optimizing CSS delivery, and implementing modern image formats could dramatically improve loading times and boost the performance score by 30+ points.
Other Optimization Recommendations
Optimize Critical Rendering Path
High Impact+15 points estimatedWhy It Matters:
Render-blocking CSS is delaying first paint by 2.5 seconds, particularly the Dashicons stylesheet that's completely unused.
How to Fix:
Remove wp_enqueue_style for dashicons if not using WordPress admin bar on frontend. Inline critical CSS for above-the-fold content using plugins like WP Rocket or Autoptimize. Defer non-critical stylesheets using media='print' then switching to 'all' via JavaScript.
Implement Modern Image Delivery
High Impact+12 points estimatedWhy It Matters:
Images consume 2.2 MB and could save 2,215 KiB through modern formats and proper sizing.
How to Fix:
Install ShortPixel or Imagify to automatically convert images to WebP/AVIF format. Use WordPress responsive images by defining custom image sizes in functions.php. Implement lazy loading with native loading='lazy' attribute on all below-fold images.
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
Reduce Render-Blocking Resources
Critical CSS and JavaScript files are blocking initial page render for 3.4 seconds, severely delaying First Contentful Paint.
Optimize JavaScript Execution and Delivery
JavaScript execution takes 4.6 seconds and blocks the main thread, preventing user interactions and delaying page readiness.
Fix Unsized Images and Font Loading
Images without dimensions and web font loading cause significant layout shifts (CLS: 0.239) and delay content visibility.
Optimize Render-Blocking Resources
Render-blocking scripts are delaying FCP by 3.3 seconds, preventing users from seeing content quickly.