aldi.com.au website review

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

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

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

16 images could be 859 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.

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

8 third-party services load with your homepage (Adobe Tag Manager, Facebook and TikTok and others), adding 737 KiB and 540 ms of main-thread time.

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

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

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

Desktop scores 78 but mobile only 48. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ALDI Special Buys”.

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

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

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

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

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

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

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

Your homepage downloads 2.8 MB in 193 requests on a phone: scripts 1.3 MB (78), images 1.1 MB (55) and HTML 108 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 226 pages on aldi.com.au and 24 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/special-buys/2026-10-17, /special-buys/2026-10-21, /special-buys/2026-10-24, /special-buys/2026-10-28 and /special-buys/2026-10-31 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/special-buys/2026-10-17, /special-buys/2026-10-21, /special-buys/2026-10-24, /special-buys/2026-10-28 and /special-buys/2026-10-31 all use the title “On sale Date”. Search engines can't tell which page to show for a search, so each competes with the others.

/special-buys/2026-10-17, /special-buys/2026-10-21, /special-buys/2026-10-24, /special-buys/2026-10-28, /special-buys/2026-10-31 and /products/christmas/baking/k/1588161425467056 and 5 others 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 /tools/features/special-buys, whose canonical is /special-buys. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Hydration completed but contains mismatches.”.

Chrome logged issues while loading the page (“Cookie”).

Requests the geolocation permission on page load.

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://doordash.sng.link/Afic8/ywm0/j2lq?_dl=https://www.doordash.com%2Fsdl/tag/c/ALDI%3Futm_source%3DWeblinks%26utm_medium%3DWeblinks%26utm_campaign%3DCX_AU_MR_WL_WL_STO_CAUXXX__PARTNR_ALDI_WEBSITE%26audience_tag%3DAldi-takeover&_smtype=3&_forward_params=1&pcn=CX_AU_MR_WL_WL_STO_CAUXXX__PARTNR_ALDI_WEBSITE&_fallback_redirect=https%3A%2F%2Fwww.doordash.com%2Fsdl/tag/c/ALDI%3Futm_source%3DWeblinks%26utm_campaign%3DCX_AU_MR_WL_WL_STO_CAUXXX__PARTNR_ALDI_WEBSITE%26utm_medium%3DWeblinks%26audience_tag%3DAldi-takeover&_force_redirect=1.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

aldi.com.au has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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