Website review, no card needed
supercmart.com website review
Visit site (opens in a new tab)Reviewed 22 October 202641 issues · 69 checks
This review found 41 issues worth fixing on supercmart.com, 19 of them high impact, across 69 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
54FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.0 s |
| May 9, 2026 | 5.0 s |
| May 16, 2026 | 4.9 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 4.7 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.9 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.5 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 193 ms |
| May 9, 2026 | 199 ms |
| May 16, 2026 | 191 ms |
| May 23, 2026 | 190 ms |
| May 30, 2026 | 186 ms |
| Jun 13, 2026 | 195 ms |
| Jun 27, 2026 | 216 ms |
| Jul 4, 2026 | 202 ms |
| Jul 11, 2026 | 189 ms |
| Jul 18, 2026 | 185 ms |
| Jul 25, 2026 | 180 ms |
| Aug 1, 2026 | 178 ms |
| Aug 8, 2026 | 179 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 182 ms |
| Aug 29, 2026 | 186 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 181 ms |
| Sep 26, 2026 | 185 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 196 ms |
| Oct 17, 2026 | 205 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
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.1 s
2.6 s
3.1 s
3.6 s
4.1 s
Speed
Reduce unused JavaScript
5.0 s · 992 KiBAbout 992 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Render-blocking requests
4.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.1 s.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
650 ms · 83 KiB4 files are served with short cache lifetimes, so returning visitors download them again (83 KiB).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 565 ms. During a long task the page ignores taps.
Reduce unused CSS
450 ms · 78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 817 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mapbox adds 163 ms
163 msMapbox costs a phone 163 ms of main-thread work and 376 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.
5 third-party services on the page
5 third-party services load with your homepage (Mapbox, fiservapps.com and noq-servers.net and others), adding 474 KiB and 179 ms of main-thread time.
Legacy JavaScript
150 ms · 16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
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: 1 ms
1 msYour server sent the HTML in 1 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.
Real-user CLS: 0.77
0.77For real visitors the layout shifts by 0.77 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing and shopping experi…”.
First Contentful Paint: 6.8 s
6.8 sThe first text or image appears after 6.8 s on a phone. Good is under 1.8 s.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 868 ms
868 msScripts block taps and scrolling for 868 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 204 ms
204 msReal visitors wait 204 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 193 ms to 205 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user TTFB: 749 ms
749 msReal visitors wait 749 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.0 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.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.5 MB in 24 requests
1.5 MBYour homepage downloads 1.5 MB in 24 requests on a phone: scripts 1.3 MB (4), stylesheets 92 KiB (4) and fonts 70 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.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
25 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 28 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 passed and 3 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.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (12 characters)
Your title is only 12 characters: “Super C Mart”. 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 canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.supercmart.com/sitemap.xml, so Google discovers your pages only by following links.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
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.supercmart.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.
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
18 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
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.
Only about 123 words
The homepage has only about 123 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start Shopping”.
Privacy and tracking
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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 supercmart.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on supercmart.com, including 18 speed issues, 10 SEO issues and 5 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.