Website review, no card needed

batelco.com logo

batelco.com website review

Visit site (opens in a new tab)Reviewed 31 October 202650 issues · 94 checks

This review found 50 issues worth fixing on batelco.com, 23 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. 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
9.7 s7.7 sMay 9Oct 248.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20267.9 s
May 16, 20267.9 s
May 23, 20267.9 s
May 30, 20268.0 s
Jun 6, 20268.1 s
Jun 13, 20268.2 s
Jun 20, 20268.3 s
Jun 27, 20268.3 s
Jul 4, 20268.1 s
Jul 11, 20268.2 s
Jul 18, 20268.2 s
Jul 25, 20268.4 s
Aug 1, 20268.8 s
Aug 8, 20269.1 s
Aug 15, 20269.4 s
Aug 22, 20269.4 s
Aug 29, 20269.2 s
Sep 5, 20268.9 s
Sep 12, 20268.8 s
Sep 19, 20268.7 s
Sep 26, 20268.8 s
Oct 3, 20268.8 s
Oct 10, 20268.7 s
Oct 17, 20268.7 s
Oct 24, 20268.9 s
Real-visitor tap response (INP)75th percentile, phones
172 ms152 msMay 9Oct 24169 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026155 ms
May 16, 2026154 ms
May 23, 2026155 ms
May 30, 2026158 ms
Jun 6, 2026164 ms
Jun 13, 2026169 ms
Jun 20, 2026170 ms
Jun 27, 2026164 ms
Jul 4, 2026160 ms
Jul 11, 2026158 ms
Jul 18, 2026158 ms
Jul 25, 2026160 ms
Aug 1, 2026160 ms
Aug 8, 2026161 ms
Aug 15, 2026162 ms
Aug 22, 2026161 ms
Aug 29, 2026161 ms
Sep 5, 2026160 ms
Sep 12, 2026161 ms
Sep 19, 2026163 ms
Sep 26, 2026166 ms
Oct 3, 2026169 ms
Oct 10, 2026170 ms
Oct 17, 2026169 ms
Oct 24, 2026169 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 batelco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. batelco.com at 1.2 s1.2 s
  2. batelco.com at 2.3 s2.3 s
  3. batelco.com at 3.5 s3.5 s
  4. batelco.com at 4.6 s4.6 s
  5. batelco.com at 5.8 s5.8 s
  6. batelco.com at 6.9 s6.9 s
  7. batelco.com at 8.1 s8.1 s
  8. batelco.com at 9.2 s9.2 s

Speed

12 to fix40
  • Use efficient cache lifetimes

    10.8 s · 2.2 MB

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

  • Improve image delivery

    4.5 s · 2.4 MB

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

  • Reduce unused CSS

    5.2 s · 936 KiB

    About 936 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.2 s faster on a phone.

  • Render-blocking requests

    3.6 s

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

  • Reduce unused JavaScript

    2.5 s · 475 KiB

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

  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40. 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, Facebook and TikTok and others), adding 1.1 MB and 1.0 s of main-thread time.

  • Minify CSS

    760 ms · 118 KiB

    118 KiB could be saved by minifying CSS.

  • Google Tag Manager adds 496 ms

    496 ms

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

  • Minify JavaScript

    310 ms · 57 KiB

    57 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.3 s

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

  • 1,972 HTML elements

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 21 KiB

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

  • Document request latency

    144 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    100 ms

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

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

    366 ms

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

  • Real-user LCP: 9.2 s

    9.2 s

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

  • Real-user FCP: 9.4 s

    9.4 s

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

  • Real-user TTFB: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 38.0 s

    38.0 s

    Your largest element takes 38.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “One Plan. More control. More flexibility. More from your pl…”.

  • Speed Index: 19.5 s

    19.5 s

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

  • Time to Interactive: 38.7 s

    38.7 s

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

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Total Blocking Time: 678 ms

    678 ms

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

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

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

    +11%

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

3 checks passed
  • Real-user INP: 162 ms

    162 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix33
  • Page weight: 7.7 MB in 133 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 133 requests on a phone: images 4.9 MB (43), scripts 1.5 MB (30) and stylesheets 1,021 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    864 KiB

    5 images are downloaded at several times the size a phone draws them, for example image-10.webp at 2,560 px wide, shown at 170 px. Resized copies would save about 864 KiB.

  • 6 images below the first screen load straight away

    6 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images in older formats

    6 images (966 KiB) 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.

  • About 2.2 g of CO₂ per visit

    2.20 g

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

Accessibility

8 to fixGoogle 7287
  • 6 buttons without a name

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

  • 6 tap targets too small

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

  • 8 images without alt text

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

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

    All page content should be contained by landmarks: 14 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.

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

  • The skip-link target should exist and be focusable (1 element)

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

  • 6 links without text

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

  • Headings skip levels

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

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

2 to fixGoogle 8588
  • No H1 headline

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

  • 2 links crawlers can't follow

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

  • 394 internal links, 66 external

    The homepage links to 394 pages on batelco.com and 66 external pages.

7 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Batelco is Bahrain’s leading telecommunications provider, offering reliable mobile, Internet and Business connectivity …”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Batelco | Leading Telecom, Internet & Mobile Services Provider”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.batelco.com/wp-sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.batelco.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,452 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 3 linked pages hidden from search

    https://www.batelco.com/devicetradein, https://www.batelco.com/postpaid-world and https://www.batelco.com/mobile/esim are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 13 pages without a meta description

    https://www.batelco.com/support, https://www.batelco.com/insure, https://www.batelco.com/devicetradein, https://www.batelco.com/protect-plus, https://www.batelco.com/easy-payments and https://www.batelco.com/mobile/roaming and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.batelco.com/devicetradein, https://www.batelco.com/protect-plus, https://www.batelco.com/mobile/roaming, https://www.batelco.com/prepaid and https://www.batelco.com/esimcar have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.batelco.com/support, https://www.batelco.com/devicetradein, https://www.batelco.com/protect-plus, https://www.batelco.com/easy-payments and https://www.batelco.com/mobile/roaming took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 104 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

5 to fixGoogle 6969
  • 2 broken images

    2 images failed to load on a phone, for example https://batelco.com/wp-content/uploads/2025/01/Google-play.svg.

  • 8 small tap targets

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

  • 1 third-party cookie

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

  • 3 JavaScript errors while loading

    3 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”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix67
  • 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 210 words

    The homepage has only about 210 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 risk reducer

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe today” and “Shop now”.

  • 26 calls to action

    The homepage has 26 calls to action, for example “Start-ups”, “Global Contact Form” and “Business contact us”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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, LinkedIn Insight and Meta Pixel 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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 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.

  • 25 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
F5

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on batelco.com, including 22 speed issues, 2 SEO issues and 5 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