Website review, no card needed
storeking.in website review
Visit site (opens in a new tab)Reviewed 17 November 202620 issues · 80 checks
This review found 20 issues worth fixing on storeking.in, 8 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.5 s |
| Jun 27, 2026 | 4.4 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 483 ms |
| Jun 6, 2026 | 438 ms |
| Jun 13, 2026 | 390 ms |
| Jun 20, 2026 | 325 ms |
| Jun 27, 2026 | 321 ms |
| Jul 4, 2026 | 348 ms |
| Jul 11, 2026 | 377 ms |
| Jul 18, 2026 | 388 ms |
| Jul 25, 2026 | 412 ms |
| Aug 1, 2026 | 372 ms |
| Aug 8, 2026 | 386 ms |
| Aug 15, 2026 | 352 ms |
| Aug 22, 2026 | 330 ms |
| Aug 29, 2026 | 337 ms |
| Sep 5, 2026 | 294 ms |
| Sep 12, 2026 | 306 ms |
| Sep 19, 2026 | 317 ms |
| Sep 26, 2026 | 317 ms |
| Oct 3, 2026 | 292 ms |
| Oct 10, 2026 | 273 ms |
| Oct 17, 2026 | 274 ms |
| Oct 24, 2026 | 275 ms |
| Oct 31, 2026 | 289 ms |
| Nov 7, 2026 | 295 ms |
| Nov 14, 2026 | 278 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
Speed
Reduce unused JavaScript
1.1 s · 165 KiBAbout 165 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Reduce initial server response time
652 msReduce initial server response time. Google estimates savings of 652 ms on a phone.
Document request latency
650 msThe HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Server response: 752 ms
752 msYour server takes 752 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Analytics), adding 300 KiB and 217 ms of main-thread time.
Legacy JavaScript
200 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
92 KiB25 files are served with short cache lifetimes, so returning visitors download them again (92 KiB).
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.
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.
Largest Contentful Paint: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A new commerce for the next billion Indians —”.
Time to Interactive: 10.6 s
10.6 sThe page becomes fully interactive after 10.6 s. Good is under 3.8 s.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 295 ms
295 msReal visitors wait 295 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 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.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
5 checks passed
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Tap response (INP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 483 ms to 278 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.9 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 156 ms
156 msScripts block the page for only 156 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 60.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.8 MB in 83 requests
1.8 MBYour homepage downloads 1.8 MB in 83 requests on a phone: fonts 769 KiB (21), scripts 607 KiB (21) and HTML 224 KiB (1). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
31 internal links, 7 external
The homepage links to 31 pages on storeking.in and 7 external pages.
8 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “India's Retail OS for kirana stores. StoreKing turns neighbourhood shops into Bright Stores that serve shoppers online …”.
One H1 headline
Your main headline reads: “A new commerce for the next billion Indians —as simple as opening WhatsApp.”.
Title: 56 characters
Your title is a healthy 56 characters: “StoreKing · Retail OS turning kiranas into Bright Stores”.
Canonical URL set
The canonical URL is https://storeking.in/.
Structured data in place
Structured data found: FAQPage, LocalBusiness, Organization, SoftwareApplication 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://storeking.in/sitemap.xml.
AI search readiness
No llms.txt
There is no https://storeking.in/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.
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.
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,262 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without an H1
https://storeking.in/club, https://storeking.in/kingmaker, https://storeking.in/shoppers and https://storeking.in/plans have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://storeking.in/kingmaker has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.
6 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.
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
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
9 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 1,585 words of copy
The homepage carries about 1,585 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “I SHOP StoreKing CLUB” and “I RUN A SHOP Retail OS”.
3 calls to action
The homepage has 3 calls to action, for example “Contact”, “PlansPick the plan for your shop” and “Shop ownersBecome a Bright Store”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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.
3 other companies contacted
Loading the homepage contacts 3 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 storeking.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on storeking.in, including 16 speed issues. 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.