Website review, no card needed

chosenstore.in logo

chosenstore.in website review

Visit site (opens in a new tab)Reviewed 9 November 202646 issues · 93 checks

This review found 46 issues worth fixing on chosenstore.in, 14 of them high impact, across 93 checks. The most urgent: improve image delivery. 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.7 s2.8 sMay 23Nov 72.9 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.5 s
May 30, 20263.5 s
Jun 6, 20263.4 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.4 s
Aug 1, 20263.5 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.3 s
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Oct 24, 20263.0 s
Oct 31, 20263.0 s
Nov 7, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
419 ms281 msMay 23Nov 7403 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026297 ms
May 30, 2026298 ms
Jun 6, 2026297 ms
Jun 13, 2026300 ms
Jun 20, 2026304 ms
Jun 27, 2026310 ms
Jul 4, 2026319 ms
Jul 11, 2026319 ms
Jul 18, 2026318 ms
Jul 25, 2026323 ms
Aug 1, 2026327 ms
Aug 8, 2026340 ms
Aug 15, 2026360 ms
Aug 22, 2026365 ms
Aug 29, 2026369 ms
Sep 5, 2026368 ms
Sep 12, 2026356 ms
Sep 19, 2026356 ms
Sep 26, 2026365 ms
Oct 3, 2026369 ms
Oct 10, 2026374 ms
Oct 17, 2026384 ms
Oct 24, 2026395 ms
Oct 31, 2026400 ms
Nov 7, 2026403 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 chosenstore.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. chosenstore.in at 0.7 s0.7 s
  2. chosenstore.in at 1.5 s1.5 s
  3. chosenstore.in at 2.2 s2.2 s
  4. chosenstore.in at 3.0 s3.0 s
  5. chosenstore.in at 3.7 s3.7 s
  6. chosenstore.in at 4.4 s4.4 s
  7. chosenstore.in at 5.2 s5.2 s
  8. chosenstore.in at 5.9 s5.9 s

Speed

13 to fix29
  • Improve image delivery

    5.1 s · 1.3 MB

    56 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.1 s faster on a phone.

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.9 s

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

  • 3,985 HTML elements

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

  • Reduce unused JavaScript

    600 ms · 951 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and gokwik.co and others), adding 2.3 MB and 1.1 s of main-thread time.

  • Use efficient cache lifetimes

    820 KiB

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

  • Reduce unused CSS

    600 ms · 177 KiB

    About 177 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.

  • Render-blocking requests

    450 ms

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

  • Google Tag Manager adds 371 ms

    371 ms

    Google Tag Manager costs a phone 371 ms of main-thread work and 662 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.

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 326 ms. During a long task the page ignores taps.

  • gokwik.co adds 168 ms

    168 ms

    gokwik.co costs a phone 168 ms of main-thread work and 790 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.

  • Shopify adds 105 ms

    105 ms

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

  • Minify CSS

    130 ms · 29 KiB

    29 KiB could be saved by minifying CSS.

  • Minify JavaScript

    130 ms · 20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    62 KiB

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

  • Duplicated JavaScript

    12 KiB

    12 KiB JavaScript is shipped twice across bundles.

  • 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: 20 ms

    20 ms

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

Core Web Vitals

12 to fix0
  • 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: 1.35

    1.35

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

  • Largest Contentful Paint: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Science-First Skin & Hair Care, Designed for Longevity”.

  • Time to Interactive: 27.4 s

    27.4 s

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

  • Cumulative Layout Shift: 0.895

    0.895

    The layout shifts by 0.895 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 10.6 s

    10.6 s

    Visually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user INP: 380 ms

    380 ms

    Real visitors wait 380 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 35% slower for real visitors

    +35%

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

  • Real-user TTFB: 841 ms

    841 ms

    Real visitors wait 841 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 490 ms

    490 ms

    Scripts block taps and scrolling for 490 ms in total while the page loads. Good is under 200 ms.

  • 10 images without width and height

    10 images have no width and height attributes, so the layout jumps as each one loads.

3 checks passed
  • Real-user FCP: 1.8 s

    1.8 s

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

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

    -15%

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

Images and page weight

4 to fix42
  • Page weight: 7.2 MB in 361 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 361 requests on a phone: images 3.4 MB (127), scripts 2.4 MB (72) and other files 800 KiB (138). Under 2 MB keeps phones on slow connections fast.

  • 33 images in older formats

    33 images (1.9 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.

  • An image on the first screen is lazy-loaded

    Long_Game_HomePage_banner_mobile.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 11 images far larger than shown

    487 KiB

    11 images are downloaded at several times the size a phone draws them, for example Tor-Classic-216gmPlain.webp at 733 px wide, shown at 149 px. Resized copies would save about 487 KiB.

  • About 2.1 g of CO₂ per visit

    2.05 g

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

Accessibility

9 to fixGoogle 9490
  • 16 text elements with low contrast

    16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (8 elements)

    Links must have discernible text: 8 elements on the page fail this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Science-First Skin & Hair Care, Designed for Longevity – CHOSEN Store”.

  • Meta description is long (201 characters)

    Your meta description is 201 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 421 internal links, 6 external

    The homepage links to 421 pages on chosenstore.in and 6 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://chosenstore.in/.

  • 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://chosenstore.in/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://chosenstore.in/llms.txt (14 KiB, 119 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix98
  • 10 pages share a meta description

    https://chosenstore.in/pages/best-skin-care-products, https://chosenstore.in/collections/sunscreens, https://chosenstore.in/collections/serums, https://chosenstore.in/collections/night-creams, https://chosenstore.in/collections/moisturizers and https://chosenstore.in/collections/exfoliators-peels and 4 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 126 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 7391
  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “[Compra Survey] Error in poll loop ReferenceError: pickEligibleSurvey is not defined”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    143 of 156 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 895 words of copy

    The homepage carries about 895 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more in our Privacy Policy” and “Shop All”.

  • 40 calls to action

    The homepage has 40 calls to action, for example “Add order notes”, “Shop All” and “Shop by Product”.

  • 38 short forms

    38 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 91 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

  • 19 cookies set on arrival

    19

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

  • 38 other companies contacted

    Loading the homepage contacts 38 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 chosenstore.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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gokwik Cart Slide Cart Drawer · Microsoft Clarity · Webengage · Getsitecontrol Countdown Timer · Whatmorelive · Compra Post Purchase Surveys · Essential Post Purchase Upsell · Sagepilot Ai Test Custom App

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
Analytics
Google 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 46 issues on chosenstore.in, including 25 speed issues, 3 SEO issues and 1 conversion gap. 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