Website review, no card needed

marshallwhite.com.au logo

marshallwhite.com.au website review

Visit site (opens in a new tab)Reviewed 31 October 202647 issues · 94 checks

This review found 47 issues worth fixing on marshallwhite.com.au, 24 of them high impact, across 94 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
5.2 s2.6 sMay 9Oct 244.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.2 s
May 16, 20264.0 s
May 23, 20263.9 s
May 30, 20263.5 s
Jun 6, 20263.3 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20263.0 s
Aug 1, 20263.1 s
Aug 8, 20263.3 s
Aug 15, 20263.4 s
Aug 22, 20263.8 s
Aug 29, 20264.4 s
Sep 5, 20264.5 s
Sep 12, 20264.8 s
Sep 19, 20264.3 s
Sep 26, 20263.8 s
Oct 3, 20264.2 s
Oct 10, 20264.4 s
Oct 17, 20264.6 s
Oct 24, 20264.9 s
Real-visitor tap response (INP)75th percentile, phones
334 ms219 msMay 9Oct 24321 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026238 ms
May 16, 2026237 ms
May 23, 2026232 ms
May 30, 2026238 ms
Jun 6, 2026245 ms
Jun 13, 2026245 ms
Jun 20, 2026254 ms
Jun 27, 2026262 ms
Jul 4, 2026262 ms
Jul 11, 2026263 ms
Jul 18, 2026262 ms
Jul 25, 2026262 ms
Aug 1, 2026262 ms
Aug 8, 2026286 ms
Aug 15, 2026291 ms
Aug 22, 2026287 ms
Aug 29, 2026277 ms
Sep 5, 2026270 ms
Sep 12, 2026262 ms
Sep 19, 2026262 ms
Sep 26, 2026281 ms
Oct 3, 2026286 ms
Oct 10, 2026304 ms
Oct 17, 2026315 ms
Oct 24, 2026321 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 marshallwhite.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. marshallwhite.com.au at 2.3 s2.3 s
  2. marshallwhite.com.au at 4.6 s4.6 s
  3. marshallwhite.com.au at 6.9 s6.9 s
  4. marshallwhite.com.au at 9.2 s9.2 s
  5. marshallwhite.com.au at 11.5 s11.5 s
  6. marshallwhite.com.au at 13.8 s13.8 s
  7. marshallwhite.com.au at 16.1 s16.1 s
  8. marshallwhite.com.au at 18.4 s18.4 s

Speed

14 to fix17
  • Use efficient cache lifetimes

    1.2 s · 8.8 MB

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

  • Reduce unused JavaScript

    2.4 s · 612 KiB

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

  • Document request latency

    1.7 s

    The HTML itself could arrive about 1.7 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    1.7 s

    Reduce initial server response time. Google estimates savings of 1.7 s 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: 17

    17/100

    Your mobile performance score is 17. 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, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Improve image delivery

    900 ms · 1,018 KiB

    15 images could be 1,018 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

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

  • Google Tag Manager adds 760 ms

    760 ms

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

  • Render-blocking requests

    750 ms

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

  • Facebook adds 426 ms

    426 ms

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

  • Server response: 1.8 s

    1.8 s

    Your server takes 1.8 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 1,693 HTML elements

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

  • 17 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 40 KiB

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

  • Legacy JavaScript

    13 KiB

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

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

Core Web Vitals

13 to fix0
  • 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 LCP: 4.9 s

    4.9 s

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

  • Real-user CLS: 6.22

    6.22

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

  • Real-user FCP: 3.6 s

    3.6 s

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • Cumulative Layout Shift: 5.334

    5.334

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

  • Largest Contentful Paint: 18.7 s

    18.7 s

    Your largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Search by suburb, postcode or address”. Most of its time is element render delay (12.3 s).

  • Speed Index: 23.4 s

    23.4 s

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

  • Time to Interactive: 23.8 s

    23.8 s

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

  • Total Blocking Time: 873 ms

    873 ms

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

  • Real-user INP: 354 ms

    354 ms

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

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

    +34%

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

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

  • Largest content (LCP) got 17% slower for real visitors

    +17%

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

Images and page weight

1 to fix70
  • Page weight: 17.2 MB in 107 requests

    17.2 MB

    Your homepage downloads 17.2 MB in 107 requests on a phone: media 12.4 MB (2), images 2.7 MB (26) and scripts 1.8 MB (31). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (45 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 4.9 g of CO₂ per visit

    4.89 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 7791
  • 5 buttons without a name

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

  • Form elements should have a visible label (8 elements)

    Form elements should have a visible label: 8 elements on the page fail this check, rated serious by axe-core.

  • 3 tap targets too small

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

  • 265 form fields without a label

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

  • Zoom is disabled

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 46 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 8392
  • No canonical URL

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 180 internal links, 7 external

    The homepage links to 180 pages on marshallwhite.com.au and 7 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Looking to Buy, Sell or Lease a property in Melbourne? Marshall White are the Leading Prestige Real Estate Agents for L…”.

  • One H1 headline

    Your main headline reads: “Leaders in prestige property”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Best Luxury Real Estate Agents in Melbourne | Marshall White”.

  • Structured data in place

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.marshallwhite.com.au/sitemap-index.xml.

AI search readiness

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

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

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.marshallwhite.com.au/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix98
  • 3 pages share a meta description

    https://www.marshallwhite.com.au/pre-release, https://www.marshallwhite.com.au/sold and https://www.marshallwhite.com.au/leased use the same meta description. A description written for each page earns more clicks.

  • 10 pages slow to respond

    https://www.marshallwhite.com.au/buy, https://www.marshallwhite.com.au/pre-release, https://www.marshallwhite.com.au/upcoming-auctions, https://www.marshallwhite.com.au/upcoming-inspections, https://www.marshallwhite.com.au/projects and https://www.marshallwhite.com.au/sold and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 2 broken images

    2 images failed to load on a phone, for example https://www.marshallwhite.com.au/assets/santa-desktop-CJeczWuX.jpg.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • No call to action on the first screen

    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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • A 12-field form

    Your longest form asks for 12 fields (0 required). Every extra field lowers completion.

  • No opening hours

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

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

  • About 319 words of copy

    The homepage carries about 319 words of visible text.

4 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Buy”, “Request Appraisal” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

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

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 Pinterest Tag (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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 marshallwhite.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
Gatsby
Analytics
Google Tag Manager
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on marshallwhite.com.au, including 27 speed issues, 3 SEO issues and 4 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