Website review, no card needed
stovekraft.com website review
Visit site (opens in a new tab)Reviewed 29 October 202644 issues · 87 checks
This review found 44 issues worth fixing on stovekraft.com, 20 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.5 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 227 ms |
| May 16, 2026 | 227 ms |
| May 23, 2026 | 224 ms |
| May 30, 2026 | 209 ms |
| Jun 6, 2026 | 164 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 199 ms |
| Jun 27, 2026 | 211 ms |
| Jul 4, 2026 | 213 ms |
| Jul 11, 2026 | 212 ms |
| Jul 18, 2026 | 207 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 159 ms |
| Aug 8, 2026 | 160 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 164 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 191 ms |
| Sep 26, 2026 | 203 ms |
| Oct 3, 2026 | 222 ms |
| Oct 10, 2026 | 251 ms |
| Oct 17, 2026 | 259 ms |
| Oct 24, 2026 | 257 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
1.4 s
2.8 s
4.2 s
5.6 s
7.0 s
8.4 s
9.7 s
11.1 s
Speed
Use efficient cache lifetimes
1.4 s · 35.5 MB84 files are served with short cache lifetimes, so returning visitors download them again (35.5 MB).
Reduce unused JavaScript
17.4 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 17.4 s faster on a phone.
YouTube adds 2.0 s
2.0 sYouTube costs a phone 2.0 s of main-thread work and 3.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.5 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 4.7 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 (YouTube, Facebook and Google Tag Manager and others), adding 3.7 MB and 2.7 s of main-thread time.
Document request latency
850 ms · 176 KiBThe HTML itself could arrive about 850 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
833 msReduce initial server response time. Google estimates savings of 833 ms on a phone.
Improve image delivery
383 KiB11 images could be 383 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 362 ms. During a long task the page ignores taps.
Facebook adds 304 ms
304 msFacebook costs a phone 304 ms of main-thread work and 216 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.
Server response: 933 ms
933 msYour server takes 933 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Reduce unused CSS
51 KiBAbout 51 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.
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: 49.4 s
49.4 sYour largest element takes 49.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 21.4 s
21.4 sVisually, the page fills in at 21.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 49.8 s
49.8 sThe page becomes fully interactive after 49.8 s. Good is under 3.8 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 284 ms
284 msReal visitors wait 284 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
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.
36 images without width and height
36 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 227 ms to 257 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.082
0.082The layout barely moves while loading (CLS 0.082, good is under 0.1).
Images and page weight
Page weight: 42.3 MB in 257 requests
42.3 MBYour homepage downloads 42.3 MB in 257 requests on a phone: media 33.4 MB (4), scripts 5.2 MB (102) and images 2.0 MB (80). Under 2 MB keeps phones on slow connections fast.
9 images below the first screen load straight away
9 images further down the page (588 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
126 KiB3 images are downloaded at several times the size a phone draws them, for example store-img.webp at 1,500 px wide, shown at 334 px. Resized copies would save about 126 KiB.
2 images in older formats
2 images (323 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 12.0 g of CO₂ per visit
11.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 11.99 g of CO₂e: 1438.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
<marquee> elements are deprecated and must not be used (1 element)
<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
11 H1 headlines
There are 11 <h1> headlines (“Leading Manufacturer of Cookware, Kitchen Applian…”, “Brand Story” and “New Launches”). One clear main headline is easier for people and search engines.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
108 internal links, 17 external
The homepage links to 108 pages on stovekraft.com and 17 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Discover cooking excellence with Stovekraft, home to Pigeon and Gilma. From Air fryers to cookware, find Pigeon Exclusi…”.
Title: 56 characters
Your title is a healthy 56 characters: “Pigeon | India’s Leading Kitchen & Home Appliances Brand”.
Canonical URL set
The canonical URL is https://stovekraft.com/.
Structured data in place
Structured data found: Organization.
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://stovekraft.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://stovekraft.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.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (562 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages point its canonical at the homepage
https://stovekraft.com/our-story, https://stovekraft.com/pigeon/category, https://stovekraft.com/pigeon/category/cooking/pressure-cookers, https://stovekraft.com/pigeon/category/cooking/cookware, https://stovekraft.com/pigeon/category/cooking/cooktops and https://stovekraft.com/pigeon/category/cooking/induction-infrared-cooktops and 9 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.
16 pages share a title
/, https://stovekraft.com/our-story, https://stovekraft.com/pigeon/category, https://stovekraft.com/pigeon/category/cooking/pressure-cookers, https://stovekraft.com/pigeon/category/cooking/cookware and https://stovekraft.com/pigeon/category/cooking/cooktops and 10 others all use the title “Pigeon | India’s Leading Kitchen & Home Appliances Brand”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://stovekraft.com/our-story, https://stovekraft.com/pigeon/category, https://stovekraft.com/pigeon/category/cooking/pressure-cookers, https://stovekraft.com/pigeon/category/cooking/cookware, https://stovekraft.com/pigeon/category/cooking/cooktops and https://stovekraft.com/pigeon/category/cooking/induction-infrared-cooktops and 9 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
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
6 small tap targets
6 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
About 749 words of copy
The homepage carries about 749 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Download E-catalogue” and “Contact Us”.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 3 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 1 of them by other companies (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.
24 other companies contacted
Loading the homepage contacts 24 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 stovekraft.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on stovekraft.com, including 24 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.