Website review, no card needed

dealerconnect.com.au logo

dealerconnect.com.au website review

Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 71 checks

This review found 37 issues worth fixing on dealerconnect.com.au, 12 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of dealerconnect.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dealerconnect.com.au at 0.7 s0.7 s
  2. dealerconnect.com.au at 1.5 s1.5 s
  3. dealerconnect.com.au at 2.2 s2.2 s
  4. dealerconnect.com.au at 2.9 s2.9 s
  5. dealerconnect.com.au at 3.6 s3.6 s
  6. dealerconnect.com.au at 4.4 s4.4 s
  7. dealerconnect.com.au at 5.1 s5.1 s
  8. dealerconnect.com.au at 5.8 s5.8 s

Speed

6 to fix52
  • Use efficient cache lifetimes

    3.5 s · 3.3 MB

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

  • Render-blocking requests

    2.2 s

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

  • Improve image delivery

    1.2 s · 240 KiB

    1 image could be 240 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Font display

    1.4 s

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

  • Mobile performance score: 52

    52/100

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

  • Reduce unused CSS

    470 ms · 55 KiB

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

  • Minify JavaScript

    160 ms · 10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Minify CSS

    160 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • 2 third-party services on the page

    2 third-party services load with your homepage (virtualyard.com.au and Google Fonts), adding 93 KiB and 2 ms of main-thread time.

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 168 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix50
  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • Cumulative Layout Shift: 0.293

    0.293

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

  • Time to Interactive: 6.6 s

    6.6 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix75
  • Page weight: 3.4 MB in 58 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 58 requests on a phone: images 2.9 MB (16), fonts 275 KiB (6) and scripts 91 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    245 KiB

    1 image is downloaded at several times the size a phone draws it, for example hero.png at 2,422 px wide, shown at 390 px. Resized copies would save about 245 KiB.

  • 2 images in older formats

    2 images (350 KiB) 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 below the first screen load straight away

    1 image further down the page (30 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.96 g

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

Accessibility

8 to fixGoogle 4881
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

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

  • All page content should be contained by landmarks (15 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • 2 links without text

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

  • Headings skip levels

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

1 checks passed
  • 24 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 8266
  • Title is long (164 characters)

    Your title is 164 characters, so Google will cut it off around 60: “Virtual Yard - Dealer Management System, Used Car Dealership Software, Motor Dealership S…”.

  • 11 H1 headlines

    There are 11 <h1> headlines (“DEALERCONNECT”, “BUY ONLINE” and “HISTORY CHECKS”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 2 problems

    Structured data found (AutomotiveBusiness, Organization and Product) but with 2 problems, for example “Organization: missing name”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at dealerconnect.com.au/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

1 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Virtual Yard is a new and used car dealership management system based completely in the cloud. Our saas for car dealers…”.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, 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.

  • No llms.txt

    There is no https://dealerconnect.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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (152 words), so crawlers that don't run JavaScript still read it.

Best practices

2 to fixGoogle 7378
  • 1 broken image

    1 image failed to load on a phone, for example https://virtualyard.com/australia/assets/img/logo-white.png.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://dealerconnect.com.au/' was loaded over HTTPS, but requested an insecure stylesheet …”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    10 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • Local business without LocalBusiness data

    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.

  • No analytics detected

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

  • Only about 158 words

    The homepage has only about 158 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop”.

  • 1 call to action

    The homepage has 1 call to action, for example “Buy Online”.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and a star rating.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • No consent tool detected

    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.

  • 6 other companies contacted

    Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at dealerconnect.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Google Cloud

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on dealerconnect.com.au, including 12 speed issues, 9 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25