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
Unused JavaScript wastes 546 KiB and delays LCP by 800ms while blocking the main thread.
Remove or defer Google Tag Manager script (107KB unused). Audit WooCommerce and payment gateway scripts for unused code. Use code splitting to load only necessary JavaScript per page. Configure async loading for analytics and tracking scripts.
A score of 28 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.
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 severe performance issues with a critically low score of 28/100. The biggest problems are massive amounts of unused JavaScript (546 KiB) and render-blocking scripts that delay page rendering by 1.7 seconds, causing extremely slow loading times with pages taking over 9 seconds to become visually complete. The site is also bloated with a 5.6 MB total payload and suffers from 11.6 seconds of main-thread blocking work. Removing unused JavaScript, deferring non-critical scripts, and optimizing the numerous WooCommerce plugins could dramatically improve performance and user experience.
Why It Matters:
Critical render path is blocked for 1,720ms, preventing First Contentful Paint from occurring sooner.
How to Fix:
Move jQuery and WooCommerce scripts to load after DOM parsing using async/defer attributes. Inline critical CSS for above-the-fold content. Use resource hints like preload for essential fonts and defer non-critical CSS until after page load.
Why It Matters:
Oversized images waste 2,187 KiB bandwidth and could improve perceived performance significantly.
How to Fix:
Compress the hero image (1.6MB WebP) using tools like TinyPNG or ImageOptim. Implement responsive images with srcset for different screen sizes. Convert PNG images to WebP format for better compression ratios.
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.
Images are causing 2,367 KiB of wasted bytes and delaying LCP by 400ms, with the hero image alone accounting for 1.6MB.
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.