tinyfootprintcoffee.com website review

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

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

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

Shopify costs a phone 85 ms of main-thread work and 332 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 127 KiB of JavaScript is downloaded but never used 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, rechargecdn.com and popupsmart.com and others), adding 500 KiB and 183 ms of main-thread time.

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

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

5 files are served with short cache lifetimes, so returning visitors download them again (42 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.

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

Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Colombia | Huila Pitalito | ASOBOMBO | Medium Roast - Tiny …”.

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

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

Your homepage downloads 2.4 MB in 146 requests on a phone: images 1.1 MB (15), other files 628 KiB (65) and scripts 470 KiB (60). Under 2 MB keeps phones on slow connections fast.

IMG_5169.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).

1 image (214 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 0.67 g of CO₂e: 80.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails 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.

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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There are 5 <h1> headlines (“”, “COLD PRESS ELIXIR” and “COLD PRESS ELIXIR”). One clear main headline is easier for people and search engines.

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

The homepage links to 84 pages on tinyfootprintcoffee.com and 11 external pages.

https://www.tinyfootprintcoffee.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.tinyfootprintcoffee.com/products/city-tavern-independence-blend declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://www.tinyfootprintcoffee.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://www.tinyfootprintcoffee.com/products/city-tavern-independence-blend all use the title “Shop Organic Carbon Negative Coffee – Tiny Footprint Coffee”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tinyfootprintcoffee.com/customer_authentication/redirect, https://www.tinyfootprintcoffee.com/collections/gifts-boxes, https://www.tinyfootprintcoffee.com/blogs/tiny-news, https://www.tinyfootprintcoffee.com/collections/decaf-coffee, https://www.tinyfootprintcoffee.com/collections/cold-brew-coffee and https://www.tinyfootprintcoffee.com/collections/gift-boxes and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tinyfootprintcoffee.com/collections/certified-organic-coffee, https://www.tinyfootprintcoffee.com/customer_authentication/redirect, https://www.tinyfootprintcoffee.com/collections/merchandise, https://www.tinyfootprintcoffee.com/collections/gifts-boxes, https://www.tinyfootprintcoffee.com/collections/coffee-blends and https://www.tinyfootprintcoffee.com/collections/single-origin-organic-coffee and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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.

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

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