weathertex.com.au website review

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

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

12 images could be 6.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 50 (desktop: 72). Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (Intercom, Google Tag Manager and Hubspot and others), adding 656 KiB and 645 ms of main-thread time.

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

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

About 214 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

10 KiB could be saved by minifying JavaScript.

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

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 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

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

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

Scripts block taps and scrolling for 281 ms in total while the page loads. Good is under 200 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-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.7 MB in 194 requests on a phone: images 9.4 MB (38), other files 1.2 MB (28) and scripts 1.1 MB (78). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example natural.webp at 600 px wide, shown at 195 px. Resized copies would save about 3 KiB.

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

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

[role="img"] and [role="image"] elements must have alternative text: 21 elements on the page fail this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

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

20 links have no real href, so search engines can't follow them.

No XML sitemap at https://weathertex.com.au/sitemap_index.xml, so Google discovers your pages only by following links.

The homepage links to 109 pages on weathertex.com.au and 11 external pages.

There is no https://weathertex.com.au/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.

https://weathertex.com.au/sample-page is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://weathertex.com.au/contact-us, https://weathertex.com.au/sample-page, https://weathertex.com.au/events-webinars, https://weathertex.com.au/sustainability-report, https://weathertex.com.au/products and https://weathertex.com.au/blog_post/we-did-it-again-weathertex-earns-platinum-nature-positive-rating-of-153 and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://weathertex.com.au/wp-content/uploads/2024/11/image-3.png.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 1,006 words of visible text.

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