Website review, no card needed
safeshopindia.com website review
Visit site (opens in a new tab)Reviewed 20 November 202653 issues · 88 checks
This review found 53 issues worth fixing on safeshopindia.com, 17 of them high impact, across 88 checks. The most urgent: page weight: 12.2 MB in 187 requests. 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
68DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
6.3 MB43 files are served with short cache lifetimes, so returning visitors download them again (6.3 MB).
Improve image delivery
4.5 MB29 images could be 4.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
2.7 MBAbout 2.7 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 466 ms. During a long task the page ignores taps.
Google Tag Manager adds 256 ms
256 msGoogle Tag Manager costs a phone 256 ms of main-thread work and 182 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.
2,412 HTML elements
The page has 2,412 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Google CDN and others), adding 312 KiB and 356 ms of main-thread time.
Reduce unused CSS
88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Time to Interactive: 41.5 s
41.5 sThe page becomes fully interactive after 41.5 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.763
0.763The layout shifts by 0.763 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 608 ms
608 msScripts block taps and scrolling for 608 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 448 ms
448 msReal visitors wait 448 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.17
0.17For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 0.8 s
0.8 sYour largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “The company does not engage in chit funds, investments, mon…”.
Images and page weight
Page weight: 12.2 MB in 187 requests
12.2 MBYour homepage downloads 12.2 MB in 187 requests on a phone: images 9.4 MB (100), scripts 1.6 MB (44) and other files 941 KiB (34). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.
18 images far larger than shown
1.5 MB18 images are downloaded at several times the size a phone draws them, for example cb4.jpg at 1,200 px wide, shown at 366 px. Resized copies would save about 1.5 MB.
40 images in older formats
40 images (7.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.
16 images below the first screen load straight away
16 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.4 g of CO₂ per visit
3.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.45 g of CO₂e: 413.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
12 form fields without a label
12 form fields have 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 should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
66 links crawlers can't follow
66 links have no real href, so search engines can't follow them.
Title is long (208 characters)
Your title is 208 characters, so Google will cut it off around 60: “Safe Shop India offers a wide range of innovative products like Talking Bhagavad Gita and…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.
Meta description is long (342 characters)
Your meta description is 342 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://www.safeshopindia.com/sitemap.xml, so Google discovers your pages only by following links.
77 internal links, 10 external
The homepage links to 77 pages on safeshopindia.com and 10 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.safeshopindia.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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.
No llms.txt
There is no https://www.safeshopindia.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (445 words), so crawlers that don't run JavaScript still read it.
Other pages
4 linked pages are broken
Your homepage links to https://www.safeshopindia.com/app/retail/product/EAUG25MANTROP5BS/haoma-vaidik-mantropasana-5-book-set, https://www.safeshopindia.com/app/retail/product/EOCT25MIAKITOOL/miakasa-kitchen-tools-set, https://www.safeshopindia.com/app/retail/product/ESEP25MWDP/miakasa-double-wall-rose-dinner-set-70pcs and https://www.safeshopindia.com/app/retail/product/ESEP25CLAPCOO5L/miakasa-stainless-steel-clavis-pressure-cooker-5l, which answer with an error. Visitors hit a dead end and search engines drop them.
11 pages point its canonical at the homepage
https://www.safeshopindia.com/app/aboutus, https://www.safeshopindia.com/app/gallery, https://www.safeshopindia.com/app/shop-cart, https://www.safeshopindia.com/app/ourbrands, https://www.safeshopindia.com/app/products and https://www.safeshopindia.com/app/firesale and 5 others 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.
6 pages share 2 titles
https://www.safeshopindia.com/app/shop-cart, https://www.safeshopindia.com/app/ourbrands and https://www.safeshopindia.com/app/legal all use the title “Safe Shop India offers a wide range of innovative products like Talki…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://www.safeshopindia.com/app/shop-cart, https://www.safeshopindia.com/app/ourbrands and https://www.safeshopindia.com/app/legal use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://www.safeshopindia.com/app/gallery, https://www.safeshopindia.com/app/ourbrands, https://www.safeshopindia.com/app/products, https://www.safeshopindia.com/app/firesale, https://www.safeshopindia.com/app/legal and https://www.safeshopindia.com/app/tribal and 1 other 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 34 found) and read each the way a search engine does.
3 checks passed
Every page has a meta description
All 11 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 175 words
The homepage has only about 175 words of visible text; thin pages give Google and first-time buyers little to go on.
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 risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
19 calls to action
The homepage has 19 calls to action, for example “Contact”, “Shop Now” and “Subscribe”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
7 other companies contacted
Loading the homepage contacts 7 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 safeshopindia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Company
- Headquarters
- New Delhi
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on safeshopindia.com, including 20 speed issues, 7 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.