Website review, no card needed
naheed.pk website review
Visit site (opens in a new tab)Reviewed 23 October 202651 issues · 87 checks
This review found 51 issues worth fixing on naheed.pk, 24 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
55F- #122,949 of 124,051 reviewed websitesbeats 1%
- #69,623 of 69,761 online storesbeats 0%
- #709 of 725 Magento storesbeats 2%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.7 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 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.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 202 ms |
| May 9, 2026 | 202 ms |
| May 16, 2026 | 197 ms |
| May 23, 2026 | 194 ms |
| May 30, 2026 | 193 ms |
| Jun 6, 2026 | 194 ms |
| Jun 13, 2026 | 197 ms |
| Jun 20, 2026 | 201 ms |
| Jun 27, 2026 | 204 ms |
| Jul 4, 2026 | 206 ms |
| Jul 11, 2026 | 208 ms |
| Jul 18, 2026 | 208 ms |
| Jul 25, 2026 | 209 ms |
| Aug 1, 2026 | 203 ms |
| Aug 8, 2026 | 197 ms |
| Aug 15, 2026 | 192 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 189 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 203 ms |
| Sep 26, 2026 | 210 ms |
| Oct 3, 2026 | 212 ms |
| Oct 10, 2026 | 211 ms |
| Oct 17, 2026 | 211 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
Improve image delivery
4.3 s · 2.8 MB32 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.
Render-blocking requests
1.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 26
26/100Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,376 HTML elements
The page has 3,376 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, reddit and Clarity and others), adding 1.0 MB and 1.7 s of main-thread time.
Google Tag Manager adds 856 ms
856 msGoogle Tag Manager costs a phone 856 ms of main-thread work and 467 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.
Reduce unused JavaScript
450 ms · 402 KiBAbout 402 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
600 ms · 73 KiBAbout 73 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 539 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
261 KiB7 files are served with short cache lifetimes, so returning visitors download them again (261 KiB).
Legacy JavaScript
33 KiBPolyfills for old browsers add 33 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.
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: 108 ms
108 msYour server sent the HTML in 108 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.
Real-user CLS: 0.31
0.31For real visitors the layout shifts by 0.31 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 33.5 s
33.5 sYour largest element takes 33.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 34.9 s
34.9 sThe page becomes fully interactive after 34.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.494
0.494The layout shifts by 0.494 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 243 ms
243 msReal visitors wait 243 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 202 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 29.7 MB in 438 requests
29.7 MBYour homepage downloads 29.7 MB in 438 requests on a phone: media 19.4 MB (2), images 8.2 MB (98) and scripts 1.6 MB (219). Under 2 MB keeps phones on slow connections fast.
19 images far larger than shown
3.8 MB19 images are downloaded at several times the size a phone draws them, for example 1080_x_1080_1.jpg at 1,080 px wide, shown at 188 px. Resized copies would save about 3.8 MB.
3 images over 500 KB
3 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.
37 images in older formats
37 images (6.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.
21 images below the first screen load straight away
21 images further down the page (4.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 8.4 g of CO₂ per visit
8.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.40 g of CO₂e: 1008.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 buttons without a name
7 buttons have no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
25 images without alt text
25 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.
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.
44 links without text
44 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (149 characters)
Your title is 149 characters, so Google will cut it off around 60: “Naheed.pk - Online Shopping in Pakistan: Cosmetics, Groceries, Mobiles, Fashion, Electron…”.
Meta description is long (253 characters)
Your meta description is 253 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1,370 internal links, 14 external
The homepage links to 1,370 pages on naheed.pk and 14 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.naheed.pk/.
Structured data in place
Structured data found: WebPage and WebSite.
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.naheed.pk/pub/media/sitemap.xml.
AI search readiness
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 https://www.naheed.pk/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 (2,571 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://www.naheed.pk/shaadi-ke-rang, https://www.naheed.pk/groceries-pets/fresh-products, https://www.naheed.pk/groceries-pets/fresh-products/fruits, https://www.naheed.pk/groceries-pets/fresh-products/vegetables, https://www.naheed.pk/groceries-pets/fresh-products/meat-poultry and https://www.naheed.pk/groceries-pets/fresh-products/meat-poultry/chicken and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.naheed.pk/shaadi-ke-rang 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 199 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
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
67 of 73 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
About 420 words of copy
The homepage carries about 420 words of visible text.
5 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Track Order”, “Contact Us” and “Register”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel, Microsoft Clarity and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.
31 cookies set on arrival
31Opening the homepage sets 31 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.
24 other companies contacted
Loading the homepage contacts 24 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 naheed.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
- Magento
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on naheed.pk, including 23 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.