Website review, no card needed

isrotel.co.il logo

isrotel.co.il website review

Visit site (opens in a new tab)Reviewed 28 October 202645 issues · 101 checks

This review found 45 issues worth fixing on isrotel.co.il, 18 of them high impact, across 101 checks. The most urgent: google Tag Manager adds 1.8 s. 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
2.4 s2.1 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
441 ms369 msMay 9Oct 24433 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026388 ms
May 16, 2026385 ms
May 23, 2026380 ms
May 30, 2026378 ms
Jun 6, 2026379 ms
Jun 13, 2026379 ms
Jun 20, 2026381 ms
Jun 27, 2026386 ms
Jul 4, 2026387 ms
Jul 11, 2026386 ms
Jul 18, 2026382 ms
Jul 25, 2026379 ms
Aug 1, 2026377 ms
Aug 8, 2026384 ms
Aug 15, 2026395 ms
Aug 22, 2026404 ms
Aug 29, 2026415 ms
Sep 5, 2026419 ms
Sep 12, 2026417 ms
Sep 19, 2026419 ms
Sep 26, 2026414 ms
Oct 3, 2026418 ms
Oct 10, 2026421 ms
Oct 17, 2026421 ms
Oct 24, 2026433 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 isrotel.co.il (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. isrotel.co.il at 1.6 s1.6 s
  2. isrotel.co.il at 3.2 s3.2 s
  3. isrotel.co.il at 4.7 s4.7 s
  4. isrotel.co.il at 6.3 s6.3 s
  5. isrotel.co.il at 7.9 s7.9 s
  6. isrotel.co.il at 9.5 s9.5 s
  7. isrotel.co.il at 11.1 s11.1 s
  8. isrotel.co.il at 12.7 s12.7 s

Speed

15 to fix39
  • Google Tag Manager adds 1.8 s

    1.8 s

    Google Tag Manager costs a phone 1.8 s of main-thread work and 836 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 13.2 s

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

  • Render-blocking requests

    1.0 s

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

  • Mobile performance score: 39

    39/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and isrotel.com and others), adding 2.5 MB and 4.6 s of main-thread time.

  • Use efficient cache lifetimes

    800 ms · 1.3 MB

    50 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    900 ms · 225 KiB

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

  • isrotel.com adds 538 ms

    538 ms

    isrotel.com costs a phone 538 ms of main-thread work and 791 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.

  • TikTok adds 573 ms

    573 ms

    TikTok costs a phone 573 ms of main-thread work and 168 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.

  • 20 long tasks on the main thread

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

  • zoomengage.com adds 512 ms

    512 ms

    zoomengage.com costs a phone 512 ms of main-thread work and 197 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.

  • Facebook adds 467 ms

    467 ms

    Facebook costs a phone 467 ms of main-thread work and 316 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.

  • Font display

    350 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

  • 2,874 HTML elements

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

  • Improve image delivery

    150 ms · 75 KiB

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

  • Minify JavaScript

    79 KiB

    79 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    42 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 73 but mobile only 39. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 5 ms

    5 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 31.5 s

    31.5 s

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

  • Total Blocking Time: 4.3 s

    4.3 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • Largest Contentful Paint: 4.9 s

    4.9 s

    Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “רשת מלונות ישרוטל איתכם בכל חופשה שתבחרו”.

  • Real-user INP: 470 ms

    470 ms

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

  • Real-user TTFB: 873 ms

    873 ms

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

4 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.046

    0.046

    The layout barely moves while loading (CLS 0.046, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 8.4 MB in 192 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 192 requests on a phone: media 4.0 MB (1), scripts 2.8 MB (61) and images 863 KiB (62). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (31 KiB) is 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.

  • 2 images below the first screen load straight away

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

  • About 2.4 g of CO₂ per visit

    2.37 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 8184
  • Invalid ARIA attributes

    4 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

  • All page content should be contained by landmarks (38 elements)

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

  • 11 links without text

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (11 elements)

    ARIA role should be appropriate for the element: 11 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 9296
  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 4 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 187 internal links, 20 external

    The homepage links to 187 pages on isrotel.co.il and 20 external pages.

8 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “רשת מלונות ישרוטל: הבחירה הטובה ביותר למלונות בישראל. הזמינו עכשיו עם 5% הנחה בלעדית באתר ותהנו מחופשה בלתי נשכחת מצפון…”.

  • One H1 headline

    Your main headline reads: “רשת מלונות ישרוטל”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “מלונות בישראל: רשת מלונות ישרוטל - המובילה בישראל”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, SiteNavigationElement, WPFooter and WPHeader.

  • 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.isrotel.co.il/sitemap.

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: 6 of 6 facts

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

  • llms.txt published

    The site publishes https://www.isrotel.co.il/llms.txt (7 KiB, 66 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://www.isrotel.co.il/about-isrotel/about/digitalcheckin is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 9 pages with very little text

    https://www.isrotel.co.il/isrotel-hotels/isrotel-exclusive-collection, https://www.isrotel.co.il/isrotel-hotels/isrotel-design, https://www.isrotel.co.il/isrotel-hotels/isrotel-collection, https://www.isrotel.co.il/deals/isrotelspa, https://www.isrotel.co.il/deals/isrotelrest and https://www.isrotel.co.il/deals/isrotelfunday and 3 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.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6988
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    26 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix67
  • 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 social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Only about 16 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

5 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “The Shop”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 30 cookies set on arrival

    30

    Opening the homepage sets 30 cookies, 3 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.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at isrotel.co.il, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
1981
Headquarters
Tel Aviv

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on isrotel.co.il, including 23 speed issues, 2 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