openpay.com.au website review

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

17 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.

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

Google Tag Manager costs a phone 1.4 s of main-thread work and 705 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Amplitude Mobile Analytics and others), adding 2.8 MB and 3.2 s of main-thread time.

About 129 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

Amplitude Mobile Analytics costs a phone 441 ms of main-thread work and 698 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.

Optimizely costs a phone 311 ms of main-thread work and 273 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.

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

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

Polyfills for old browsers add 114 KiB JavaScript that modern phones do not need.

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.

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.

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

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

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

Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Make payments. Earn points. Simple.”.

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

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

Your homepage downloads 5.0 MB in 232 requests on a phone: scripts 3.2 MB (66), images 936 KiB (65) and other files 411 KiB (73). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example image.png at 1,536 px wide, shown at 350 px. Resized copies would save about 309 KiB.

1 image (335 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.

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

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

2 elements hidden from screen readers can still receive keyboard focus.

All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h2 → h4, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 99 pages on openpay.com.au and 27 external pages.

https://pay.com.au/100000-bonus-payrewards-points and https://pay.com.au/offers/earn-300k-bonus-payrewards-points are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://pay.com.au/100000-bonus-payrewards-points and https://pay.com.au/offers/earn-300k-bonus-payrewards-points all use the title “Earn 300K Bonus PayRewards Points - pay.com.au”. Search engines can't tell which page to show for a search, so each competes with the others.

https://pay.com.au/100000-bonus-payrewards-points, https://pay.com.au/offers/earn-300k-bonus-payrewards-points and https://pay.com.au/mobile-app have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97039408&tm=gtm002&Ver=2&mid=d0a5284d-5091-4e82-bceb-168e8ce1f49b&bo=1&sid=4a131290cea811f1bb27f72f721be139&vid=4a1320b0cea811f1a1630d5d7b033bea&vids=1&msclkid=N&gtm_t.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The homepage carries about 2,822 words of visible text.

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 5 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.

Opening the homepage sets 38 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 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.