Website review, no card needed
batik.com.pk website review
Visit site (opens in a new tab)Reviewed 22 October 202637 issues · 81 checks
This review found 37 issues worth fixing on batik.com.pk, 12 of them high impact, across 81 checks. The most urgent: avoid multiple page redirects. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80B- #46,406 of 118,024 reviewed websitesbeats 55%
- #30,897 of 67,072 online storesbeats 48%
- #29,726 of 61,156 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 152 ms |
| May 9, 2026 | 151 ms |
| May 16, 2026 | 149 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 158 ms |
| Jun 6, 2026 | 173 ms |
| Jun 13, 2026 | 199 ms |
| Jun 20, 2026 | 228 ms |
| Jun 27, 2026 | 228 ms |
| Jul 4, 2026 | 227 ms |
| Jul 11, 2026 | 227 ms |
| Jul 18, 2026 | 226 ms |
| Jul 25, 2026 | 223 ms |
| Aug 1, 2026 | 224 ms |
| Aug 8, 2026 | 232 ms |
| Aug 15, 2026 | 233 ms |
| Aug 22, 2026 | 235 ms |
| Aug 29, 2026 | 236 ms |
| Sep 5, 2026 | 236 ms |
| Sep 12, 2026 | 239 ms |
| Sep 19, 2026 | 244 ms |
| Sep 26, 2026 | 257 ms |
| Oct 3, 2026 | 274 ms |
| Oct 10, 2026 | 290 ms |
| Oct 17, 2026 | 297 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
Speed
Avoid multiple page redirects
4.2 sThe page goes through 2 redirects before it starts loading, costing about 4.2 s. Link and advertise the final URL directly.
Reduce unused JavaScript
2.1 s · 626 KiBAbout 626 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,249 HTML elements
The page has 3,249 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
300 ms · 1.3 MB18 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 50
50/100Your mobile performance score is 50 (desktop: 48). Pages that score under 90 lose visitors before the first paint.
gotolstoy.com adds 5 ms
5 msgotolstoy.com costs a phone 5 ms of main-thread work and 300 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 · 88 KiB5 files are served with short cache lifetimes, so returning visitors download them again (88 KiB).
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
6 third-party services on the page
6 third-party services load with your homepage (Shopify, gotolstoy.com and spicegems.org and others), adding 471 KiB and 59 ms of main-thread time.
Reduce unused CSS
30 ms · 31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 30 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Render-blocking requests
50 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 50 ms.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 36.7 s
36.7 sYour largest element takes 36.7 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 24.2 s
24.2 sVisually, the page fills in at 24.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 44.5 s
44.5 sThe page becomes fully interactive after 44.5 s. Good is under 3.8 s.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Tap response (INP) got 94% slower for real visitors
+94%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 152 ms to 297 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 268 ms
268 msScripts block taps and scrolling for 268 ms in total while the page loads. Good is under 200 ms.
5 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 187 ms
187 msReal visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Images and page weight
Page weight: 11.8 MB in 446 requests
11.8 MBYour homepage downloads 11.8 MB in 446 requests on a phone: images 7.9 MB (62), scripts 2.1 MB (138) and other files 1.2 MB (225). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Khizaan_Karandi_mobile_slider.jpg 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 3.3 g of CO₂ per visit
3.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.34 g of CO₂e: 400.7 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
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (24 characters)
Your title is only 24 characters: “BATIK | Official Website”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (250 characters)
Your meta description is 250 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("@batikstudio.pk")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
218 internal links, 4 external
The homepage links to 218 pages on batik.com.pk and 4 external pages.
4 checks passed
One H1 headline
Your main headline reads: “BATIK”.
Canonical URL set
The canonical URL is https://batik.com.pk/.
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://batik.com.pk/sitemap.xml.
AI search readiness
4 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,048 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://batik.com.pk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without a meta description
https://batik.com.pk/collections/khizaan-shades-of-fall-khaddar-edit, https://batik.com.pk/collections/eid-2026, https://batik.com.pk/collections/khizaan-karandi-edit, https://batik.com.pk/collections/cambric-pret-edit-ii, https://batik.com.pk/collections/midnight-muse-luxe-pret-redefined and https://batik.com.pk/collections/cambric-pret-a-fresh-chapter and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://batik.com.pk/collections/batik-new-arrivals-ready-to-wear, https://batik.com.pk/collections/khizaan-shades-of-fall-khaddar-edit, https://batik.com.pk/collections/eid-2026, https://batik.com.pk/collections/khizaan-karandi-edit, https://batik.com.pk/collections/cambric-pret-edit-ii and https://batik.com.pk/collections/paper-silk-edit-luxe-pret-redefined and 8 others 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 152 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
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.
Thin social proof
Social proof on the homepage: 16 trust badges. 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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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.
About 615 words of copy
The homepage carries about 615 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact us”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Snap Pixel (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.
15 cookies set on arrival
15Opening the homepage sets 15 cookies, 9 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.
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.
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 batik.com.pk, 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
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on batik.com.pk, including 16 speed issues, 4 SEO issues and 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.