limore.co.il website review

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.

7 images could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

Google Tag Manager costs a phone 285 ms of main-thread work and 362 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.

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

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

8 third-party services load with your homepage (Google Tag Manager, tctm.xyz and Shopify and others), adding 543 KiB and 387 ms of main-thread time.

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

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

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

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

Polyfills for old browsers add 6 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.

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Your homepage downloads 5.9 MB in 178 requests on a phone: media 3.5 MB (1), images 841 KiB (29) and other files 744 KiB (91). Under 2 MB keeps phones on slow connections fast.

H8460103_iimor_Headers_Mobile.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).

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

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

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

Your title is 75 characters, so Google will cut it off around 60: “לימור – מומחים למוצרי ספיגה והיגיינה למבוגרים, שיחת ייעוץ ללא עלות – Limore”.

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

Your meta description is only 6 characters: “Limore”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Limore” and “Limore”). One clear main headline is easier for people and search engines.

The homepage links to 145 pages on limore.co.il and 4 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.

Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://limore.co.il/collections/%D7%97%D7%99%D7%AA%D7%95%D7%9C%D7%99%D7%9D-%D7%9C%D7%9E%D7%91%D7%95%D7%92%D7%A8%D7%99%D7%9D, whose canonical is https://limore.co.il/collections/%d7%97%d7%99%d7%aa%d7%95%d7%9c%d7%99%d7%9d-%d7%9c%d7%9e%d7%91%d7%95%d7%92%d7%a8%d7%99%d7%9d. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://limore.co.il/collections/%D7%9E%D7%95%D7%A6%D7%A8%D7%99-%D7%97%D7%99%D7%98%D7%95%D7%99-%D7%95%D7%A0%D7%99%D7%A7%D7%95%D7%99-%D7%94%D7%91%D7%99%D7%AA and https://limore.co.il/collections use the same meta description. A description written for each page earns more clicks.

https://limore.co.il/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

https://limore.co.il/pages/contact, https://limore.co.il/collections/%D7%AA%D7%97%D7%AA%D7%95%D7%A0%D7%99%D7%95%D7%AA-%D7%95%D7%AA%D7%97%D7%91%D7%95%D7%A9%D7%95%D7%AA-%D7%9C%D7%A0%D7%A9%D7%99%D7%9D, https://limore.co.il/collections/%D7%9E%D7%92%D7%9F-%D7%9E%D7%96%D7%A8%D7%95%D7%9F-%D7%95%D7%A1%D7%93%D7%99%D7%A0%D7%99%D7%95%D7%AA, https://limore.co.il/collections/%D7%9E%D7%95%D7%A6%D7%A8%D7%99-%D7%A4%D7%90%D7%A8%D7%9D, https://limore.co.il/collections/%D7%9E%D7%92%D7%91%D7%95%D7%A0%D7%99%D7%9D-%D7%A1%D7%99%D7%A0%D7%A8%D7%99%D7%9D-%D7%95%D7%A1%D7%A4%D7%95%D7%92%D7%99-%D7%A8%D7%97%D7%A6%D7%94 and https://limore.co.il/collections/%D7%A7%D7%A8%D7%9E%D7%99%D7%9D-%D7%98%D7%99%D7%A4%D7%95%D7%9C%D7%99%D7%99%D7%9D and 5 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 52 found) and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

Social proof on the homepage: 23 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 117 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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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, 1 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.