terrakaffe.com website review

About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.0 s faster on a phone.

43 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, replocdn.com and Facebook and others), adding 4.9 MB and 1.6 s of main-thread time.

Google Tag Manager costs a phone 582 ms of main-thread work and 1.0 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.

replocdn.com costs a phone 334 ms of main-thread work and 1.2 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.

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

71 KiB could be saved by minifying JavaScript.

13 images could be 308 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

59 KiB could be saved by minifying CSS.

6 KiB JavaScript is shipped twice across bundles.

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.

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 30.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Black Friday Starts Early. For a limited time, our best-sel…”.

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

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

For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.5 MB in 409 requests on a phone: images 5.4 MB (45), scripts 4.9 MB (169) and other files 827 KiB (167). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example 1773165299764-1773165293313-image.png at 1,509 px wide, shown at 145 px. Resized copies would save about 3.4 MB.

1773165299764-1773165293313-image.png weighs 2.8 MB. On a phone connection a single image that size takes seconds.

3 images (3.3 MB) 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.

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

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

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

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

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

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

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

ARIA role should be appropriate for the element: 2 elements on the page fail 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.

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

There are 8 <h1> headlines (“$100 Off Demi”, “$200 Off Demi, Shipping Now” and “Always fresh,Forever cutting edge.”). One clear main headline is easier for people and search engines.

The homepage links to 91 pages on terrakaffe.com and 17 external pages.

Your Organization JSON-LD is missing logo, 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://www.terrakaffe.com/pages/tk-flow-rental and https://www.terrakaffe.com/pages/loyalty are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.terrakaffe.com/collections/coffee and https://www.terrakaffe.com/bestsellers all use the title “Coffee | Terra Kaffe – Terra Kaffe”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.terrakaffe.com/pages/tk-flow-rental, https://www.terrakaffe.com/pages/loyalty, https://www.terrakaffe.com/pages/referrals, https://www.terrakaffe.com/collections/care-cleaning, https://www.terrakaffe.com/collections/drinkware-extras and https://www.terrakaffe.com/collections/tk-02-extra-parts and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.terrakaffe.com/collections/coffee and https://www.terrakaffe.com/bestsellers use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.terrakaffe.com/bestsellers, whose canonical is https://www.terrakaffe.com/collections/coffee. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.terrakaffe.com/pages/tk-flow-rental and https://www.terrakaffe.com/collections/coffee have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.terrakaffe.com/bestsellers took over 3 s to send its HTML from our server.

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

3 images failed to load on a phone, for example https://pixel.streetmetrics.io/pixel/637d5fda-a797-4735-aee6-917fcfde5d52.

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

5 errors were logged to the browser console while the page loaded, for example “Identifier 'harkScript' has already been declared”.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 7 mores (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 46 cookies, 1 of them by other companies (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 81 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.