Website review, no card needed

bata.com.pk logo

bata.com.pk website review

Visit site (opens in a new tab)Reviewed 2 November 202629 issues · 77 checks

This review found 29 issues worth fixing on bata.com.pk, 10 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.6 s2.3 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 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.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
334 ms238 msMay 16Oct 31254 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026309 ms
May 23, 2026311 ms
May 30, 2026313 ms
Jun 6, 2026316 ms
Jun 13, 2026323 ms
Jun 20, 2026321 ms
Jun 27, 2026322 ms
Jul 4, 2026319 ms
Jul 11, 2026299 ms
Jul 18, 2026282 ms
Jul 25, 2026268 ms
Aug 1, 2026258 ms
Aug 8, 2026257 ms
Aug 15, 2026256 ms
Aug 22, 2026256 ms
Aug 29, 2026256 ms
Sep 5, 2026254 ms
Sep 12, 2026259 ms
Sep 19, 2026258 ms
Sep 26, 2026258 ms
Oct 3, 2026256 ms
Oct 10, 2026250 ms
Oct 17, 2026249 ms
Oct 24, 2026251 ms
Oct 31, 2026254 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

3 to fix33
  • Fails Core Web Vitals for real visitors

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

  • Real-user CLS: 0.62

    0.62

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

  • Real-user INP: 254 ms

    254 ms

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 646 ms

    646 ms

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

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

    -19%

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

Images and page weight

2 to fix64
  • Page weight: 4.8 MB

    4.8 MB

    Your homepage downloads 4.8 MB on a phone, 1.1 MB of it images (22%). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    mobile_copy_c6c38f34-f92e-401d-b850-e035b0bbdb4b.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).

  • 3 images in older formats

    3 images (304 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 1.4 g of CO₂ per visit

    1.36 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 162.7 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

9 to fix88
  • 2 buttons without a name

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

  • 11 text elements with low contrast

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

  • 6 tap targets too small

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 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 (2 elements)

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 12 links without text

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

  • 2 form fields without a label

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

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 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 fix84
  • Title is short (13 characters)

    Your title is only 13 characters: “Bata Pakistan”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (280 characters)

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

  • 286 internal links, 13 external

    The homepage links to 286 pages on bata.com.pk and 13 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “.bt__header___logo .header__heading-logo { width: 100%; height: auto; display: block; max-width: 90px; } @media (min-wi…”.

  • Canonical URL set

    The canonical URL is https://www.bata.com.pk/.

  • 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.bata.com.pk/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no /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.

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

  • Text is in the HTML

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

Other pages

6 to fix55
  • 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.

  • 2 pages share a title

    /pages/fan-club and /pages/bata-club all use the title “Bata Club – Bata Pakistan”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    /collections/all, /customer_authentication/redirect, /policies/shipping-policy, /pages/fan-club and /pages/bata-club have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /pages/fan-club, whose canonical is /pages/bata-club. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    /collections/all, /customer_authentication/redirect, /pages/fan-club, /pages/bata-club and /collections/new-arrivals-kids 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 125 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

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

Best practices

1 to fix93
  • 19 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

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

  • 2 links through redirect chains

    2 links go through two or more redirects, for example https://www.bata.com.pk/customer_authentication/redirect?locale=en&region_country=PK.

  • 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 (bata.com.pk).

  • Valid certificate (79 days left)

    The certificate from Let's Encrypt · YE1 verifies for bata.com.pk and is valid for another 79 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://bata.com.pk 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 48 links work

    All 48 links checked from your homepage (40 internal, 8 external) answered without errors; 1 did not answer within 5 s.

Domain and trust

1 checks passed
  • Certificate issuers are restricted

    CAA records allow only globalsign.com, letsencrypt.org, pki.goog and ssl.com to issue certificates for bata.com.pk, so a mis-issued certificate from anyone else is refused.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 21 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 295 words of visible text.

4 checks passed
  • 25 calls to action

    The homepage has 25 calls to action, for example “Track Order”, “New New Arrival Shop The Latest Style” and “Bata Club Join. Earn. Enjoy.”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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 bata.com.pk is still delivered. Add a report address, check the reports, then move to quarantine.

  • 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 +a:host.hosttechno.com include:ncfp.asia include:170075225.spf2.netcorecloud.net include:146132ed5.spf2.n…”.

  • DKIM signing found

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

Privacy and tracking

1 to fix
  • 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 Clarity and 2 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.

  • 27 cookies set on arrival

    27

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 | Hotjar | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on bata.com.pk, including 3 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