adaptil.com.au website review

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

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

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

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

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

Amazon Web Services costs a phone 102 ms of main-thread work and 3.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.

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

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

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

About 152 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.

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

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

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

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

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

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 element shown below.

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

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

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

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

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

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

Your homepage downloads 8.6 MB in 332 requests on a phone: images 4.8 MB (157), scripts 2.8 MB (47) and other files 805 KiB (114). Under 2 MB keeps phones on slow connections fast.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your meta description is 315 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 152 pages on adaptil.com.au and 6 external pages.

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

/collections/our-products, /pages/dog-scared-of-thunder and /pages/dog-behaviour-problems have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://rtd-tm.everesttech.net/upi/?sid=9mfmXCKvbVYBY6dGSNrF&cs=1.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

Social proof on the homepage: 9 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,053 words of visible text.

adaptil.com.au has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

adaptil.com.au has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Taboola and 1 more (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 16 cookies, 1 of them by other companies (measured from a US location before any click).

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