teadrop.com website review

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

2 third-party services load with your homepage (Shopify and okendo.io), adding 12.7 MB and 472 ms of main-thread time.

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

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

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

10 images could be 189 KiB 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.

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

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

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

About 17 KiB of CSS is downloaded but never applied on this page.

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 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Listen carefully”.

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

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

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

7 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 13.0 MB in 89 requests on a phone: media 11.2 MB (2), images 1.2 MB (29) and scripts 329 KiB (49). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (105 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 3.67 g of CO₂e: 440.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

The homepage links to 133 pages on teadrop.com and 19 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://teadrop.com/wishlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://teadrop.com/wholesale, https://teadrop.com/wishlist and https://teadrop.com/collections/best-selling-teas have no <h1> headline, so visitors and search engines get no clear main topic.

https://teadrop.com/products/english-breakfast, https://teadrop.com/products/my-melbourne, https://teadrop.com/products/chamomile-blossoms, https://teadrop.com/products/peppermint and https://teadrop.com/products/lemongrass-ginger took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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,039 words of visible text.

Opening the homepage sets 2 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.