Website review, no card needed

kravitz.co.il logo

kravitz.co.il website review

Visit site (opens in a new tab)Reviewed 20 October 202646 issues · 104 checks

This review found 46 issues worth fixing on kravitz.co.il, 21 of them high impact, across 104 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.4 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
679 ms78 msMay 2Oct 17163 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026570 ms
May 9, 2026599 ms
May 16, 2026610 ms
May 23, 2026609 ms
May 30, 2026496 ms
Jun 6, 2026319 ms
Jun 13, 2026193 ms
Jun 20, 2026154 ms
Jun 27, 2026147 ms
Jul 4, 2026147 ms
Jul 11, 2026147 ms
Jul 18, 2026147 ms
Jul 25, 2026147 ms
Aug 1, 2026149 ms
Aug 8, 2026154 ms
Aug 15, 2026158 ms
Aug 22, 2026162 ms
Aug 29, 2026163 ms
Sep 5, 2026162 ms
Sep 12, 2026161 ms
Sep 19, 2026156 ms
Sep 26, 2026155 ms
Oct 3, 2026160 ms
Oct 10, 2026161 ms
Oct 17, 2026163 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of kravitz.co.il (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kravitz.co.il at 0.5 s0.5 s
  2. kravitz.co.il at 1.1 s1.1 s
  3. kravitz.co.il at 1.6 s1.6 s
  4. kravitz.co.il at 2.1 s2.1 s
  5. kravitz.co.il at 2.6 s2.6 s
  6. kravitz.co.il at 3.2 s3.2 s
  7. kravitz.co.il at 3.7 s3.7 s
  8. kravitz.co.il at 4.2 s4.2 s

kravitz.co.il does not allow embedding, so this is Google's rendering of the page.

Speed

11 to fix34
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 5.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and Google CDN and others), adding 1.4 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    770 ms · 599 KiB

    About 599 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.

  • Google Tag Manager adds 601 ms

    601 ms

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

  • Improve image delivery

    546 KiB

    16 images could be 546 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 11 long tasks on the main thread

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

  • 2,256 HTML elements

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

  • Google CDN adds 163 ms

    163 ms

    Google CDN costs a phone 163 ms of main-thread work and 347 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.

  • Shopify adds 46 ms

    46 ms

    Shopify costs a phone 46 ms of main-thread work and 327 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.

  • Use efficient cache lifetimes

    45 KiB

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

  • Minify JavaScript

    36 KiB

    36 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    18 KiB

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

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Time to Interactive: 20.4 s

    20.4 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “לוגו של קרביץ”.

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Total Blocking Time: 838 ms

    838 ms

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Cumulative Layout Shift: 0.257

    0.257

    The layout shifts by 0.257 while loading, so content jumps under the reader's thumb. Good is under 0.1.

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 171 ms

    171 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 594 ms

    594 ms

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

  • Tap response (INP) got 72% faster for real visitors

    -72%

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

Images and page weight

5 to fix25
  • Page weight: 4.6 MB in 398 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 398 requests on a phone: scripts 1.6 MB (81), other files 1.3 MB (226) and images 1.3 MB (44). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    contigo-02_1.webp weighs 508 KiB. On a phone connection a single image that size takes seconds.

  • 14 images in older formats

    14 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.

  • An image on the first screen is lazy-loaded

    PS_banner_mobile_bf9c7bd8-1160-452a-abb0-14735b6b9960.webp 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).

  • 6 images far larger than shown

    156 KiB

    6 images are downloaded at several times the size a phone draws them, for example september_26_c040e6b0-5bd4-4985-8d80-331f89c67a3e.webp at 359 px wide, shown at 106 px. Resized copies would save about 156 KiB.

  • About 1.3 g of CO₂ per visit

    1.29 g

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

Accessibility

