overlookcoffeeco.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Yotpo and appstle.com and others), adding 1.2 MB and 473 ms of main-thread time.

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

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

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

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

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

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

About 19 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10 ms faster on a phone.

Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need.

8 KiB could be saved by minifying JavaScript.

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 13.0 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 13.1 s. Good is under 3.8 s.

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

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

24 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.8 MB in 196 requests on a phone: media 10.7 MB (1), scripts 1.3 MB (92) and images 978 KiB (25). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example FredyOrantesBuenaVistaNatural_bag_photo.png at 2,035 px wide, shown at 172 px. Resized copies would save about 251 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 3.91 g of CO₂e: 469.1 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.

1 image has 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.

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

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

Your <h1> is empty.

The homepage links to 60 pages on overlookcoffeeco.com and 6 external pages.

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

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

https://overlookcoffeeco.com/collections/all, https://overlookcoffeeco.com/customer_authentication/redirect, https://overlookcoffeeco.com/policies/shipping-policy, https://overlookcoffeeco.com/collections/all-coffee, https://overlookcoffeeco.com/collections/blends and https://overlookcoffeeco.com/collections/single-origins and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://overlookcoffeeco.com/customer_authentication/redirect, https://overlookcoffeeco.com/pages/subscriptions, https://overlookcoffeeco.com/pages/blogs and https://overlookcoffeeco.com/pages/location have no <h1> headline, so visitors and search engines get no clear main topic.

https://overlookcoffeeco.com/collections/all and https://overlookcoffeeco.com/collections/single-origins took over 3 s to send their HTML from our server.

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

1 error was 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 504 words of visible text.

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