pointsbet.com.au website review

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

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

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

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

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

Polyfills for old browsers add 82 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 650 ms faster on a phone.

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

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

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

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

pointsbet.com costs a phone 38 ms of main-thread work and 451 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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

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.

3 KiB could be saved by minifying CSS.

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 visitors wait 5.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 31.9 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

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

Your homepage downloads 5.7 MB in 503 requests on a phone: scripts 4.2 MB (315), images 828 KiB (51) and other files 464 KiB (124). Under 2 MB keeps phones on slow connections fast.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

SVG elements with an img role do not have an accessible text alternative (76 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 9 characters: “PointsBet”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

7 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://pointsbet.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.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

Large scripts ship without source maps.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Tag Manager (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.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

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