9 to fixGoogle 8588
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Positive tabindex

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

  • 1 text element with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

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

  • All page content should be contained by landmarks (1 element)

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

  • 8 links without text

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

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9281
  • No H1 headline

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

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “ציוד משרדי וטכנולוגיה ברכישה אונליין - קרביץ החברה המובילה והותיקה”.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • 354 internal links, 5 external

    The homepage links to 354 pages on kravitz.co.il and 5 external pages.

6 checks passed
  • Meta description: 110 characters

    Your meta description is 110 characters: “קרביץ, החברה המובילה והותיקה בישראל לציוד משרדי, וטכנולוגיה . באתר תוכלו לקבל את כל המידע ולבצע רכישה ומשלוחים”.

  • Canonical URL set

    The canonical URL is https://www.kravitz.co.il/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.kravitz.co.il/sitemap.xml.

AI search readiness

100
3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes /llms.txt (5 KiB, 5 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix63
  • 1 page without a title

    /customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    /customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 11 pages without a meta description

    /collections/all, /customer_authentication/redirect, /collections/%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D-%D7%91%D7%9E%D7%91%D7%A6%D7%A2, /collections/%D7%9E%D7%9B%D7%95%D7%A0%D7%95%D7%AA-%D7%9E%D7%A9%D7%A8%D7%93%D7%99%D7%95%D7%AA-%D7%95%D7%9E%D7%AA%D7%9B%D7%9C%D7%99%D7%9D, /collections/inks-toners and /collections/%D7%9E%D7%93%D7%A4%D7%A1%D7%95%D7%AA-%D7%9C%D7%99%D7%99%D7%96%D7%A8-%D7%9E%D7%A9%D7%95%D7%9C%D7%91%D7%95%D7%AA and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example /collections/%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D-%D7%91%D7%9E%D7%91%D7%A6%D7%A2, whose canonical is /collections/%d7%9e%d7%95%d7%a6%d7%a8%d7%99%d7%9d-%d7%91%d7%9e%d7%91%d7%a6%d7%a2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    /customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    /collections/%D7%9E%D7%9B%D7%95%D7%A0%D7%95%D7%AA-%D7%9C%D7%9E%D7%99%D7%A0%D7%A6%D7%99%D7%94 and /collections/%D7%A1%D7%95%D7%A8%D7%A7-%D7%9E%D7%A9%D7%A8%D7%93%D7%99 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.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

2 checks passed
  • Tap targets are thumb-sized

    59 of 62 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 1 link through redirect chains

    1 link go through two or more redirects, for example https://www.kravitz.co.il/customer_authentication/redirect?locale=he&region_country=IL.

  • No Referrer-Policy

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

  • No Permissions-Policy

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

  • Deprecated X-XSS-Protection

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

  • No security.txt

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

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (kravitz.co.il).

  • Valid certificate (81 days left)

    The certificate from Let's Encrypt · YE1 verifies for kravitz.co.il and is valid for another 81 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://kravitz.co.il redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 45 links work

    All 45 links checked from your homepage (40 internal, 5 external) answered without errors.

Domain and trust

  • No CAA record

    kravitz.co.il has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

4 to fix50
  • No call to action on the first screen

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

  • No calls to action

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

  • No social proof

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

  • Only about 35 words

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

  • No risk reducer

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

3 checks passed
  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Email authentication

1 to fix75
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be kravitz.co.il is still delivered. Reports are on, so moving to quarantine is the next step.

  • Email authentication score: 75/100

    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.

2 checks passed
  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 a mx ip4:173.243.135.128 ip4:212.199.157.84 ip4:85.64.214.178 ip4:212.199.157.66 include:_spf.activetrail.com in…”.

  • DKIM signing found

    A DKIM key is published (selector “selector1”, “s1” and “s2”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 mores (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.

  • 20 cookies set on arrival

    20

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

  • No consent tool detected

    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.

  • 47 other companies contacted

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

Upkeep, stack and company

  • It loads jQuery 2.2.4, older than 3.5 (which fixed known security holes).

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This free review found 46 issues on kravitz.co.il, including 17 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25