vacc.com.au website review

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

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

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

About 745 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 979 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and azure.com and others), adding 1.4 MB and 1.5 s of main-thread time.

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

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

Facebook costs a phone 297 ms of main-thread work and 264 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.

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

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

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

Your largest element takes 42.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “From the start Join Now Member Portal”.

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

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

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

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

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

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

10 images weigh 26.0 MB together. On a phone connection a single image that size takes seconds.

16 images are downloaded at several times the size a phone draws them, for example vacc-ev-guide-banner.png at 5,407 px wide, shown at 317 px. Resized copies would save about 19.7 MB.

Your homepage downloads 15.3 MB in 105 requests on a phone: images 12.7 MB (32), scripts 1.7 MB (26) and fonts 707 KiB (10). Under 2 MB keeps phones on slow connections fast.

21 images (27.9 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.

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

Images must have alternative text: 5 elements on the page fail this check, rated critical by axe-core.

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

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

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

Headings skip levels (h1 → h3 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. (3 elements).

Your title is only 11 characters: “Home | VACC”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“Latest News” and “Upcoming Events”). One clear main headline is easier for people and search engines.

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

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

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

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

The homepage links to 46 pages on vacc.com.au and 13 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.

There is no https://vacc.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://vacc.com.au/Web/Web/Membership/Member-Services.aspx and https://vacc.com.au/Web/Membership/Member-Services.aspx are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://vacc.com.au/web all use the title “Home | VACC”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://vacc.com.au/Web/Web/Membership/Member-Services.aspx, https://vacc.com.au/Web/Membership/Member-Services.aspx, https://vacc.com.au/Web/Events-web.aspx, https://vacc.com.au/Web/Contact-Us.aspx, https://vacc.com.au/smart-register and https://vacc.com.au/Web/About.aspx and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://vacc.com.au/web, whose canonical is https://vacc.com.au/Web/web/Default.aspx. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://vacc.com.au/Web/News/Media-Releases/2026/World%20EV%20Day%20belongs%20to%20the%20industry,%20not%20just%20the%20technology.aspx, https://vacc.com.au/Web/News/General/The%202026%20AIA%20%20Victorian%20finalists.aspx, https://vacc.com.au/Web/News/Media-Releases/2026/Victoria's%20best-selling%20vehicle%20no%20longer%20appears%20in%20the%20VFACTS%20tables.aspx, https://vacc.com.au/Web/News/Media-Releases/2026/Cost-of-living%20squeeze%20forces%20one%20in%20three%20young%20Victorians%20to%20put%20off%20car%20servicing.aspx and https://vacc.com.au/smart-register have no <h1> headline, so visitors and search engines get no clear main topic.

https://vacc.com.au/Web/Events-web.aspx and https://vacc.com.au/smart-register have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is 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 “Failed to load resource: the server responded with a status of 404 ()”.

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

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

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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 416 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 8 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.