freshventilation.com.au website review

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

40 images could be 4.9 MB 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.

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

7 third-party services load with your homepage (Shopify, Mapbox and Google CDN and others), adding 1.3 MB and 523 ms of main-thread time.

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

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

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

Mapbox costs a phone 239 ms of main-thread work and 403 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 276 KiB of JavaScript is downloaded but never used on this page.

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

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

About 22 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 6 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.

4 KiB could be saved by minifying JavaScript.

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 9.3 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 22.6 s. Good is under 3.8 s.

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

Real visitors wait 866 ms for your server to start answering (75th percentile). Good is under 800 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-11-07, real Chrome visitors' tap response (inp) went from 103 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 8.9 MB in 267 requests on a phone: images 6.7 MB (67), other files 1.0 MB (76) and scripts 814 KiB (107). Under 2 MB keeps phones on slow connections fast.

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

2 buttons have no accessible name, so screen readers announce just “button”.

44 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: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 11 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: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is 90 characters, so Google will cut it off around 60: “Fresh Ventilation | Home Ventilation, HRV/ERV and Subfloor Ventilation · Fresh Ventilation”.

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

Structured data found (LocalBusiness, Organization, Service and Store) but with 8 problems, for example “Service: missing name”.

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

The homepage links to 270 pages on freshventilation.com.au and 13 external pages.

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

3 errors were logged to the browser console while the page loaded, for example “Error: high-color: unknown property "high-color"”.

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

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

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 1,217 words of visible text.

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