Website review, no card needed
safetykart.com website review
Visit site (opens in a new tab)Reviewed 6 November 202622 issues · 52 checks
This review found 22 issues worth fixing on safetykart.com, 4 of them high impact, across 52 checks. The most urgent: 1 text element with low contrast. 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
80B- #47,314 of 120,828 reviewed websitesbeats 55%
- #31,430 of 68,397 online storesbeats 48%
- #30,225 of 62,325 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
740 ms · 116 KiBAbout 116 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 740 ms faster on a phone.
Render-blocking requests
650 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Reduce unused CSS
280 ms · 40 KiBAbout 40 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Shopify, qikify.com and Google Fonts and others), adding 350 KiB and 125 ms of main-thread time.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 90 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.
Use efficient cache lifetimes
1 KiB1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 291 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Opening Soon”.
Time to Interactive: 6.3 s
6.3 sThe page becomes fully interactive after 6.3 s. Good is under 3.8 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Speed Index: 3.6 s
3.6 sVisually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 73 ms
73 msScripts block the page for only 73 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.35 g of CO₂e: 41.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.2 MB in 106 requests
1.2 MBYour homepage downloads 1.2 MB in 106 requests on a phone: other files 658 KiB (72), scripts 488 KiB (28) and fonts 62 KiB (2). That is a lean page.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (27 characters)
Your title is only 27 characters: “Safetykart Retail Pvt. Ltd.”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.safetykart.com/sitemap.xml, so Google discovers your pages only by following links.
Only 1 internal link
The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
3 checks passed
One H1 headline
Your main headline reads: “Opening Soon”.
Canonical URL set
The canonical URL is https://www.safetykart.com/password.
robots.txt in place
robots.txt is in place.
AI search readiness
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.safetykart.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.
Best practices
2 small tap targets
2 of 8 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: the server responded with a status of 404 ()”.
1 checks passed
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.
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 45 words
The homepage has only about 45 words of visible text; thin pages give Google and first-time buyers little to go on.
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: “Sign Up”.
1 call to action
The homepage has 1 call to action, for example “Sign Up”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
13 other companies contacted
Loading the homepage contacts 13 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 safetykart.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Smart Menu · tawk.to
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 22 issues on safetykart.com, including 7 speed issues, 7 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.