Website review, no card needed
sanasafinaz.com website review
Visit site (opens in a new tab)Reviewed 1 November 202639 issues · 86 checks
This review found 39 issues worth fixing on sanasafinaz.com, 15 of them high impact, across 86 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
74C- #86,601 of 123,940 reviewed websitesbeats 26%
- #54,458 of 69,726 online storesbeats 18%
- #51,163 of 63,424 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 255 ms |
| May 16, 2026 | 262 ms |
| May 23, 2026 | 334 ms |
| May 30, 2026 | 412 ms |
| Jun 6, 2026 | 511 ms |
| Jun 13, 2026 | 588 ms |
| Jun 20, 2026 | 590 ms |
| Jun 27, 2026 | 587 ms |
| Jul 4, 2026 | 609 ms |
| Jul 11, 2026 | 638 ms |
| Jul 18, 2026 | 668 ms |
| Jul 25, 2026 | 678 ms |
| Aug 1, 2026 | 674 ms |
| Aug 8, 2026 | 686 ms |
| Aug 15, 2026 | 703 ms |
| Aug 22, 2026 | 713 ms |
| Aug 29, 2026 | 723 ms |
| Sep 5, 2026 | 721 ms |
| Sep 12, 2026 | 711 ms |
| Sep 19, 2026 | 707 ms |
| Sep 26, 2026 | 697 ms |
| Oct 3, 2026 | 680 ms |
| Oct 10, 2026 | 657 ms |
| Oct 17, 2026 | 637 ms |
| Oct 24, 2026 | 629 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
1.9 s
2.9 s
3.9 s
4.8 s
5.8 s
6.8 s
7.8 s
Speed
Avoid multiple page redirects
13.7 sThe page goes through 2 redirects before it starts loading, costing about 13.7 s. Link and advertise the final URL directly.
Reduce unused JavaScript
4.8 s · 1,020 KiBAbout 1,020 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Main-thread work: 10.4 s
A phone's processor spends 10.4 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Facebook and others), adding 1.6 MB and 2.0 s of main-thread time.
Google Tag Manager adds 846 ms
846 msGoogle Tag Manager costs a phone 846 ms of main-thread work and 532 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.
Improve image delivery
629 KiB6 images could be 629 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
621 KiB239 files are served with short cache lifetimes, so returning visitors download them again (621 KiB).
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 526 ms. During a long task the page ignores taps.
Shopify adds 299 ms
299 msShopify costs a phone 299 ms of main-thread work and 237 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.
Facebook adds 294 ms
294 msFacebook costs a phone 294 ms of main-thread work and 230 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.
Document request latency
300 msThe HTML itself could arrive about 300 ms sooner: redirects, a slow server response or missing compression delay everything after it.
2,813 HTML elements
The page has 2,813 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
azurefd.net adds 76 ms
76 msazurefd.net costs a phone 76 ms of main-thread work and 451 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.
Render-blocking requests
200 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 ms.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
12 KiB12 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 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: 25.2 s
25.2 sYour largest element takes 25.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “In Pakistan, a flat fee of PKR 250 applies to all orders. F…”.
Time to Interactive: 33.9 s
33.9 sThe page becomes fully interactive after 33.9 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.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Real-user INP: 327 ms
327 msReal visitors wait 327 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 145% slower for real visitors
+145%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 255 ms to 629 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.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 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: 732 ms
732 msReal visitors wait 732 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.4 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).
Images and page weight
Page weight: 9.0 MB in 767 requests
9.0 MBYour homepage downloads 9.0 MB in 767 requests on a phone: images 3.8 MB (263), scripts 3.3 MB (192) and other files 1.3 MB (249). Under 2 MB keeps phones on slow connections fast.
About 2.5 g of CO₂ per visit
2.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.55 g of CO₂e: 306.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Top Women's Fashion in Pakistan | Shop Latest Styles Online – Sana Safinaz”.
Structured data has 2 problems
Structured data found (LocalBusiness, Organization, Service and WebSite) but with 2 problems, for example “Service: missing name”.
One H1 headline
Your <h1> is empty.
286 internal links, 7 external
The homepage links to 286 pages on sanasafinaz.com and 7 external pages.
5 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Discover one of the best women clothing brands in Pakistan. You can shop unstitched suits, ready-to-wear, and luxury st…”.
Canonical URL set
The canonical URL is https://sanasafinaz.com/.
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://sanasafinaz.com/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 (806 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://sanasafinaz.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://sanasafinaz.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://sanasafinaz.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://sanasafinaz.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://sanasafinaz.com/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 134 found) and read each the way a search engine does.
2 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.
Best practices
20 small tap targets
20 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 370 words of copy
The homepage carries about 370 words of visible text.
7 checks passed
6 calls to action
The homepage has 6 calls to action, for example “View all Shop By Category”, “Shop By Category” and “Contact Us”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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, 1 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.
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 sanasafinaz.com, 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 Tag Manager | 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 39 issues on sanasafinaz.com, including 23 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.