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
JavaScript dependency chains are creating a 6.7-second bottleneck that delays Largest Contentful Paint.
Bundle critical JavaScript resources to reduce chain length. Preload key resources like wp-polyfill.min.js and flatsome.js. Remove unused preconnect hints to fonts.googleapis.com and fonts.gstatic.com that aren't being used.
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 severe performance problems with a score of only 50/100, indicating critical issues that are hurting user experience. The biggest problem is extremely slow page loading - it takes 9.7 seconds for content to appear and 17.7 seconds for the largest element to load, which is far beyond acceptable standards. The site is loading massive amounts of unnecessary JavaScript (545 KiB of unused code) and CSS (209 KiB unused), along with oversized images that are much larger than needed for their display size. Reducing these bloated resources, optimizing images, and minimizing the complex chain of network requests could dramatically improve loading times and user satisfaction.
Why It Matters:
Critical CSS files are blocking First Contentful Paint by 1.4 seconds, severely delaying visible content.
How to Fix:
Inline critical CSS directly in the HTML head section. Use WP Rocket or Autoptimize to defer non-critical CSS. Remove unused CSS from dashicons.min.css (35KB) and flatsome-rtl.css that's blocking render.
Why It Matters:
Main thread is blocked for 4.6 seconds by script evaluation, preventing user interactions and delaying Time to Interactive.
How to Fix:
Remove or defer 545KB of unused JavaScript from Google Tag Manager and support widgets. Split large JavaScript bundles and load non-critical scripts after page load. Consider removing heavy third-party scripts that aren't essential.
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
Main thread is blocked for 4.6 seconds by script evaluation, preventing user interactions and delaying Time to Interactive.
Zero cache lifetime on static assets forces 312 KiB re-downloads on every visit, slowing repeat visits significantly.
Oversized product images waste 682 KiB and delay LCP by 600ms with images 10x larger than needed.
JavaScript is forcing 125ms of layout reflows, blocking the main thread and degrading user interaction responsiveness.