h-o.co.il website review

The page has 8,012 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

A phone's processor spends 4.5 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

99 images could be 7.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Your mobile performance score is 66 (desktop: 49). Pages that score under 90 lose visitors before the first paint.

7 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 1.1 MB and 698 ms of main-thread time.

11 long tasks block the main thread while loading, the longest for 616 ms. During a long task the page ignores taps.

Google Tag Manager costs a phone 511 ms of main-thread work and 865 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 492 KiB of JavaScript is downloaded but never used on this page.

About 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

4 files are served with short cache lifetimes, so returning visitors download them again (218 KiB).

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The page becomes fully interactive after 18.1 s. Good is under 3.8 s.

Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 206 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 113 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

Visually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “חצאית עם תחרה אמיליה”.

The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

5 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 14.7 MB in 289 requests on a phone: images 12.5 MB (126), scripts 1.1 MB (18) and other files 899 KiB (138). Under 2 MB keeps phones on slow connections fast.

19 images are downloaded at several times the size a phone draws them, for example 5100211944_4.jpg at 900 px wide, shown at 182 px. Resized copies would save about 895 KiB.

40 images (3.2 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

5434_HO_70_640X6404.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (103 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 4.17 g of CO₂e: 500.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 5 elements on the page fail this check, rated critical by axe-core.

44 tap targets are too small or too close together to hit reliably with a finger.

9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

2 visible links have no text or label, so screen readers cannot say where they go.

2 elements have a tabindex above 0, which scrambles the keyboard order.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 290 pages on h-o.co.il and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/privacy, /store-locator and /contact have no meta description, so Google writes the search snippet from whatever text it finds.

/144343-%D7%A0%D7%A9%D7%99%D7%9D/144351-%D7%91%D7%99%D7%92%D7%95%D7%93, /144343-%D7%A0%D7%A9%D7%99%D7%9D/144351-%D7%91%D7%99%D7%92%D7%95%D7%93/144697-%D7%97%D7%95%D7%9C%D7%A6%D7%95%D7%AA-%D7%98%D7%99-%D7%A0%D7%A9%D7%99%D7%9D, /144343-%D7%A0%D7%A9%D7%99%D7%9D/144351-%D7%91%D7%99%D7%92%D7%95%D7%93/144423-%D7%92-%D7%99%D7%A0%D7%A1%D7%99%D7%9D, /144343-%D7%A0%D7%A9%D7%99%D7%9D/144351-%D7%91%D7%99%D7%92%D7%95%D7%93/144430-%D7%97%D7%95%D7%9C%D7%A6%D7%95%D7%AA, /144343-%D7%A0%D7%A9%D7%99%D7%9D/144351-%D7%91%D7%99%D7%92%D7%95%D7%93/144429-%D7%9E%D7%9B%D7%A0%D7%A1%D7%99%D7%99%D7%9D and /144343-%D7%A0%D7%A9%D7%99%D7%9D/144351-%D7%91%D7%99%D7%92%D7%95%D7%93/144426-%D7%A1%D7%A8%D7%99%D7%92%D7%99%D7%9D-%D7%95%D7%A7%D7%A8%D7%93%D7%99%D7%92%D7%A0%D7%99%D7%9D and 6 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 124 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://ams46.creativecdn.com/info?tk=J6-p1nUuZB6l6GHX6s0O6O9ZCYxfazYIP7w5xCyT5dVP9G5Pt5Z3elgJm7jsuOEUYfCK3wCKSqPsmagSaFfiHgA.

45 of 126 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://www.clarity.ms/tag/qfavvtsjl5?ref=gtm2' violates the following Content Security Policy dire…”.

Chrome logged issues while loading the page (“Content security policy”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 99 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Xandr (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 13 cookies, 2 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.