LCP
Largest Contentful Paint
7.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Delivery and Sizing
How to optimize iratszef.hu
Optimize Image Delivery and Sizing
Medium Impact+15 points estimated
Why It Matters
The main content image is oversized by 155KB and lacks proper dimensions, contributing to slow LCP and layout shifts.
How to Fix
Resize iratkezeles-iratszef-2.jpg from 1333x2000 to its displayed size of 651x977. Convert images to WebP format using ShortPixel or Imagify. Add explicit width and height attributes to all images to prevent CLS. Enable responsive images in WordPress theme settings.
0Poor
What This Score Means
A score of 32 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
625ms
Poor
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 severe performance issues with a critically low score of 32/100. The biggest problem is render-blocking CSS files that are delaying the initial page load by nearly 4 seconds, preventing users from seeing any content quickly. The site is loading an excessive amount of unused CSS (84KB wasted) and has extremely slow loading times with First Contentful Paint at 4.8 seconds and Largest Contentful Paint at 7.4 seconds. Optimizing the CSS delivery by removing unused styles, deferring non-critical CSS, and reducing the number of stylesheet requests could dramatically improve performance by 3-4 seconds and boost the score by 30+ points.
Other Optimization Recommendations
Eliminate Render-Blocking CSS Resources
High Impact+35 points estimatedWhy It Matters:
Critical CSS files are blocking page render for 3.7 seconds, severely delaying both FCP and LCP.
How to Fix:
Use WP Rocket or Autoptimize to inline critical CSS and defer non-critical stylesheets. Specifically target the large thegem-style.min.css (22KB) and thegem-widgets.min.css (20KB) files. Remove unused CSS rules which account for 84KB of wasted bytes across multiple theme files.
Reduce Main Thread Blocking Time
High Impact+25 points estimatedWhy It Matters:
JavaScript execution blocks the main thread for 1.6 seconds with 1,610ms Total Blocking Time, preventing user interactions.
How to Fix:
Defer jQuery and non-critical JavaScript using async/defer attributes. Break up long tasks in wp-includes/js/jquery/jquery.min.js which causes 712ms of forced reflow. Use WP Optimize to minimize and combine JavaScript files, focusing on the heaviest scripts first.
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.