Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize ona.co.il
Images are causing 2,367 KiB of wasted bytes and delaying LCP by 400ms, with the hero image alone accounting for 1.6MB.
Implement responsive images using srcset for the hero image (800x450 displayed as 371x209). Increase compression on the WebP image to reduce file size by ~1.5MB. Use WordPress plugins like ShortPixel or Smush to automatically optimize and serve properly sized images.
A score of 50 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This website has poor performance with a score of 50/100, indicating significant issues that are hurting user experience. The biggest problem is extremely slow image loading - a single oversized image (1.6MB) is taking over 22 seconds to fully load and is severely impacting your Largest Contentful Paint. The site could save over 2MB by properly compressing images and serving them at appropriate sizes for mobile devices. Additionally, there's 545KB of unused JavaScript code that could be removed to speed up loading, and render-blocking CSS files are delaying the initial page display by nearly 1.5 seconds.
Why It Matters:
545 KiB of unused JavaScript and 208 KiB of unused CSS are blocking rendering and delaying LCP by 2.35 seconds.
How to Fix:
Remove or defer unused JavaScript from Google Tag Manager and support widgets. Use Asset CleanUp plugin to conditionally load CSS files only where needed. Remove unused Dashicons CSS (35KB) from frontend pages since it's admin-only.
Why It Matters:
JavaScript is forcing 125ms of layout reflows, blocking the main thread and degrading user interaction responsiveness.
How to Fix:
Optimize Clarity.js tracking script to batch DOM queries instead of individual reads. Update Flatsome theme JavaScript to cache layout properties rather than repeatedly querying offsetWidth. Consider moving analytics scripts to web workers or defer until after page load.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
JavaScript is forcing 125ms of layout reflows, blocking the main thread and degrading user interaction responsiveness.
545 KiB of unused JavaScript and 208 KiB of unused CSS are blocking rendering and delaying LCP by 2.35 seconds.
The LCP image has a 2.4 second resource load delay because it's not discoverable in the initial HTML and lacks priority hints.
Images are 32KB larger than needed, slowing LCP by 150ms due to oversized assets.