wakeandbrewcoffee.com website review

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

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

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

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

6 images could be 114 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Adroll and others), adding 885 KiB and 402 ms of main-thread time.

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

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

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

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

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

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

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

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 2.1 MB in 167 requests on a phone: other files 734 KiB (93), scripts 727 KiB (42) and images 533 KiB (15). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (232 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 0.59 g of CO₂e: 70.3 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.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 2 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.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is only 22 characters: “Wake & Brew Coffee Co.”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 32 characters: “All Adventure Begins With Coffee”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“” and “Freshly Roasted Whole Bean Coffee”). One clear main headline is easier for people and search engines.

The homepage links to 48 pages on wakeandbrewcoffee.com and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://wakeandbrewcoffee.com/collections/whole-bean-coffee/products/white-eagle-costa-rica-arabica-whole-bean, which answers with an error. Visitors hit a dead end and search engines drop it.

https://wakeandbrewcoffee.com/collections/shop-everything, https://wakeandbrewcoffee.com/collections/whole-bean-coffee, https://wakeandbrewcoffee.com/collections/pancakes, https://wakeandbrewcoffee.com/collections/mugs, https://wakeandbrewcoffee.com/blogs/blog and https://wakeandbrewcoffee.com/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://wakeandbrewcoffee.com/products/black-bear-kenyan-arabica-whole-bean, whose canonical is https://wakeandbrewcoffee.com/products/black-bear-kenyan-arabica-whole-bean-coffee. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://wakeandbrewcoffee.com/products/black-bear-kenyan-arabica-whole-bean has no <h1> headline, so visitors and search engines get no clear main topic.

https://wakeandbrewcoffee.com/collections/whole-bean-coffee, https://wakeandbrewcoffee.com/collections/pancakes, https://wakeandbrewcoffee.com/pages/join-the-adventure, https://wakeandbrewcoffee.com/pages/quality and https://wakeandbrewcoffee.com/pages/contact 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://wakeandbrewcoffee.com/products/black-bear-kenyan-arabica-whole-bean took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 17 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: the server responded with a status of 404 ()”.

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

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 230 words of visible text; thin pages give Google and first-time buyers little to go on.

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