Website review, no card needed
waghbakritea.com website review
Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 79 checks
This review found 32 issues worth fixing on waghbakritea.com, 9 of them high impact, across 79 checks. The most urgent: page weight: 56.3 MB in 143 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
83BClosest 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 | 3.7 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.5 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.7 s |
| Aug 22, 2026 | 4.7 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.0 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.7 s |
| Nov 7, 2026 | 3.8 s |
| Nov 14, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 114 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 107 ms |
| Jun 27, 2026 | 106 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 149 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 182 ms |
| Aug 15, 2026 | 173 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 148 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 155 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 152 ms |
| Oct 17, 2026 | 144 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 144 ms |
| Nov 7, 2026 | 144 ms |
| Nov 14, 2026 | 142 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Use efficient cache lifetimes
37.7 MB99 files are served with short cache lifetimes, so returning visitors download them again (37.7 MB).
Improve image delivery
13.9 MB23 images could be 13.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 88
88/100Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 298 ms. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Clarity and nitrocdn.com and others), adding 190 KiB and 254 ms of main-thread time.
Reduce unused CSS
150 ms · 29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
117 KiBAbout 117 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 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.
1 checks passed
Server response: 113 ms
113 msYour server sent the HTML in 113 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.
Speed Index: 19.6 s
19.6 sVisually, the page fills in at 19.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 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.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 114 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.9 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 147 ms
147 msReal visitors wait 147 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Total Blocking Time: 176 ms
176 msScripts block the page for only 176 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “For bonds that begin over a brew”.
Images and page weight
Page weight: 56.3 MB in 143 requests
56.3 MBYour homepage downloads 56.3 MB in 143 requests on a phone: images 49.1 MB (103), media 6.3 MB (2) and scripts 491 KiB (18). Under 2 MB keeps phones on slow connections fast.
19 images over 500 KB
19 images weigh 24.5 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
4.6 MB3 images are downloaded at several times the size a phone draws them, for example Website Desktop size 730 × 569 px-01.jpg at 3,042 px wide, shown at 360 px. Resized copies would save about 4.6 MB.
39 images in older formats
39 images (31.6 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.
35 images below the first screen load straight away
35 images further down the page (26.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 15.9 g of CO₂ per visit
15.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 15.95 g of CO₂e: 1913.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 122 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (27 characters)
Your title is only 27 characters: “Home | Wagh Bakri Tea Group”. Between 30 and 65 characters leaves room to say what you do and for whom.
No XML sitemap
No XML sitemap at https://www.waghbakritea.com/sitemap.xml, so Google discovers your pages only by following links.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
80 internal links, 67 external
The homepage links to 80 pages on waghbakritea.com and 67 external pages.
6 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Wagh Bakri Tea Group is one of India’s most trusted tea companies, delivering premium quality tea crafted with heritage…”.
One H1 headline
Your main headline reads: “For bonds that begin over a brew”.
Canonical URL set
The canonical URL is https://www.waghbakritea.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.
AI search readiness
No llms.txt
There is no https://www.waghbakritea.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, which the crawlers above handle.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (829 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.waghbakritea.com/waghbakri-royale has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.waghbakritea.com/our-brands/wagh-bakri and https://www.waghbakritea.com/our-brands/wagh-bakri-sipz use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://www.waghbakritea.com/our-brands/wagh-bakri, https://www.waghbakritea.com/our-brands/wagh-bakri-good-morning, https://www.waghbakritea.com/our-brands/wagh-bakri-mili, https://www.waghbakritea.com/our-brands/wagh-bakri-navchetan, https://www.waghbakritea.com/our-brands/wagh-bakri-sipz and https://www.waghbakritea.com/our-brands/vending-machines 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 30 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
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”.
2 checks passed
Tap targets are thumb-sized
6 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 205 words
The homepage has only about 205 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
4 calls to action
The homepage has 4 calls to action, for example “SHOP NOW”, “Contact Us” and “Learn More”.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 3 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
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.
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 waghbakritea.com, 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
- Cloudflare
Company
- Founded
- 1915
- Headquarters
- Ahmedabad
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on waghbakritea.com, including 14 speed issues, 3 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.