Website review, no card needed

shopclues.com logo

shopclues.com website review

Visit site (opens in a new tab)Reviewed 30 October 202660 issues · 96 checks

This review found 60 issues worth fixing on shopclues.com, 22 of them high impact, across 96 checks. The most urgent: use efficient cache lifetimes. 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
5.7 s4.9 sMay 9Oct 245.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.1 s
May 16, 20265.0 s
May 23, 20265.0 s
May 30, 20265.2 s
Jun 6, 20265.1 s
Jun 13, 20265.3 s
Jun 20, 20265.3 s
Jun 27, 20265.1 s
Jul 4, 20265.4 s
Jul 11, 20265.3 s
Jul 18, 20265.3 s
Jul 25, 20265.3 s
Aug 1, 20265.3 s
Aug 8, 20265.4 s
Aug 15, 20265.5 s
Aug 22, 20265.6 s
Aug 29, 20265.5 s
Sep 5, 20265.4 s
Sep 12, 20265.1 s
Sep 19, 20265.0 s
Sep 26, 20265.0 s
Oct 3, 20265.1 s
Oct 10, 20265.3 s
Oct 17, 20265.2 s
Oct 24, 20265.3 s
Real-visitor tap response (INP)75th percentile, phones
484 ms430 msMay 9Oct 24453 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026448 ms
May 16, 2026439 ms
May 23, 2026464 ms
May 30, 2026466 ms
Jun 6, 2026461 ms
Jun 13, 2026467 ms
Jun 20, 2026467 ms
Jun 27, 2026463 ms
Jul 4, 2026463 ms
Jul 11, 2026468 ms
Jul 18, 2026457 ms
Jul 25, 2026456 ms
Aug 1, 2026450 ms
Aug 8, 2026437 ms
Aug 15, 2026436 ms
Aug 22, 2026439 ms
Aug 29, 2026451 ms
Sep 5, 2026461 ms
Sep 12, 2026476 ms
Sep 19, 2026478 ms
Sep 26, 2026474 ms
Oct 3, 2026476 ms
Oct 10, 2026468 ms
Oct 17, 2026458 ms
Oct 24, 2026453 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 shopclues.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shopclues.com at 0.9 s0.9 s
  2. shopclues.com at 1.8 s1.8 s
  3. shopclues.com at 2.7 s2.7 s
  4. shopclues.com at 3.6 s3.6 s
  5. shopclues.com at 4.5 s4.5 s
  6. shopclues.com at 5.3 s5.3 s
  7. shopclues.com at 6.2 s6.2 s
  8. shopclues.com at 7.1 s7.1 s

Speed

17 to fix10
  • Use efficient cache lifetimes

    6.8 s · 2.9 MB

    269 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).

  • Render-blocking requests

    5.5 s

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

  • Reduce unused JavaScript

    4.0 s · 886 KiB

    About 886 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

  • Improve image delivery

    2.0 s · 688 KiB

    44 images could be 688 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

  • Document request latency

    1.0 s · 59 KiB

    The HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Mobile performance score: 10

    10/100

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

  • Main-thread work: 4.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 2.3 MB and 1.8 s of main-thread time.

  • Google Tag Manager adds 727 ms

    727 ms

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

  • Avoid multiple page redirects

    751 ms

    The page goes through 1 redirect before it starts loading, costing about 751 ms. Link and advertise the final URL directly.

  • Reduce unused CSS

    600 ms · 117 KiB

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

  • Legacy JavaScript

    400 ms · 57 KiB

    Polyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • Facebook adds 342 ms

    342 ms

    Facebook costs a phone 342 ms of main-thread work and 308 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.

  • Google/Doubleclick Ads adds 242 ms

    242 ms

    Google/Doubleclick Ads costs a phone 242 ms of main-thread work and 450 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.

  • 17 long tasks on the main thread

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

  • 2,571 HTML elements

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

  • shopclues.net adds 106 ms

    106 ms

    shopclues.net costs a phone 106 ms of main-thread work and 515 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.

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 246 ms

    246 ms

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

Core Web Vitals

12 to fix33
  • 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.00

    1.00

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

  • Cumulative Layout Shift: 2.053

    2.053

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

  • Largest Contentful Paint: 25.1 s

    25.1 s

    Your largest element takes 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Rocket Deal”.

  • Time to Interactive: 26.9 s

    26.9 s

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

  • Speed Index: 12.5 s

    12.5 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

    The first text or image appears after 5.3 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 955 ms

    955 ms

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

  • Real-user LCP: 3.0 s

    3.0 s

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

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 235 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 448 ms to 453 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-10-24, real Chrome visitors' largest content (lcp) went from 5.1 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 checks passed
  • Real-user INP: 194 ms

    194 ms

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

Images and page weight

2 to fix60
  • Page weight: 5.4 MB in 393 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 393 requests on a phone: images 2.3 MB (255), scripts 2.2 MB (54) and other files 537 KiB (74). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (671 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.5 g of CO₂ per visit

    1.54 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 185.0 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

10 to fixGoogle 5984
  • 215 text elements with low contrast

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

  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical 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 (17 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 23 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 30 automated accessibility rules passed

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

SEO

6 to fixGoogle 8578
  • Title is long (134 characters)

    Your title is 134 characters, so Google will cut it off around 60: “Online Shopping Site India - Shop Online for men, women and kids fashion, home, kitchen, …”.

  • Meta description is long (217 characters)

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

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 9 links crawlers can't follow

    9 links have no real href, so search engines can't follow them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 226 internal links, 26 external

    The homepage links to 226 pages on shopclues.com and 26 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Online Shopping in India @www.ShopClues.com”.

  • Canonical URL set

    The canonical URL is https://www.shopclues.com/.

  • 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.shopclues.com/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    50%

    The HTML your server sends has 1,320 of the 2,618 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://www.shopclues.com/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.

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.shopclues.com/mychat declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 11 pages share 2 titles

    / and https://www.shopclues.com/mychat all use the title “Online Shopping Site India - Shop Online for men, women and kids fash…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://www.shopclues.com/vip-club.html, https://www.shopclues.com/shopclues-sale-2.html, https://www.shopclues.com/refurbished-phones-1.html, https://www.shopclues.com/express-shipping.html, https://www.shopclues.com/lifestyle-sale-17.html and https://www.shopclues.com/work-from-home-dresses.html and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.shopclues.com/mychat 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.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

4 to fixGoogle 5074
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5218204&Ver=2&mid=43211080-0128-4930-ae67-97000b18bc80&bo=1&sid=cb9518b0d40711f199b7ef50a8b1e887&vid=cb954190d40711f191cd1daf22fbac15&vids=1&msclkid=N&pi=918639831&lg=.

  • 4 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    40 of 41 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 2,618 words of copy

    The homepage carries about 2,618 words of visible text.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Login/Register” and “Join VIP Club”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, 1 customer or partner logo and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Matomo.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 37 cookies set on arrival

    37

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

  • 52 other companies contacted

    Loading the homepage contacts 52 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 shopclues.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
jQuery
Analytics
Google Analytics | Google Tag Manager | Matomo
Hosting
AWS

Company

Founded
2011
Headquarters
Gurgaon Lok Sabha constituency

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 60 issues on shopclues.com, including 29 speed issues, 6 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

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