more.com.au website review

58 files are served with short cache lifetimes, so returning visitors download them again (4.2 MB).

5 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.2 s faster on a phone.

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.4 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.5 MB and 1.6 s of main-thread time.

Google CDN costs a phone 647 ms of main-thread work and 1.1 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.

Google Tag Manager costs a phone 512 ms of main-thread work and 790 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 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

About 98 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

103 KiB could be saved by minifying JavaScript.

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

13 KiB could be saved by minifying CSS.

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

Your largest element takes 51.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

6 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-17, real Chrome visitors' tap response (inp) went from 131 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 9.9 MB in 137 requests on a phone: images 4.7 MB (24), scripts 3.0 MB (50) and fonts 1.3 MB (7). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example Dcy8vTZosNmRPSFvaQqb.png at 1,497 px wide, shown at 390 px. Resized copies would save about 1.4 MB.

6 images (3.7 MB) 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.

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

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (15 elements).

Your title is 73 characters, so Google will cut it off around 60: “nbn® Plans, Mobile Plans, Business Phone Systems & Business Data | More ™”.

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

There are 4 <h1> headlines (“Important”, “Heads Up!” and “Oops!”). One clear main headline is easier for people and search engines.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 116 pages on more.com.au and 8 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.

Your homepage links to https://more.com.au/36mth-eero, which answers with an error. Visitors hit a dead end and search engines drop it.

https://more.com.au/CommBankATLnbn25 has no <title>, so Google invents the link text in results.

https://more.com.au/personal/nbn-plans and https://more.com.au/personal/nbn-plans-wireless all use the title “nbn® Plans with Unlimited Data | More ™”. Search engines can't tell which page to show for a search, so each competes with the others.

https://more.com.au/CommBankATLnbn25 has no meta description, so Google writes the search snippet from whatever text it finds.

https://more.com.au/personal/nbn-plans and https://more.com.au/personal/nbn-plans-wireless use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://more.com.au/personal/nbn-plans-wireless, whose canonical is https://more.com.au/personal/nbn-plans. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://more.com.au/CommBankATLnbn25 has no <h1> headline, so visitors and search engines get no clear main topic.

https://more.com.au/policies, https://more.com.au/personal/nbn-plans-wireless and https://more.com.au/CommBankATLnbn25 took over 3 s to send their HTML from our server.

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

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

1 image is served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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