wagflags.com.au website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and lvrgseo.com and others), adding 732 KiB and 144 ms of main-thread time.

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

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

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

1 long task block the main thread while loading, the longest for 80 ms. During a long task the page ignores taps.

16 KiB could be saved by minifying JavaScript.

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

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 JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying CSS.

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

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

The layout shifts by 0.139 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

13 images are downloaded at several times the size a phone draws them, for example 14.webp at 800 px wide, shown at 182 px. Resized copies would save about 819 KiB.

Your homepage downloads 3.6 MB in 295 requests on a phone: images 1.5 MB (25), other files 1.0 MB (141) and scripts 776 KiB (114). Under 2 MB keeps phones on slow connections fast.

14 images (1.6 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.

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

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

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 63 pages on wagflags.com.au and 1 external page.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://wagflags.com.au/blogs/news, https://wagflags.com.au/policies/shipping-policy and https://wagflags.com.au/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://wagflags.com.au/pages/how-it-works, https://wagflags.com.au/pages/about-us, https://wagflags.com.au/products/wag-flag-starter-set, https://wagflags.com.au/products/wag-flag-dual-set and https://wagflags.com.au/products/wag-flag-complete-set have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

2 errors were logged to the browser console while the page loaded, for example “Identifier 'EmailSignupBlock' has already been declared”.

Social proof on the homepage: 40 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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