Website review, no card needed

babtain.com logo

babtain.com website review

Visit site (opens in a new tab)Reviewed 26 October 202634 issues · 85 checks

This review found 34 issues worth fixing on babtain.com, 10 of them high impact, across 85 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
1.8 s1.4 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
102 ms87 msMay 2Oct 1795 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202694 ms
May 9, 202694 ms
May 16, 202695 ms
May 23, 202695 ms
May 30, 202692 ms
Jun 6, 202694 ms
Jun 13, 202695 ms
Jun 20, 202692 ms
Jun 27, 202689 ms
Jul 4, 202692 ms
Jul 11, 202694 ms
Jul 18, 202694 ms
Jul 25, 2026100 ms
Aug 1, 2026100 ms
Aug 8, 202699 ms
Aug 15, 202698 ms
Aug 22, 202696 ms
Aug 29, 202696 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 202694 ms
Sep 26, 202692 ms
Oct 3, 202694 ms
Oct 10, 202697 ms
Oct 17, 202695 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 babtain.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. babtain.com at 0.4 s0.4 s
  2. babtain.com at 0.8 s0.8 s
  3. babtain.com at 1.1 s1.1 s
  4. babtain.com at 1.5 s1.5 s
  5. babtain.com at 1.9 s1.9 s
  6. babtain.com at 2.3 s2.3 s
  7. babtain.com at 2.6 s2.6 s
  8. babtain.com at 3.0 s3.0 s

Speed

7 to fix62
  • Reduce unused JavaScript

    1.4 s · 235 KiB

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

  • 3,179 HTML elements

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 97). Pages that score under 90 lose visitors before the first paint.

  • 5 third-party services on the page

    5 third-party services load with your homepage (cloudfront.net, Google Tag Manager and netdirector.auto and others), adding 1.4 MB and 453 ms of main-thread time.

  • Reduce unused CSS

    460 ms · 105 KiB

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

  • cloudfront.net adds 269 ms

    269 ms

    cloudfront.net costs a phone 269 ms of main-thread work and 696 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.

  • NetDirector adds 0 ms

    0 ms

    NetDirector costs a phone 0 ms of main-thread work and 435 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

    150 ms · 21 KiB

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

  • Font display

    100 ms

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

  • 6 long tasks on the main thread

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

  • Phones get a much slower page than desktops

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

  • Legacy JavaScript

    10 KiB

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

  • Improve image delivery

    6 KiB

    1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 796 ms of it running JavaScript. That is comfortably low.

  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 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.

  • Largest Contentful Paint: 9.0 s

    9.0 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Time to Interactive: 9.1 s

    9.1 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Real-user CLS: 0.20

    0.20

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

  • Real-user TTFB: 866 ms

    866 ms

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

  • 76 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 94 ms

    94 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Total Blocking Time: 108 ms

    108 ms

    Scripts block the page for only 108 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • 1 image below the first screen load straight away

    1 image further down the page (25 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.4 g of CO₂ per visit

    0.41 g

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

3 checks passed
  • Page weight: 1.4 MB in 140 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 140 requests on a phone: scripts 631 KiB (76), images 618 KiB (51) and stylesheets 112 KiB (2). That is a lean page.

  • 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

7 to fixGoogle 6386
  • 7 tap targets too small

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

  • 25 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 7 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 30 automated accessibility rules passed

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

SEO

3 to fixGoogle 8588
  • 3 H1 headlines

    There are 3 <h1> headlines (“70+ years”, “Al Babtain News & Events” and “Our Brands”). One clear main headline is easier for people and search engines.

  • Meta description is long (199 characters)

    Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 20 links with vague text

    20 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 94 internal links, 20 external

    The homepage links to 94 pages on babtain.com and 20 external pages.

5 checks passed
  • Title: 38 characters

    Your title is a healthy 38 characters: “Al Babtain Group | Kuwait | Al Babtain”.

  • Canonical URL set

    The canonical URL is https://www.babtain.com/.

  • Structured data in place

    Structured data found: Organization, WebPage 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://www.babtain.com/sitemap.xml.gz.

AI search readiness

100
  • No llms.txt

    There is no https://www.babtain.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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix79
  • 2 linked pages hidden from search

    https://www.babtain.com/contact-us and https://www.babtain.com/contact-us/enquiry are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 9 pages share 3 titles

    /, https://www.babtain.com/real-estate, https://www.babtain.com/technology, https://www.babtain.com/industrial and https://www.babtain.com/locations all use the title “Al Babtain Group | Kuwait | Al Babtain”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages share a meta description

    https://www.babtain.com/contact-us/nissan-intelliegent-choice-cpo and https://www.babtain.com/contact-us/omoda-al-babtain-showroom use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://www.babtain.com/contact-us, https://www.babtain.com/businesses, https://www.babtain.com/automotive, https://www.babtain.com/automotive/new-vehicles, https://www.babtain.com/automotive/parts-and-services and https://www.babtain.com/locations and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 55 small tap targets

    55 of 139 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Failed to execute 'querySelector' on 'Document': '> .cycle-pager' is not a valid selector.”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 36 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 744 words of copy

    The homepage carries about 744 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call” and “CONTACT US”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact”, “Join us on LinkedIn” and “Join us on Facebook”.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

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

  • 7 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on babtain.com, including 15 speed issues, 3 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