revivemushroomtea.com website review

17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

11 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

About 120 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

8 third-party services load with your homepage (ecomposer.app, loox.io and Shopify and others), adding 2.9 MB and 197 ms of main-thread time.

Shopify costs a phone 31 ms of main-thread work and 2.4 MB 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.

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

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Revive-22_31dd8168-9f6d-433c-b125-59d45b702244”.

The layout shifts by 0.418 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.1 MB in 186 requests on a phone: images 2.5 MB (17), other files 828 KiB (102) and scripts 407 KiB (41). Under 2 MB keeps phones on slow connections fast.

Revive-21_72c87f61-1caa-449a-8df1-a20db9fd2564.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

1 image (65 KiB) is 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.

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

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 6 characters: “REVIVE”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“” and “Revive Adaptogenic Tea”). One clear main headline is easier for people and search engines.

The homepage links to only 3 pages on your own site, so visitors and crawlers find few routes into the rest of it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://revivemushroomtea.com/collections/frontpage and https://revivemushroomtea.com/pages/revive-mushroom-tea_2 have no meta description, so Google writes the search snippet from whatever text it finds.

https://revivemushroomtea.com/products/revive-mushroom-tea, https://revivemushroomtea.com/collections/frontpage and https://revivemushroomtea.com/pages/revive-mushroom-tea_2 took over 3 s to send their HTML from our server.

We fetched 3 pages linked from your homepage and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Unable to decode Infinite pixel data: URIError: URI malformed”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 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 carries about 637 words of visible text.

Before a visitor clicks anything, the page loads Meta Pixel and TikTok 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.