Website review, no card needed

bateel.com logo

bateel.com website review

Visit site (opens in a new tab)Reviewed 30 October 202647 issues · 97 checks

This review found 47 issues worth fixing on bateel.com, 21 of them high impact, across 97 checks. The most urgent: reduce unused JavaScript. 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
4.2 s2.8 sMay 9Oct 243.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.8 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20263.9 s
Jun 27, 20263.5 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.3 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.1 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
180 ms126 msMay 9Oct 24174 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026134 ms
May 16, 2026136 ms
May 23, 2026137 ms
May 30, 2026138 ms
Jun 6, 2026140 ms
Jun 13, 2026143 ms
Jun 20, 2026146 ms
Jun 27, 2026146 ms
Jul 4, 2026145 ms
Jul 11, 2026144 ms
Jul 18, 2026137 ms
Jul 25, 2026132 ms
Aug 1, 2026132 ms
Aug 8, 2026135 ms
Aug 15, 2026137 ms
Aug 22, 2026139 ms
Aug 29, 2026137 ms
Sep 5, 2026137 ms
Sep 12, 2026140 ms
Sep 19, 2026139 ms
Sep 26, 2026145 ms
Oct 3, 2026153 ms
Oct 10, 2026159 ms
Oct 17, 2026170 ms
Oct 24, 2026174 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 bateel.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bateel.com at 1.6 s1.6 s
  2. bateel.com at 3.2 s3.2 s
  3. bateel.com at 4.8 s4.8 s
  4. bateel.com at 6.4 s6.4 s
  5. bateel.com at 8.0 s8.0 s
  6. bateel.com at 9.6 s9.6 s
  7. bateel.com at 11.2 s11.2 s
  8. bateel.com at 12.8 s12.8 s

Speed

11 to fix52
  • Reduce unused JavaScript

    1.5 s · 748 KiB

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

  • Render-blocking requests

    2.2 s

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

  • Main-thread work: 4.8 s

    A phone's processor spends 4.8 s on main-thread work while loading, 3.1 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 (gumlet.io, posthog.com and Facebook and others), adding 3.2 MB and 1.5 s of main-thread time.

  • Mobile performance score: 52

    52/100

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

  • Reduce unused CSS

    740 ms · 218 KiB

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

  • Improve image delivery

    450 ms · 468 KiB

    12 images could be 468 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.

  • gumlet.io adds 585 ms

    585 ms

    gumlet.io costs a phone 585 ms of main-thread work and 2.2 MB 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

    400 ms · 399 KiB

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

  • posthog.com adds 377 ms

    377 ms

    posthog.com costs a phone 377 ms of main-thread work and 227 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.

  • 1,767 HTML elements

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

  • 8 long tasks on the main thread

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

  • Duplicated JavaScript

    150 ms · 7 KiB

    7 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    64 KiB

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 13.0 s

    13.0 s

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

  • Time to Interactive: 21.5 s

    21.5 s

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

  • Speed Index: 11.5 s

    11.5 s

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

  • Real-user CLS: 0.14

    0.14

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

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

    +27%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.124

    0.124

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

  • Total Blocking Time: 264 ms

    264 ms

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

  • 1 image without width and height

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

5 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 155 ms

    155 ms

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 530 ms

    530 ms

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

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

    -14%

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

Images and page weight

2 to fix64
  • Page weight: 4.0 MB in 475 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 475 requests on a phone: scripts 2.4 MB (324), images 1.1 MB (53) and fonts 246 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    september_headerbanner_mobile_850x934-pastel_e__1.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).

  • About 1.1 g of CO₂ per visit

    1.14 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

14 to fixGoogle 5580
  • 3 buttons without a name

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

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • Orphan list items

    Some list items are not inside a list.

  • 3 text elements with low contrast

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

  • 3 tap targets too small

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

  • Malformed lists

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

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

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

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

  • 14 links without text

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

  • 6 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h5), 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. (6 elements).

1 checks passed
  • 46 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: 46 passed and 14 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8595
  • 20 links crawlers can't follow

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

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 180 internal links, 9 external

    The homepage links to 180 pages on bateel.com and 9 external pages.

7 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Welcome to the luxurious world of Bateel. Shop the finest organic dates, gifts and gourmet products | Express Internati…”.

  • One H1 headline

    Your main headline reads: “The World's Finest Organic Dates, Artisan Chocolates and Luxury Gift Boxes”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Bateel | Organic Dates and Luxury Gifts | Shop Online”.

  • Canonical URL set

    The canonical URL is https://bateel.com/en_us/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://bateel.com/sitemaps/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://bateel.com/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.

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

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (865 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 3 pages without a meta description

    https://bateel.com/en_us/price-below-hundred, https://bateel.com/en_us/from-hundred-to-two-hundred and https://bateel.com/en_us/two-hundred-to-three-hundred have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://bateel.com/en_us/contact-us, whose canonical is https://bateel.com/en/contact. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://bateel.com/en_us/gifts/chest-drawers has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://bateel.com/en_us/birthday-gifts took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343232332&tm=gtm002&Ver=2&mid=ce5e7fa5-ed31-4b0c-8e89-fcb5f5471041&bo=4&sid=79f8e360d4b111f18cfd51ab8e162c50&vid=79f90c80d4b111f18742431c4bd09c36&vids=0&msclkid=N&pi=9.

  • 1 third-party cookie

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “require is not defined”.

  • 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

    81 of 97 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • About 664 words of copy

    The homepage carries about 664 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Call Us”, “Shop Organic Dates” and “Shop Collection”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics, PostHog and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 35 cookies set on arrival

    35

    Opening the homepage sets 35 cookies (measured from a US location before any click).

  • 29 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 bateel.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Magento
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on bateel.com, including 21 speed issues, 2 SEO issues and 2 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