Website review, no card needed

dilate.com.au logo

dilate.com.au website review

Visit site (opens in a new tab)Reviewed 18 October 202624 issues · 74 checks

This review found 24 issues worth fixing on dilate.com.au, 5 of them high impact, across 74 checks. The most urgent: main-thread work: 9.0 s. 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.9 s969 msApr 25Sep 263.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.8 s
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20261.9 s
May 23, 20261.8 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.8 s
Jun 27, 20262.1 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20262.3 s
Sep 5, 20263.2 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.0 s

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 dilate.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dilate.com.au at 1.0 s1.0 s
  2. dilate.com.au at 2.1 s2.1 s
  3. dilate.com.au at 3.1 s3.1 s
  4. dilate.com.au at 4.1 s4.1 s
  5. dilate.com.au at 5.1 s5.1 s
  6. dilate.com.au at 6.2 s6.2 s
  7. dilate.com.au at 7.2 s7.2 s
  8. dilate.com.au at 8.2 s8.2 s

Speed

11 to fix61
  • Main-thread work: 9.0 s

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

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

  • Reduce initial server response time

    971 ms

    Reduce initial server response time. Google estimates savings of 971 ms on a phone.

  • Document request latency

    950 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (hsappstatic.net, Hubspot and hubspotusercontent-eu1.net), adding 284 KiB and 695 ms of main-thread time.

  • hsappstatic.net adds 409 ms

    409 ms

    hsappstatic.net costs a phone 409 ms of main-thread work and 124 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

    400 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 400 ms.

  • Hubspot adds 286 ms

    286 ms

    Hubspot costs a phone 286 ms of main-thread work and 61 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.

  • 2,900 HTML elements

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

  • 20 long tasks on the main thread

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

  • Server response: 1.1 s

    1.1 s

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

  • Reduce unused JavaScript

    94 KiB

    About 94 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    41 KiB

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

  • Improve image delivery

    23 KiB

    1 image could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 92 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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

5 to fix68
  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Time to Interactive: 7.9 s

    7.9 s

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

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

    +70%

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

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

2 checks passed
  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Create Business. Better Everyday.”.

  • Cumulative Layout Shift: 0.03

    0.03

    The layout barely moves while loading (CLS 0.03, good is under 0.1).

Images and page weight

2 to fix83
  • 10 images below the first screen load straight away

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

  • 1 image far larger than shown

    86 KiB

    1 image is downloaded at several times the size a phone draws it, for example How-To-Know-If-Your-Facebook-Ads-Are-Working-And-Worth-Runni at 2,000 px wide, shown at 328 px. Resized copies would save about 86 KiB.

  • 1 image in older formats

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

    0.48 g

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

1 checks passed
  • Page weight: 1.7 MB in 104 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 104 requests on a phone: images 879 KiB (68), scripts 378 KiB (23) and fonts 353 KiB (5). That is a lean page.

Accessibility

2 to fixGoogle 9697
  • 15 text elements with low contrast

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

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

2 checks passed
  • Every image has alt text

    All 66 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

Google 100100
  • 131 internal links, 19 external

    The homepage links to 131 pages on dilate.com.au and 19 external pages.

8 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Perth’s #1 Digital Marketing Agency | An Online Marketing Agency that Creates Business, Better Everyday. No Contracts, …”.

  • One H1 headline

    Your main headline reads: “PERTH'S #1 DIGITAL MARKETING AGENCY”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Full-Service Digital Marketing Agency Perth | Dilate Digital”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, CreativeWorkSeries, FAQPage, LocalBusiness and Organization.

  • 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.dilate.com.au/sitemap_index.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 75 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

3 to fixGoogle 7385
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix95
  • A 24-field form

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

  • About 3,235 words of copy

    The homepage carries about 3,235 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Dilate Digital now” and “Request a call Request a call”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Download the guide Download the guide” and “Sign Up”.

  • Social proof on the page

    Social proof on the homepage: 28 testimonial or review blocks, 9 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Hotjar and HubSpot.

  • Direct contact links

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

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 dilate.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 | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on dilate.com.au, including 16 speed 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