houseofmacadamias.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Intercom and loox.io and others), adding 1.3 MB and 1.1 s of main-thread time.

22 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

47 KiB could be saved by minifying JavaScript.

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

Google Tag Manager costs a phone 227 ms of main-thread work and 316 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.

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

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

About 34 KiB of CSS is downloaded but never applied on this page.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 19.9 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 27.9 s. Good is under 3.8 s.

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

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

Real visitors wait 253 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 103.5 MB in 275 requests on a phone: media 97.7 MB (11), images 2.8 MB (60) and scripts 1.7 MB (84). Under 2 MB keeps phones on slow connections fast.

macadamia-oil.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 further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 29.33 g of CO₂e: 3519.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

19 buttons have no accessible name, so screen readers announce just “button”.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

4 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Headings skip levels (h1 → h4, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.

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

There are 6 <h1> headlines (“Raw macadamias”, “Macadamia nuts” and “100% mac oil”). One clear main headline is easier for people and search engines.

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

The homepage links to 50 pages on houseofmacadamias.com and 10 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.

https://www.houseofmacadamias.com/collections/macadamia-nuts, https://www.houseofmacadamias.com/collections/macadamia-nut-butters and https://www.houseofmacadamias.com/collections/snack-bars have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 404 ()”.

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

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