Website review, no card needed
nutanvastra.in website review
Visit site (opens in a new tab)Reviewed 16 November 202630 issues · 77 checks
This review found 30 issues worth fixing on nutanvastra.in, 11 of them high impact, across 77 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
83B- #25,583 of 110,818 reviewed websitesbeats 72%
- #16,940 of 63,136 online storesbeats 67%
- #16,435 of 57,638 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 152 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 156 ms |
| Aug 1, 2026 | 168 ms |
| Aug 8, 2026 | 167 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 165 ms |
| Sep 5, 2026 | 165 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 166 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 169 ms |
| Oct 24, 2026 | 160 ms |
| Oct 31, 2026 | 160 ms |
| Nov 7, 2026 | 160 ms |
| Nov 14, 2026 | 153 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.3 s
2.7 s
4.0 s
5.3 s
6.6 s
8.0 s
9.3 s
10.6 s
Speed
Improve image delivery
3.3 s · 1.0 MB16 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
350 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Reduce unused CSS
300 ms · 49 KiBAbout 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,420 HTML elements
The page has 2,420 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
2 third-party services on the page
2 third-party services load with your homepage (Shopify and shop.app), adding 143 KiB and 48 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.
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.
Use efficient cache lifetimes
3 KiB2 files are served with short cache lifetimes, so returning visitors download them again (3 KiB).
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 371 ms of it running JavaScript. That is comfortably low.
Server response: 12 ms
12 msYour server sent the HTML in 12 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: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 9.8 s
9.8 sThe page becomes fully interactive after 9.8 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 892 ms
892 msReal visitors wait 892 ms for your server to start answering (75th percentile). Good is under 800 ms.
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.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 161 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Total Blocking Time: 4 ms
4 msScripts block the page for only 4 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.9 MB in 216 requests
4.9 MBYour homepage downloads 4.9 MB in 216 requests on a phone: images 3.5 MB (27), other files 732 KiB (75) and scripts 332 KiB (105). Under 2 MB keeps phones on slow connections fast.
13 images below the first screen load straight away
13 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (335 KiB) 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 1.4 g of CO₂ per visit
1.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 167.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Hidden but focusable
7 elements hidden from screen readers can still receive keyboard focus.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 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: 48 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (220 characters)
Your meta description is 220 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
105 internal links, 2 external
The homepage links to 105 pages on nutanvastra.in and 2 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Nutan Vastra”.
Title: 36 characters
Your title is a healthy 36 characters: “Nutan Vastra - Online Clothing Store”.
Canonical URL set
The canonical URL is https://nutanvastra.in/.
Structured data in place
Structured data found: Organization.
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://nutanvastra.in/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 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 (796 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://nutanvastra.in/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages point its canonical at the homepage
https://nutanvastra.in/products/cotton-long-straight-kurta-7 and https://nutanvastra.in/products/handloom-ikkat-long-straight-kurti declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
3 pages share a title
/, https://nutanvastra.in/products/cotton-long-straight-kurta-7 and https://nutanvastra.in/products/handloom-ikkat-long-straight-kurti all use the title “Nutan Vastra - Online Clothing Store”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://nutanvastra.in/collections/all, https://nutanvastra.in/collections/cotton-suit-sets, https://nutanvastra.in/pages/contact, https://nutanvastra.in/collections/anarkali-kurti-sets, https://nutanvastra.in/collections/cotton-short-kurtis and https://nutanvastra.in/collections/slub-cotton-kurtas and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://nutanvastra.in/collections, https://nutanvastra.in/products/cotton-long-straight-kurta-7 and https://nutanvastra.in/products/handloom-ikkat-long-straight-kurti use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://nutanvastra.in/collections/anarkali-kurti-sets, https://nutanvastra.in/collections/cotton-short-kurtis, https://nutanvastra.in/collections/slub-cotton-kurtas, https://nutanvastra.in/collections/co-ord-sets and https://nutanvastra.in/products/cotton-kalamkari-long-straight-kurtis have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://nutanvastra.in/collections/slub-cotton-kurtas and https://nutanvastra.in/collections/co-ord-sets have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
3 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
17 of 19 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 6 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 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 271 words of copy
The homepage carries about 271 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”.
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “SHOP NOW” and “Subscribe”.
18 short forms
18 short forms (1 field at most) are right on the homepage, asking for an email.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 nutanvastra.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
King Product Options · Judge Me Reviews
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on nutanvastra.in, including 11 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.