Website review, no card needed
dabble.com.au website review
Visit site (opens in a new tab)Reviewed 20 October 202640 issues · 86 checks
This review found 40 issues worth fixing on dabble.com.au, 21 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.1 s |
| May 9, 2026 | 3.2 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 146 ms |
| May 9, 2026 | 143 ms |
| May 16, 2026 | 143 ms |
| May 23, 2026 | 141 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 156 ms |
| Jun 20, 2026 | 166 ms |
| Jun 27, 2026 | 165 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 151 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 143 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 160 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 158 ms |
| Sep 19, 2026 | 153 ms |
| Sep 26, 2026 | 169 ms |
| Oct 3, 2026 | 169 ms |
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 178 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.5 s
3.1 s
3.8 s
4.4 s
5.0 s
Speed
Use efficient cache lifetimes
1.8 s · 53.4 MB35 files are served with short cache lifetimes, so returning visitors download them again (53.4 MB).
Reduce unused JavaScript
6.9 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.
Improve image delivery
1.6 s · 1.9 MB13 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
3.3 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Reduce unused CSS
1.5 s · 283 KiBAbout 283 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Minify JavaScript
1.1 s · 215 KiB215 KiB could be saved by minifying JavaScript.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and Facebook and others), adding 1.9 MB and 1.1 s of main-thread time.
YouTube adds 403 ms
403 msYouTube costs a phone 403 ms of main-thread work and 975 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 407 ms
407 msGoogle Tag Manager costs a phone 407 ms of main-thread work and 522 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.
Legacy JavaScript
300 ms · 55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
150 ms · 20 KiB20 KiB could be saved by minifying CSS.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
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: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
First Contentful Paint: 13.0 s
13.0 sThe first text or image appears after 13.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 29.6 s
29.6 sYour largest element takes 29.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 30.0 s
30.0 sThe page becomes fully interactive after 30.0 s. Good is under 3.8 s.
Speed Index: 13.1 s
13.1 sVisually, the page fills in at 13.1 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 146 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 408 ms
408 msScripts block taps and scrolling for 408 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 184 ms
184 msReal visitors wait 184 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 59.1 MB in 131 requests
59.1 MBYour homepage downloads 59.1 MB in 131 requests on a phone: media 52.8 MB (12), images 2.9 MB (27) and scripts 2.7 MB (45). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
iPhone-Mockup-esports-uai-516x917.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 16.7 g of CO₂ per visit
16.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 16.74 g of CO₂e: 2009.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Interactive controls must not be nested (12 elements)
Interactive controls must not be nested: 12 elements on the page fail this check, rated serious by axe-core.
ARIA commands must have an accessible name (7 elements)
ARIA commands must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.
Orphan list items
Some list items are not inside a list.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
28 links without text
28 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
8 internal links, 38 external
The homepage links to 8 pages on dabble.com.au and 38 external pages.
6 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Australian Sports Betting App. Create Your Dabble Account In Minutes. Competitive Markets Across Sports And Racing. Dow…”.
Title: 55 characters
Your title is a healthy 55 characters: “Dabble – You Better Believe It | Your Go-To Betting App”.
Canonical URL set
The canonical URL is https://www.dabble.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://dabbledev.wpenginepowered.com/sitemap_index.xml.
AI search readiness
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: 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 (913 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.dabble.com.au/llms.txt (6 KiB, 44 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://www.dabble.com.au/pick-em, https://www.dabble.com.au/about and https://www.dabble.com.au/affiliate-program have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.dabble.com.au/pick-em, https://www.dabble.com.au/blog, https://www.dabble.com.au/about and https://www.dabble.com.au/affiliate-program have no <h1> headline, so visitors and search engines get no clear main topic.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 4 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 4 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343001039&tm=gtm002&Ver=2&mid=e6c0f3b3-bdf4-44fa-b4db-e1ff58e8be9a&bo=1&sid=19ba1cc0cc6e11f1a8ce79674699a328&vid=19ba5040cc6e11f1bc99b10dededd559&vids=1&msclkid=N>m_.
6 third-party cookies
6 third-party cookies are 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”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
14 of 15 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 681 words of copy
The homepage carries about 681 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Sign Up”.
9 calls to action
The homepage has 9 calls to action, for example “Contact”, “Sign Up” and “Download Now”.
1 short form
A short form (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo, 2 trust badges and “13K reviews”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 mores (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
18Opening 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.
34 other companies contacted
Loading the homepage contacts 34 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 dabble.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on dabble.com.au, including 23 speed issues and 2 SEO issues. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.