noonbrew.co website review

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

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

8 third-party services load with your homepage (Shopify, alia-prod.com and Klaviyo and others), adding 2.7 MB and 1.5 s of main-thread time.

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

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

About 622 KiB of JavaScript is downloaded but never used on this page.

alia-prod.com costs a phone 436 ms of main-thread work and 305 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.

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

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

12 images could be 216 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.

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

12 KiB could be saved by minifying JavaScript.

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

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

9 files block the first paint until they finish downloading. Deferring or inlining them could save 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.

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

Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE BEST DEAL TO SLEEP ON Better sleep, better mornings, be…”.

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

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

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

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

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

Your homepage downloads 6.3 MB in 414 requests on a phone: images 2.5 MB (63), scripts 2.1 MB (157) and other files 857 KiB (161). Under 2 MB keeps phones on slow connections fast.

hf_20260116_030027_69f896be-c6b9-47d6-b821-8c81d52d1b24_1.pn weighs 1.2 MB. On a phone connection a single image that size takes seconds.

2 images further down the page (87 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 1.78 g of CO₂e: 213.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 158 pages on noonbrew.co and 20 external pages.

https://moonbrew.co/pages/store-locator, https://moonbrew.co/pages/fit-bundle and https://moonbrew.co/pages/3-pack have no meta description, so Google writes the search snippet from whatever text it finds.

https://moonbrew.co/pages/product-finder-quiz, https://moonbrew.co/pages/reviews, https://moonbrew.co/pages/faqs, https://moonbrew.co/pages/fit-bundle, https://moonbrew.co/products/moonbrew-starter-kit and https://moonbrew.co/products/moonbrew-jar have no <h1> headline, so visitors and search engines get no clear main topic.

https://moonbrew.co/products/moonbrew-jar has 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.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97012602&Ver=2&mid=9ab50e05-1af8-4b14-81c3-82d08a9d8168&bo=1&sid=c10247f0d8f611f196487341024042e5&vid=c1024de0d8f611f1b4d8d3668bb1357c&vids=1&msclkid=N&pi=918639831&lg.

9 of 44 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 “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

The homepage carries about 1,035 words of visible text.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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 55 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 79 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.