LCP
Largest Contentful Paint
7.2s
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 umtcar.be
Optimize Image Delivery and Sizing
High Impact+25 points estimated
Why It Matters
Large images waste 1.7MB bandwidth and significantly impact loading performance with poor LCP of 7.2s.
How to Fix
Implement responsive images using srcset attributes to serve appropriately sized images (current images are 3-4x larger than displayed). Compress existing WebP images further using tools like ImageOptim. Add proper image dimensions in HTML to prevent layout shifts during loading.
0Needs Improvement
What This Score Means
A score of 65 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
108ms
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 website has poor performance with a score of 65/100, primarily due to extremely slow loading times with pages taking over 7 seconds to become interactive. The biggest problem is oversized images that are much larger than needed for their display size, wasting nearly 1.7MB of download data and significantly delaying page rendering. Additionally, the site is bloated with unused JavaScript (106KB) and CSS (14KB), while legacy JavaScript code is adding unnecessary overhead. Optimizing image sizes to match their display dimensions, removing unused code, and fixing the forced reflow issues in the main JavaScript file could dramatically improve loading speeds and user experience.
Other Optimization Recommendations
Fix JavaScript Forced Reflows
High Impact+18 points estimatedWhy It Matters:
Main.js causes 133ms of forced reflows, blocking the main thread and delaying interactivity.
How to Fix:
Refactor main.js to batch DOM reads and writes separately. Cache DOM measurements instead of repeatedly querying offsetWidth/height. Use CSS transforms instead of layout-triggering properties where possible. Consider using requestAnimationFrame for smoother animations.
Remove Unused JavaScript and CSS
Medium Impact+12 points estimatedWhy It Matters:
106KB of unused JavaScript and 14KB of unused CSS slow down page parsing and execution unnecessarily.
How to Fix:
Remove unused portions of jQuery (76% unused) and Swiper.js (61% unused) by using tree-shaking or switching to lighter alternatives. Audit all-min.css and remove unused rules (72% unused). Consider loading Google Analytics asynchronously to reduce blocking time.
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 Generic Speed Tests
Generic Performance Resources
Minify and Reduce JavaScript
Unminified JavaScript wastes 1.4 MB and causes 2.3 seconds of blocking execution time.
Optimize Image Delivery and Sizing
Large unoptimized images cause 10.4 MB of wasted bandwidth and trigger major layout shifts affecting CLS.
Eliminate Render Blocking CSS
Blocking CSS resources delay First Contentful Paint by 5.4 seconds and waste 237 KiB of unused styles.
Eliminate Render Blocking CSS
Critical CSS file blocks initial page render for 8.1 seconds, severely delaying FCP and LCP.