Website review, no card needed

rdoequipment.com.au logo

rdoequipment.com.au website review

Visit site (opens in a new tab)Reviewed 28 October 202644 issues · 92 checks

This review found 44 issues worth fixing on rdoequipment.com.au, 21 of them high impact, across 92 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

Real-visitor load time (LCP)75th percentile, phones
3.3 s2.8 sMay 9Oct 242.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20263.1 s
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
218 ms132 msMay 9Oct 24205 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026144 ms
May 16, 2026146 ms
May 23, 2026144 ms
May 30, 2026143 ms
Jun 6, 2026142 ms
Jun 13, 2026146 ms
Jun 20, 2026150 ms
Jun 27, 2026149 ms
Jul 4, 2026152 ms
Jul 11, 2026152 ms
Jul 18, 2026151 ms
Jul 25, 2026152 ms
Aug 1, 2026153 ms
Aug 8, 2026162 ms
Aug 15, 2026171 ms
Aug 22, 2026183 ms
Aug 29, 2026193 ms
Sep 5, 2026192 ms
Sep 12, 2026192 ms
Sep 19, 2026190 ms
Sep 26, 2026196 ms
Oct 3, 2026202 ms
Oct 10, 2026205 ms
Oct 17, 2026208 ms
Oct 24, 2026205 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. rdoequipment.com.au at 2.2 s2.2 s
  2. rdoequipment.com.au at 4.3 s4.3 s
  3. rdoequipment.com.au at 6.5 s6.5 s
  4. rdoequipment.com.au at 8.7 s8.7 s
  5. rdoequipment.com.au at 10.9 s10.9 s
  6. rdoequipment.com.au at 13.0 s13.0 s
  7. rdoequipment.com.au at 15.2 s15.2 s
  8. rdoequipment.com.au at 17.4 s17.4 s

Speed

14 to fix26
  • Use efficient cache lifetimes

    5.0 s · 1.4 MB

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

  • Reduce unused JavaScript

    5.0 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.

  • Improve image delivery

    3.9 s · 2.0 MB

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

  • Render-blocking requests

    3.6 s

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

  • Reduce unused CSS

    1.1 s · 202 KiB

    About 202 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 26

    26/100

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

  • Main-thread work: 4.5 s

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

  • 3,603 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 2.2 MB and 1.1 s of main-thread time.

  • Legacy JavaScript

    450 ms · 64 KiB

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

  • YouTube adds 346 ms

    346 ms

    YouTube costs a phone 346 ms of main-thread work and 977 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.

  • Google Tag Manager adds 300 ms

    300 ms

    Google Tag Manager costs a phone 300 ms of main-thread work and 360 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.

  • 15 long tasks on the main thread

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

  • Facebook adds 238 ms

    238 ms

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

  • Minify CSS

    150 ms · 24 KiB

    24 KiB could be saved by minifying CSS.

  • Minify JavaScript

    52 KiB

    52 KiB could be saved by minifying JavaScript.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 562 ms

    562 ms

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

Core Web Vitals

12 to fix67
  • Fails Core Web Vitals for real visitors

    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-user TTFB: 2.5 s

    2.5 s

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

  • Largest Contentful Paint: 26.9 s

    26.9 s

    Your largest element takes 26.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SAVE ON CLEARANCE EQUIPMENT VIEW INVENTORY”.

  • Speed Index: 21.9 s

    21.9 s

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

  • Time to Interactive: 30.2 s

    30.2 s

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

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Cumulative Layout Shift: 0.338

    0.338

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Tap response (INP) got 42% slower for real visitors

    +42%

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • Total Blocking Time: 558 ms

    558 ms

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

  • 27 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

2 checks passed
  • Real-user INP: 191 ms

    191 ms

    Real visitors wait 191 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

Images and page weight

4 to fix28
  • Page weight: 6.6 MB in 175 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 175 requests on a phone: images 3.7 MB (48), scripts 2.5 MB (59) and stylesheets 250 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    John-Deere-E210LC-excavator-RDO-Equipment-Studio-5.jpg weighs 555 KiB. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    569 KiB

    8 images are downloaded at several times the size a phone draws them, for example 853050635_18211244545370292_8906300457322480077_nfull.webp at 640 px wide, shown at 110 px. Resized copies would save about 569 KiB.

  • 14 images below the first screen load straight away

    14 images further down the page (978 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (119 KiB) is 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.

  • About 1.9 g of CO₂ per visit

    1.88 g

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

Accessibility

7 to fixGoogle 8792
  • Invalid ARIA attributes

    4 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 3 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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)

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

  • 5 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (2 elements)

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 7793
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links crawlers can't follow

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 221 internal links, 83 external

    The homepage links to 221 pages on rdoequipment.com.au and 83 external pages.

7 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “RDO Equipment is your partner across NT, QLD & NSW for John Deere Construction & Forestry, and Agriculture & Turf equip…”.

  • One H1 headline

    Your main headline reads: “YOUR PARTNER AS YOU GROW AND BUILD THE WORLD.”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “John Deere Machinery Dealer - RDO Equipment”.

  • Canonical URL set

    The canonical URL is https://www.rdoequipment.com.au/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.rdoequipment.com.au/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

100
  • 3 pages slow to respond

    https://www.rdoequipment.com.au/compact-track-loaders, https://www.rdoequipment.com.au/forestry and https://www.rdoequipment.com.au/tracked-harvesters took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7382
  • 1 broken image

    1 image failed to load on a phone, for example https://www.rdoequipment.com.au/.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • A 17-field form

    Your longest form asks for 17 fields (7 required). Every extra field lowers completion.

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

  • About 438 words of copy

    The homepage carries about 438 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 10 calls to action

    The homepage has 10 calls to action, for example “Register”, “Contact Us” and “Shop Online”.

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks, 2 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 1 of them by other companies (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.

  • 28 other companies contacted

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

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

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Host Universal Pty Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on rdoequipment.com.au, including 26 speed issues, 3 SEO issues and 1 conversion gap. 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