Website review, no card needed
englishteastore.com website review
Visit site (opens in a new tab)Reviewed 4 November 202643 issues · 93 checks
This review found 43 issues worth fixing on englishteastore.com, 23 of them high impact, across 93 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
75C- #82,133 of 125,664 reviewed websitesbeats 30%
- #51,834 of 70,232 online storesbeats 22%
- #48,879 of 63,802 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 293 ms |
| May 23, 2026 | 290 ms |
| May 30, 2026 | 274 ms |
| Jun 6, 2026 | 265 ms |
| Jun 13, 2026 | 267 ms |
| Jun 20, 2026 | 272 ms |
| Jun 27, 2026 | 273 ms |
| Jul 4, 2026 | 275 ms |
| Jul 11, 2026 | 276 ms |
| Jul 18, 2026 | 276 ms |
| Jul 25, 2026 | 275 ms |
| Aug 1, 2026 | 276 ms |
| Aug 8, 2026 | 299 ms |
| Aug 15, 2026 | 311 ms |
| Aug 22, 2026 | 324 ms |
| Aug 29, 2026 | 312 ms |
| Sep 5, 2026 | 291 ms |
| Sep 12, 2026 | 274 ms |
| Sep 19, 2026 | 244 ms |
| Sep 26, 2026 | 228 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 213 ms |
| Oct 17, 2026 | 221 ms |
| Oct 24, 2026 | 230 ms |
| Oct 31, 2026 | 240 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
2.1 s
4.1 s
6.2 s
8.2 s
10.3 s
12.4 s
14.4 s
16.5 s
Speed
Reduce unused JavaScript
6.4 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.
Use efficient cache lifetimes
6.0 s · 1.7 MB29 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Render-blocking requests
3.0 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Main-thread work: 27.7 s
A phone's processor spends 27.7 s on main-thread work while loading, 15.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
1.7 s · 217 KiBAbout 217 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.7 s faster on a phone.
ucontactcloud.com adds 1.1 s
1.1 sucontactcloud.com costs a phone 1.1 s of main-thread work and 1.3 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.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 523 KiB 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.
10,842 HTML elements
The page has 10,842 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (ucontactcloud.com, Google Tag Manager and rebuyengine.com and others), adding 3.5 MB and 4.8 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.
Improve image delivery
1.0 MB39 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
rebuyengine.com adds 622 ms
622 msrebuyengine.com costs a phone 622 ms of main-thread work and 587 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.
Google CDN adds 516 ms
516 msGoogle CDN costs a phone 516 ms of main-thread work and 379 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.
Convert Insights adds 495 ms
495 msConvert Insights costs a phone 495 ms of main-thread work and 209 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.
Legacy JavaScript
150 ms · 58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
70 ms · 19 KiB19 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 20 ms
20 msYour server sent the HTML in 20 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.
Largest Contentful Paint: 33.5 s
33.5 sYour largest element takes 33.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Promotional banner with various loose-leaf teas and Kraft p…”.
Speed Index: 16.7 s
16.7 sVisually, the page fills in at 16.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 8.4 s
8.4 sScripts block taps and scrolling for 8.4 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 41.8 s
41.8 sThe page becomes fully interactive after 41.8 s. Good is under 3.8 s.
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 INP: 251 ms
251 msReal visitors wait 251 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 658 ms
658 msReal visitors wait 658 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 293 ms to 240 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 8.3 MB in 657 requests
8.3 MBYour homepage downloads 8.3 MB in 657 requests on a phone: scripts 3.5 MB (148), images 2.3 MB (96) and other files 1.2 MB (335). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
206 KiB5 images are downloaded at several times the size a phone draws them, for example mnekkpyfqx7nv7fxxiyi.jpg at 1,280 px wide, shown at 290 px. Resized copies would save about 206 KiB.
2 images in older formats
2 images (135 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.
3 images below the first screen load straight away
3 images further down the page (243 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.35 g of CO₂e: 281.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 277 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 H1 headlines
There are 6 <h1> headlines (“English Tea Store | Shop British Teas & Foods, Te…”, “Premium Loose Leaf Black Tea & Traditional Herita…” and “Premium Loose Leaf Green Tea & Artisanal Flushes”). One clear main headline is easier for people and search engines.
1,156 internal links, 23 external
The homepage links to 1,156 pages on englishteastore.com and 23 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Discover authentic British teas, fine porcelain teaware, and heritage pantry staples at the English Tea Store. Enjoy fa…”.
Title: 63 characters
Your title is a healthy 63 characters: “British Teas, Fine Teaware & Imported Foods | English Tea Store”.
Canonical URL set
The canonical URL is https://www.englishteastore.com/.
Structured data in place
Structured data found: Organization, ProductGroup 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://www.englishteastore.com/sitemap.xml.
AI search readiness
4 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 (5,610 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.englishteastore.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.englishteastore.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.englishteastore.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.englishteastore.com/collections/all, https://www.englishteastore.com/customer_authentication/redirect and https://www.englishteastore.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.englishteastore.com/collections/all, https://www.englishteastore.com/customer_authentication/redirect, https://www.englishteastore.com/policies/shipping-policy, https://www.englishteastore.com/collections/teas-of-the-month, https://www.englishteastore.com/collections/tea and https://www.englishteastore.com/collections/all-tea-by-type and 9 others 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 197 found) and read each the way a search engine does.
3 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.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “SecurityError: Failed to read a named property 'document' from 'Window': Blocked a frame with origin "null" from access…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
77 of 93 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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,579 words of copy
The homepage carries about 1,579 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
14 calls to action
The homepage has 14 calls to action, for example “Shop Candy by Brand”, “Subscribe & Save” and “Shop All Black Tea”.
6 short forms
6 short forms (3 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 100 testimonial or review blocks, 4 customer or partner logos, 9 trust badges and “74K+ Happy Customers”.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
34 other companies contacted
Loading the homepage contacts 34 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 englishteastore.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
- jQuery
- E-commerce
- Shopify
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on englishteastore.com, including 24 speed issues, 1 SEO issue 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.