Website review, no card needed

adtsecurity.com.au logo

adtsecurity.com.au website review

Visit site (opens in a new tab)Reviewed 18 October 202626 issues · 78 checks

This review found 26 issues worth fixing on adtsecurity.com.au, 6 of them high impact, across 78 checks. The most urgent: page weight: 5.1 MB in 111 requests. 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
2.4 s1.7 sApr 25Oct 102.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.8 s
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20262.2 s
Oct 10, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
213 ms118 msApr 25Oct 10202 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026129 ms
May 2, 2026135 ms
May 9, 2026137 ms
May 16, 2026140 ms
May 23, 2026146 ms
May 30, 2026151 ms
Jun 6, 2026148 ms
Jun 13, 2026150 ms
Jun 20, 2026147 ms
Jun 27, 2026148 ms
Jul 4, 2026148 ms
Jul 11, 2026147 ms
Jul 18, 2026146 ms
Jul 25, 2026152 ms
Aug 1, 2026152 ms
Aug 8, 2026154 ms
Aug 15, 2026169 ms
Aug 22, 2026171 ms
Aug 29, 2026187 ms
Sep 5, 2026193 ms
Sep 12, 2026193 ms
Sep 19, 2026201 ms
Sep 26, 2026191 ms
Oct 3, 2026202 ms
Oct 10, 2026202 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 adtsecurity.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adtsecurity.com.au at 0.5 s0.5 s
  2. adtsecurity.com.au at 1.0 s1.0 s
  3. adtsecurity.com.au at 1.4 s1.4 s
  4. adtsecurity.com.au at 1.9 s1.9 s
  5. adtsecurity.com.au at 2.4 s2.4 s
  6. adtsecurity.com.au at 2.9 s2.9 s
  7. adtsecurity.com.au at 3.4 s3.4 s
  8. adtsecurity.com.au at 3.8 s3.8 s

Speed

9 to fix65
  • Main-thread work: 5.0 s

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

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    150 ms · 1,019 KiB

    About 1,019 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 65

    65/100

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

  • Google Tag Manager adds 703 ms

    703 ms

    Google Tag Manager costs a phone 703 ms of main-thread work and 1.3 MB 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 CDN adds 613 ms

    613 ms

    Google CDN costs a phone 613 ms of main-thread work and 1.4 MB 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.

  • Facebook adds 288 ms

    288 ms

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

  • 20 long tasks on the main thread

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

  • ContentSquare adds 119 ms

    119 ms

    ContentSquare costs a phone 119 ms of main-thread work and 317 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.

  • Use efficient cache lifetimes

    234 KiB

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

  • Improve image delivery

    78 KiB

    3 images could be 78 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    60 KiB

    About 60 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

1 checks passed
  • Server response: 91 ms

    91 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 27.7 s

    27.7 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

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

    +53%

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

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

    +28%

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ADT Security monitoring room”.

  • Speed Index: 3.6 s

    3.6 s

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 603 ms

    603 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.017

    0.017

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

Images and page weight

1 to fix70
  • Page weight: 5.1 MB in 111 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 111 requests on a phone: scripts 2.4 MB (33), other files 2.2 MB (49) and images 267 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.46 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

2 to fixGoogle 9797
  • Links must have discernible text (3 elements)

    Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

  • 21 form fields without a label

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

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

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

2 checks passed
  • Every image has alt text

    All 66 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No canonical URL

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

  • 5 links with vague text

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

  • 93 internal links, 4 external

    The homepage links to 93 pages on adtsecurity.com.au and 4 external pages.

7 checks passed
  • Meta description: 117 characters

    Your meta description is 117 characters: “Monitored integrated security and professional installation for industry, business and homes - ADT Security Australia”.

  • One H1 headline

    Your main headline reads: “More than monitoring. Security that acts.”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “ADT Security Australia - Monitored and Installed”.

  • Structured data in place

    Structured data found: Organization and WebPage.

  • 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.adtsecurity.com.au/sitemap-0.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.adtsecurity.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 (915 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 4 pages without an H1

    https://www.adtsecurity.com.au/commercial-security/retail-security-solutions, https://www.adtsecurity.com.au/commercial-security/healthcare-security, https://www.adtsecurity.com.au/business-safety-training-by-threat-protect and https://www.adtsecurity.com.au/video-monitoring have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=247009661&tm=gtm002&Ver=2&mid=dfba6b88-a523-490c-aa15-4a4194351a1a&bo=1&sid=6f8b9eb0caaa11f18a13a7d17ac2b9a4&vid=6f8bb090caaa11f1919a87e551ae67f6&vids=1&msclkid=N&gtm_.

  • 4 small tap targets

    4 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • A 25-field form

    Your longest form asks for 25 fields (0 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 821 words of copy

    The homepage carries about 821 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 today”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact”, “Get a quote” and “Contact us today”.

  • Social proof on the page

    Social proof on the homepage: 9 customer or partner logos and 11 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, Meta Pixel and Microsoft Ads and 1 more (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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 adtsecurity.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 26 issues on adtsecurity.com.au, including 15 speed issues, 2 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