Website review, no card needed
generation.com.pk website review
Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 81 checks
This review found 40 issues worth fixing on generation.com.pk, 13 of them high impact, across 81 checks. The most urgent: page weight: 37.2 MB in 548 requests. 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
77C- #65,876 of 117,615 reviewed websitesbeats 39%
- #42,968 of 66,923 online storesbeats 31%
- #40,920 of 61,018 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.7 s |
| May 23, 2026 | 4.6 s |
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 188 ms |
| May 23, 2026 | 188 ms |
| May 30, 2026 | 179 ms |
| Jun 6, 2026 | 180 ms |
| Jun 13, 2026 | 182 ms |
| Jun 20, 2026 | 182 ms |
| Jun 27, 2026 | 183 ms |
| Jul 4, 2026 | 210 ms |
| Jul 11, 2026 | 218 ms |
| Jul 18, 2026 | 225 ms |
| Jul 25, 2026 | 228 ms |
| Aug 1, 2026 | 289 ms |
| Aug 8, 2026 | 351 ms |
| Aug 15, 2026 | 428 ms |
| Aug 22, 2026 | 499 ms |
| Aug 29, 2026 | 515 ms |
| Sep 5, 2026 | 536 ms |
| Sep 12, 2026 | 545 ms |
| Sep 19, 2026 | 561 ms |
| Sep 26, 2026 | 597 ms |
| Oct 3, 2026 | 608 ms |
| Oct 10, 2026 | 609 ms |
| Oct 17, 2026 | 615 ms |
| Oct 24, 2026 | 614 ms |
| Oct 31, 2026 | 616 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
How it loaded on a phone
1.0 s
2.1 s
3.1 s
4.2 s
5.2 s
6.2 s
7.3 s
8.3 s
Speed
Main-thread work: 17.5 s
A phone's processor spends 17.5 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,433 HTML elements
The page has 5,433 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
350 ms · 8.1 MB87 images could be 8.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, ContentSquare and Clarity and others), adding 1.9 MB and 1.5 s of main-thread time.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 826 ms
826 msGoogle Tag Manager costs a phone 826 ms of main-thread work and 1.0 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.
Render-blocking requests
850 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Reduce unused JavaScript
767 KiBAbout 767 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
308 KiB13 files are served with short cache lifetimes, so returning visitors download them again (308 KiB).
ContentSquare adds 268 ms
268 msContentSquare costs a phone 268 ms of main-thread work and 190 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 285 ms. During a long task the page ignores taps.
Shopify adds 114 ms
114 msShopify costs a phone 114 ms of main-thread work and 546 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
27 KiB27 KiB could be saved by minifying JavaScript.
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: 17 ms
17 msYour server sent the HTML in 17 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.
Time to Interactive: 18.4 s
18.4 sThe page becomes fully interactive after 18.4 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Real-user INP: 439 ms
439 msReal visitors wait 439 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 227% slower for real visitors
+227%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 188 ms to 616 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 614 ms
614 msReal visitors wait 614 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 59% faster for real visitors
-59%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.7 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 37.2 MB in 548 requests
37.2 MBYour homepage downloads 37.2 MB in 548 requests on a phone: media 22.4 MB (2), images 11.2 MB (127) and scripts 1.8 MB (127). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
803 KiB4 images are downloaded at several times the size a phone draws them, for example handcrafted_cc8589c1-1d46-4b64-8899-8b1d4cf73dfe.png at 1,200 px wide, shown at 195 px. Resized copies would save about 803 KiB.
About 10.6 g of CO₂ per visit
10.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.55 g of CO₂e: 1266.1 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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
92 tap targets too small
92 tap targets are too small or too close together to hit reliably with a finger.
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.
2 images without alt text
2 images have 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.
46 form fields without a label
46 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (54 elements).
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
42 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: 42 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
249 internal links, 8 external
The homepage links to 249 pages on generation.com.pk and 8 external pages.
7 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Discover ready-to-wear kurtas, matching 2-piece & 3-piece suits, handcrafted kurtas, and Anarkali suits. Shop premium s…”.
Title: 54 characters
Your title is a healthy 54 characters: “Pakistan's Pioneering Ready-to-Wear Label – GENERATION”.
Canonical URL set
The canonical URL is https://generation.com.pk/.
Structured data in place
Structured data found: Organization 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://generation.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: 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,483 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://generation.com.pk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://generation.com.pk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://generation.com.pk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://generation.com.pk/collections/all, https://generation.com.pk/customer_authentication/redirect and https://generation.com.pk/collections/festive-2026 have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://generation.com.pk/customer_authentication/redirect has 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 112 found) and read each the way a search engine does.
3 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
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.
Best practices
6 small tap targets
6 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 15-field form
Your longest form asks for 15 fields (0 required). Every extra field lowers completion.
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 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 618 words of copy
The homepage carries about 618 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: “SHOP NOW!”.
5 calls to action
The homepage has 5 calls to action, for example “Shop Now!”, “Track Your Order” and “Order”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Hotjar.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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
18Opening 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.
30 other companies contacted
Loading the homepage contacts 30 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 generation.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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 13 open roles
- Teams
- Regional COO, LatAm Function (5), Partnerships - Development (2), Curriculum & Instruction (1), Digital (1)
- Job board
- bamboohr
Company
- Employees
- 190
- Headquarters
- Lahore
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on generation.com.pk, including 21 speed issues, 2 SEO issues and 3 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.