Website review, no card needed

samantchauhan.com logo

samantchauhan.com website review

Visit site (opens in a new tab)Reviewed 9 November 202627 issues · 75 checks

This review found 27 issues worth fixing on samantchauhan.com, 6 of them high impact, across 75 checks. The most urgent: page weight: 24.8 MB in 376 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.3 s1.8 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.6 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20262.7 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.4 s
Oct 3, 20262.1 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
230 ms106 msMay 16Oct 31126 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026145 ms
May 23, 2026148 ms
May 30, 2026154 ms
Jun 6, 2026163 ms
Jun 13, 2026165 ms
Jun 20, 2026161 ms
Jun 27, 2026160 ms
Jul 4, 2026149 ms
Jul 11, 2026146 ms
Jul 18, 2026145 ms
Jul 25, 2026144 ms
Aug 1, 2026152 ms
Aug 8, 2026195 ms
Aug 15, 2026195 ms
Aug 22, 2026216 ms
Aug 29, 2026212 ms
Sep 5, 2026187 ms
Sep 12, 2026189 ms
Sep 19, 2026169 ms
Sep 26, 2026157 ms
Oct 3, 2026136 ms
Oct 10, 2026122 ms
Oct 17, 2026120 ms
Oct 24, 2026120 ms
Oct 31, 2026126 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

Full-page screenshot of samantchauhan.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. samantchauhan.com at 0.4 s0.4 s
  2. samantchauhan.com at 0.8 s0.8 s
  3. samantchauhan.com at 1.1 s1.1 s
  4. samantchauhan.com at 1.5 s1.5 s
  5. samantchauhan.com at 1.9 s1.9 s
  6. samantchauhan.com at 2.3 s2.3 s
  7. samantchauhan.com at 2.6 s2.6 s
  8. samantchauhan.com at 3.0 s3.0 s

Speed

7 to fix79
  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, JSDelivr CDN and Cloudflare CDN and others), adding 20.9 MB and 361 ms of main-thread time.

  • Shopify adds 214 ms

    214 ms

    Shopify costs a phone 214 ms of main-thread work and 20.6 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.

  • Mobile performance score: 79

    79/100

    Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 211 KiB

    About 211 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Render-blocking requests

    450 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Main-thread work: 2.7 s

    A phone's processor spends 2.7 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1,828 HTML elements

    The page has 1,828 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    150 ms · 47 KiB

    About 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    157 KiB

    2 images could be 157 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    79 KiB

    9 files are served with short cache lifetimes, so returning visitors download them again (79 KiB).

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 64 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.

  • Legacy JavaScript

    4 KiB

    Polyfills for old browsers add 4 KiB JavaScript that modern phones do not need.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix50
  • 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: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Samant Chauhan”.

  • Real-user LCP: 2.6 s

    2.6 s

    Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Time to Interactive: 6.4 s

    6.4 s

    The page becomes fully interactive after 6.4 s. Good is under 3.8 s.

8 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Tap response (INP) got 16% faster for real visitors

    -16%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 145 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 28% faster for real visitors

    -28%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 14 ms

    14 ms

    Scripts block the page for only 14 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 24.8 MB in 376 requests

    24.8 MB

    Your homepage downloads 24.8 MB in 376 requests on a phone: media 21.2 MB (2), images 1.4 MB (24) and other files 1.1 MB (211). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (60 KiB) is 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 7.0 g of CO₂ per visit

    7.02 g

    By the Sustainable Web Design model, a visit to your homepage emits about 7.02 g of CO₂e: 841.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • 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

4 to fixGoogle 9395
  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 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.

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 86 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 124 internal links, 8 external

    The homepage links to 124 pages on samantchauhan.com and 8 external pages.

7 checks passed
  • Meta description: 88 characters

    Your meta description is 88 characters: “Shop Samant Chauhan couture handcrafted Bhagalpuri silk lehengas, gowns & sarees online.”.

  • One H1 headline

    Your main headline reads: “Samant Chauhan”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “SAMANT CHAUHAN | Luxury Couture Online – Samant Chauhan”.

  • Canonical URL set

    The canonical URL is https://samantchauhan.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://samantchauhan.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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 (837 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://samantchauhan.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://samantchauhan.com/collections/couture-kaftan, https://samantchauhan.com/collections/couture-bestsellers, https://samantchauhan.com/collections/view-all-couture-collection, https://samantchauhan.com/collections/ready-to-ship and https://samantchauhan.com/collections/indian-wear-kurta-sets-collection have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://samantchauhan.com/pages/our-stores, https://samantchauhan.com/collections/couture-gowns, https://samantchauhan.com/collections/couture-jacket, https://samantchauhan.com/collections/couture-dress, https://samantchauhan.com/collections/couture-kaftan and https://samantchauhan.com/collections/bridal and 9 others have 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 64 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

2 to fixGoogle 9687
  • 7 small tap targets

    7 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 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”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 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 265 words of copy

    The homepage carries about 265 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop”, “Book an Appointment” and “icon-email Subscribe”.

  • 6 short forms

    6 short forms (5 fields at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 samantchauhan.com, 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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Wishlist Hero · Bucks · zoko.io

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 Hosted

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on samantchauhan.com, including 11 speed issues, 1 SEO issue and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25