valleyoftea.com website review

12 images could be 424 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

A phone's processor spends 2.3 s on main-thread work while loading, 821 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,682 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 98 ms of main-thread work and 458 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.

About 49 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.

4 third-party services load with your homepage (Shopify, JSDelivr CDN and shop.app and others), adding 606 KiB and 131 ms of main-thread time.

About 99 KiB of JavaScript is downloaded but never used on this page.

9 files are served with short cache lifetimes, so returning visitors download them again (63 KiB).

1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.

Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Real visitors wait 895 ms for your server to start answering (75th percentile). Good is under 800 ms.

The page becomes fully interactive after 5.3 s. Good is under 3.8 s.

26 images have no width and height attributes, so the layout jumps as each one loads.

Visually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.

Your homepage downloads 4.5 MB in 361 requests on a phone: images 2.0 MB (21), other files 1,018 KiB (180) and scripts 757 KiB (132). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (293 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 153.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

11 elements use ARIA attributes their role does not allow, which confuses screen readers.

10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 81 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

16 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h3, h1 → h3 and h2 → h6), which makes the page harder to scan with a screen reader.

Your title is only 22 characters: “Tea shop Valley of Tea”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“Welcome to Valley of Tea”, “Our teas are crafted by artisan farmers.” and ““Tea where you can see, smell and taste the hard …”). One clear main headline is easier for people and search engines.

7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

3 links have no real href, so search engines can't follow them.

The homepage links to 108 pages on valleyoftea.com and 0 external pages.

There is no https://www.valleyoftea.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.

We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.

8 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Swiper is not defined”.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,076 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

Opening the homepage sets 10 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.