LCP
Largest Contentful Paint
12.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix LCP Image Discovery Issues
How to optimize ona.co.il
Fix LCP Image Discovery Issues
High Impact+25 points estimated
Why It Matters
The LCP image has a 2.4 second resource load delay because it's not discoverable in the initial HTML and lacks priority hints.
How to Fix
Remove lazy loading from the hero image by removing data-lazy-src attribute and ensuring it loads immediately. Add fetchpriority='high' attribute to the LCP image. Ensure the image src is directly in HTML rather than loaded via JavaScript to make it discoverable.
0Poor
What This Score Means
A score of 47 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
131ms
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 serious performance issues with a poor score of 47/100. The biggest problem is an extremely slow Largest Contentful Paint of 12.5 seconds, primarily caused by a 2.4-second delay in loading the main hero image due to poor resource discovery and lack of proper prioritization hints. The site is also bloated with 545 KB of unused JavaScript and 208 KB of unused CSS, which blocks rendering and slows down the initial page load. Fixing the image loading by adding fetchpriority="high" to the hero image, removing unused code, and implementing better caching could improve the score by 30+ points and dramatically reduce load times for users.
Other Optimization Recommendations
Eliminate Render Blocking Resources
High Impact+20 points estimatedWhy It Matters:
CSS files are blocking first paint by 2.05 seconds, significantly delaying when users see content.
How to Fix:
Inline critical CSS for above-the-fold content directly in the HTML head. Defer non-critical CSS like cart styles and payment gateway CSS using media='print' onload technique. Use WordPress plugins like Autoptimize to automatically handle CSS optimization and critical path extraction.
Reduce Unused JavaScript and CSS
High Impact+18 points estimatedWhy It Matters:
545 KiB of unused JavaScript and 208 KiB of unused CSS are unnecessarily slowing down your site by 1.5 seconds.
How to Fix:
Remove or conditionally load unused WordPress plugins like dashicons.min.css (35KB) that aren't needed on frontend. Use Asset CleanUp plugin to disable scripts/styles on pages where they're not needed. Split large JavaScript bundles and only load required functionality per page.
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
Eliminate Forced Layout Reflows
JavaScript is forcing 125ms of layout reflows, blocking the main thread and degrading user interaction responsiveness.
Optimize Image Delivery and Sizing
Images are causing 2,367 KiB of wasted bytes and delaying LCP by 400ms, with the hero image alone accounting for 1.6MB.
Reduce Unused JavaScript and CSS
545 KiB of unused JavaScript and 208 KiB of unused CSS are blocking rendering and delaying LCP by 2.35 seconds.
Optimize Image Sizing
Images are 32KB larger than needed, slowing LCP by 150ms due to oversized assets.