chefsedge.com.au website review

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

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

8 third-party services load with your homepage (Shopify, returngo.ai and Clarity and others), adding 1.5 MB and 1.3 s of main-thread time.

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

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

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

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

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

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

returngo.ai costs a phone 274 ms of main-thread work and 239 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,032 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

smile.io costs a phone 96 ms of main-thread work and 353 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.

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

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

2 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Yu Kurosaki Bunka knife, hand-forged in Japan”.

Scripts block taps and scrolling for 649 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' tap response (inp) went from 82 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 4.0 MB in 283 requests on a phone: images 1.4 MB (30), scripts 1.3 MB (116) and other files 885 KiB (118). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example DSC02488_16d823a7-2b19-443e-aa8d-cc7e312a9396.jpg at 600 px wide, shown at 93 px. Resized copies would save about 141 KiB.

2 images (107 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

7 elements hidden from screen readers can still receive keyboard focus.

Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

5 links inside paragraphs rely on colour alone to stand out.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

Structured data found (Organization, Store and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.chefs-edge.com.au)”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 336 pages on chefsedge.com.au and 16 external pages.

https://www.chefs-edge.com/pages/rewards and https://www.chefs-edge.com/pages/swym-wishlist have no meta description, so Google writes the search snippet from whatever text it finds.

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

4 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://judge.me/api/v1/reviews?shop_domain=chefs-edgeau.myshopify.com&api_token=8mwvKSTu1a9ajpIV8k…”.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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