10000coffee.com website review

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

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

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

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

About 445 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.

297 KiB could be saved by minifying JavaScript.

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

4 third-party services load with your homepage (imweb.me, Google Tag Manager and JSDelivr CDN and others), adding 3.8 MB and 561 ms of main-thread time.

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

imweb.me costs a phone 383 ms of main-thread work and 2.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.

46 KiB could be saved by minifying CSS.

JSDelivr CDN costs a phone 0 ms of main-thread work and 986 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.

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

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

Your largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

2 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.3 MB in 149 requests on a phone: scripts 1.5 MB (100), fonts 1.4 MB (7) and images 976 KiB (8). Under 2 MB keeps phones on slow connections fast.

3 images (946 KiB) 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 1.23 g of CO₂e: 147.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Document should not have more than one main 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.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 24 pages on 10000coffee.com and 5 external pages.

/, https://10000coffee.com/BRAND, https://10000coffee.com/location, https://10000coffee.com/locationau, https://10000coffee.com/55 and https://10000coffee.com/52 and 5 others all use the title “TENTHOUSAND”. Search engines can't tell which page to show for a search, so each competes with the others.

https://10000coffee.com/BRAND, https://10000coffee.com/location, https://10000coffee.com/locationau, https://10000coffee.com/55, https://10000coffee.com/52 and https://10000coffee.com/44 and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://10000coffee.com/BRAND, https://10000coffee.com/location, https://10000coffee.com/locationau, https://10000coffee.com/55, https://10000coffee.com/52 and https://10000coffee.com/44 and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://10000coffee.com/locationau, https://10000coffee.com/55, https://10000coffee.com/52, https://10000coffee.com/44, https://10000coffee.com/locationusa and https://10000coffee.com/46 and 1 other have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://10000coffee.com/contact took over 3 s to send its HTML from our server.

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

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

6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://vendor-cdn.imweb.me/minify_css/vendor_red_10.css?1794320053' from origin 'https://…”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 18 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 8 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.