Website review, no card needed
qmobile.com.pk website review
Visit site (opens in a new tab)Reviewed 3 November 202634 issues · 79 checks
This review found 34 issues worth fixing on qmobile.com.pk, 11 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. 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
74C- #87,459 of 125,363 reviewed websitesbeats 26%
- #54,759 of 70,167 online storesbeats 18%
- #51,412 of 63,754 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 173 ms |
| May 23, 2026 | 169 ms |
| May 30, 2026 | 168 ms |
| Jun 6, 2026 | 172 ms |
| Jun 13, 2026 | 172 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 160 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 166 ms |
| Aug 22, 2026 | 168 ms |
| Aug 29, 2026 | 170 ms |
| Sep 5, 2026 | 174 ms |
| Sep 12, 2026 | 176 ms |
| Sep 19, 2026 | 173 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 172 ms |
| Oct 10, 2026 | 176 ms |
| Oct 17, 2026 | 182 ms |
| Oct 24, 2026 | 187 ms |
| Oct 31, 2026 | 191 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
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
450 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
2,231 HTML elements
The page has 2,231 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 52 ms
52 msShopify costs a phone 52 ms of main-thread work and 303 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.
5 third-party services on the page
5 third-party services load with your homepage (Shopify, Klaviyo and powl.io and others), adding 390 KiB and 98 ms of main-thread time.
Improve image delivery
52 KiB2 images could be 52 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
37 KiBAbout 37 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
5 KiB2 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 545 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 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: 8.0 s
8.0 sYour largest element takes 8.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.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.1 s
8.1 sThe page becomes fully interactive after 8.1 s. Good is under 3.8 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 269 ms
269 msReal visitors wait 269 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 173 ms to 191 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 64 ms
64 msScripts block the page for only 64 ms while loading. Good is under 200 ms.
Images and page weight
5 images far larger than shown
813 KiB5 images are downloaded at several times the size a phone draws them, for example orangenew.webp at 713 px wide, shown at 33 px. Resized copies would save about 813 KiB.
Page weight: 2.2 MB in 216 requests
2.2 MBYour homepage downloads 2.2 MB in 216 requests on a phone: images 961 KiB (37), other files 750 KiB (83) and scripts 379 KiB (62). Under 2 MB keeps phones on slow connections fast.
17 images in older formats
17 images (1.7 MB) 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 0.6 g of CO₂ per visit
0.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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 (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h6, h1 → h3 and h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
50 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: 50 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
2 H1 headlines
There are 2 <h1> headlines (“” and “NEW LAUNCH”). One clear main headline is easier for people and search engines.
Meta description is long (287 characters)
Your meta description is 287 characters; Google truncates after about 160, so the end of your pitch is cut.
137 internal links, 11 external
The homepage links to 137 pages on qmobile.com.pk and 11 external pages.
6 checks passed
Title: 45 characters
Your title is a healthy 45 characters: “QMobile Pakistan's Leading Mobile phone brand”.
Canonical URL set
The canonical URL is https://qmobile.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://qmobile.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 (512 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://qmobile.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://qmobile.com.pk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
2 linked pages hidden from search
https://qmobile.com.pk/collections/all and https://qmobile.com.pk/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages without a meta description
https://qmobile.com.pk/collections/all, https://qmobile.com.pk/customer_authentication/redirect, https://qmobile.com.pk/collections/phone and https://qmobile.com.pk/pages/faqs have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://qmobile.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 31 found) and read each the way a search engine does.
3 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://qmobile.com.pk/.
8 small tap targets
8 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Requests the notification permission on page load
Requests the notification permission on page load.
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.
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.
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 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 258 words of copy
The homepage carries about 258 words of visible text.
3 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Track My Order”, “Contact” and “Register a claim”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 48 testimonial or review blocks and 2 trust badges.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
12 other companies contacted
Loading the homepage contacts 12 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 qmobile.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
- Hosting
- Shopify
Company
- Founded
- 2009
- Headquarters
- Karachi
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on qmobile.com.pk, including 14 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.