redchilli.co.il website review

20 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.3 s faster on a phone.

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

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

About 393 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Facebook and glassix.com and others), adding 1.0 MB and 823 ms of main-thread time.

Google Tag Manager costs a phone 460 ms of main-thread work and 506 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.5 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

15 KiB could be saved by minifying JavaScript.

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.

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.

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

Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “אורך עדן1”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.1 MB in 176 requests on a phone: images 2.6 MB (29), scripts 1.2 MB (61) and fonts 148 KiB (8). Under 2 MB keeps phones on slow connections fast.

אורך-עדן1.png weighs 1.3 MB. On a phone connection a single image that size takes seconds.

13 images (2.3 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.

3 images are downloaded at several times the size a phone draws them, for example Asset-6.png at 554 px wide, shown at 60 px. Resized copies would save about 159 KiB.

8 images further down the page (354 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 element has a tabindex above 0, which scrambles the keyboard order.

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 98 pages on redchilli.co.il and 4 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://redchilli.co.il/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://redchilli.co.il/product-category/bedroom/jersey/bed-linen and https://redchilli.co.il/product-category/bedroom/%d7%91%d7%93%d7%99%d7%93%d7%99%d7%9d/%d7%a1%d7%93%d7%99%d7%a0%d7%99%d7%9d-%d7%91%d7%93%d7%99%d7%93%d7%99%d7%9d all use the title “קולקציית סדינים | Red Chilli - מותגים שאוהבים”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://redchilli.co.il/product-category/bedroom, https://redchilli.co.il/product-category/bedroom/cotton, https://redchilli.co.il/product-category/bedroom/jersey, https://redchilli.co.il/product-category/bedroom/jersey/bed-linen, https://redchilli.co.il/product-category/bedroom/jersey/%d7%a6%d7%99%d7%a4%d7%95%d7%aa-%d7%9e%d7%a6%d7%a2%d7%99-%d7%92%d7%a8%d7%a1%d7%99 and https://redchilli.co.il/product-category/bedroom/jersey/%d7%a6%d7%99%d7%a4%d7%99%d7%95%d7%aa and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://redchilli.co.il/product-category/bedroom/jersey/%d7%a6%d7%99%d7%a4%d7%95%d7%aa-%d7%9e%d7%a6%d7%a2%d7%99-%d7%92%d7%a8%d7%a1%d7%99, whose canonical is https://redchilli.co.il/product-category/bedroom/jersey/%D7%A6%D7%99%D7%A4%D7%95%D7%AA-%D7%9E%D7%A6%D7%A2%D7%99-%D7%92%D7%A8%D7%A1%D7%99. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://redchilli.co.il/product-category/bedroom/jersey/%d7%a6%d7%99%d7%a4%d7%95%d7%aa-%d7%9e%d7%a6%d7%a2%d7%99-%d7%92%d7%a8%d7%a1%d7%99 and https://redchilli.co.il/product-category/bedroom-kids/%d7%9e%d7%a6%d7%a2%d7%99-%d7%9e%d7%a2%d7%91%d7%a8-100-%d7%9b%d7%95%d7%aa%d7%a0%d7%94 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.

https://redchilli.co.il/product-category/bedroom/jersey, https://redchilli.co.il/product-category/bedroom/jersey/%d7%a6%d7%99%d7%a4%d7%95%d7%aa-%d7%9e%d7%a6%d7%a2%d7%99-%d7%92%d7%a8%d7%a1%d7%99, https://redchilli.co.il/product-category/bedroom/jersey/%d7%a6%d7%99%d7%a4%d7%99%d7%95%d7%aa, https://redchilli.co.il/product-category/bedroom/%d7%91%d7%93%d7%99%d7%93%d7%99%d7%9d and https://redchilli.co.il/product-category/bedroom-kids/%d7%9e%d7%a6%d7%a2%d7%99-%d7%9e%d7%a2%d7%91%d7%a8-100-%d7%9b%d7%95%d7%aa%d7%a0%d7%94 took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 (Bad Request)”.

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

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

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 32 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 25 cookies (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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.