superfeast.com.au website review

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

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

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

8 third-party services load with your homepage (Yotpo, rebuyengine.com and Google Tag Manager and others), adding 1.7 MB and 1.1 s of main-thread time.

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

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

Polyfills for old browsers add 96 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

Yotpo costs a phone 377 ms of main-thread work and 506 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 2,434 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

rebuyengine.com costs a phone 200 ms of main-thread work and 385 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.

roseperl.com costs a phone 122 ms of main-thread work and 309 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.

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

5 images could be 52 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.

14 KiB could be saved by minifying JavaScript.

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

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.

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.

Real visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tried supplement after supplement and still feel flat, depl…”.

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

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

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

For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.

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

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

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

14 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' largest content (lcp) went from 3.0 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 265 requests on a phone: scripts 2.1 MB (73), other files 882 KiB (149) and images 302 KiB (21). Under 2 MB keeps phones on slow connections fast.

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

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

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

4 visible links have no text or label, so screen readers cannot say where they go.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 70 characters, so Google will cut it off around 60: “SuperFeast Australia, premium Di Dao medicinal mushrooms & tonic herbs”.

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

The homepage links to 265 pages on superfeast.com.au and 6 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.superfeast.com.au/pages/black-friday-vip-2026 has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.superfeast.com.au/pages/black-friday-vip-2026, https://www.superfeast.com.au/collections/all-products-1, https://www.superfeast.com.au/collections/signature-blends, https://www.superfeast.com.au/products/masons-mushrooms-powdered-extract-blend, https://www.superfeast.com.au/products/qi and https://www.superfeast.com.au/products/jing-herbs and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.superfeast.com.au/products/masons-mushrooms-powdered-extract-blend, https://www.superfeast.com.au/products/qi, https://www.superfeast.com.au/products/jing-herbs, https://www.superfeast.com.au/products/jing-capsules, https://www.superfeast.com.au/products/neural-nectar and https://www.superfeast.com.au/products/womens-rhythm and 5 others 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.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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