revolutiontea.com website review

23 images could be 761 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

About 201 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

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

Your mobile performance score is 60. 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 800 ms.

8 third-party services load with your homepage (Clarity, Klaviyo and Shopify and others), adding 1.3 MB and 513 ms of main-thread time.

Shopify costs a phone 92 ms of main-thread work and 476 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 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

9 long tasks block the main thread while loading, the longest for 145 ms. During a long task the page ignores taps.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

11 KiB could be saved by minifying JavaScript.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Person placing hands on a festive box with two illustrated …”.

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

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

The first text or image appears after 3.1 s on a phone. Good is under 1.8 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 106 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Scripts block taps and scrolling for 202 ms in total while the page loads. Good is under 200 ms.

Your homepage downloads 3.3 MB in 332 requests on a phone: scripts 1.0 MB (149), images 1,018 KiB (34) and other files 774 KiB (115). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Links must have discernible text: 8 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (26 elements).

Your title is 75 characters, so Google will cut it off around 60: “Revolution Tea - Premium Tea Shop - Loose & Full Leaf Teas | Revolution Tea”.

There are 2 <h1> headlines (“Revolution Tea” and “UNWRAP THE MAGIC OF THE SEASON”). One clear main headline is easier for people and search engines.

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

The homepage links to 244 pages on revolutiontea.com and 13 external pages.

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

https://www.revolutiontea.com/collections/tea-bags-black-tea and https://www.revolutiontea.com/collections/loose-teas-black-tea all use the title “Black Tea | Revolution Tea”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.revolutiontea.com/collections/iced-tea has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.revolutiontea.com/collections/tea-bags-black-tea, https://www.revolutiontea.com/collections/tea-bags-green-white-tea, https://www.revolutiontea.com/collections/tea-bags-oolong-teas, https://www.revolutiontea.com/collections/tea-bags-herbal-teas, https://www.revolutiontea.com/collections/tea-bags-rooibos-tea and https://www.revolutiontea.com/collections/tea-bags-caffeine-free use the same meta description. A description written for each page earns more clicks.

https://www.revolutiontea.com/pages/ratings-and-reviews has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute preserveAspectRatio: Unrecognized enumerated value, "true".”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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