Mobile Readiness & Progressive
Web Apps in Australia

An Audit of the Top 100 Australian Retail Websites

Inspired by our initial study of Mobile Readiness & Progressive Web Apps in the UK – in this study we’re taking a look to see if the top 100 Australian retail sites are adapting to mobile best practises and are progressive web app ready.

We believe that the majority of websites have not changed to take advantage of all the features available (sometimes essential) to ensure a good experience for the majority of visitors, this can be caused by a series of factors, such as: speed, security, discoverability and much more.

Our previous studies: Mobile Readiness & Progressive Web Apps in the UK and Mobile Site Speed Benchmark indicated that slow mobile experiences had a detrimental impact on visitors and visitor performance metrics.

First, let’s recap on what the PWA features are.


What are the Progressive Web App Features

Progressive Web Apps (PWAs) are websites that can be available on any mobile device by adopting app-like features and characteristics. These features contribute to a better user experience by making the site accessible to a greater amount of users. For day-to-day use, features like those related to speed and security are considered best practices for any website and are being continuously emphasised by Google.


Here are the total list:

Progressive – Works for every user, regardless of browser choice because it’s built with progressive enhancement as a core tenet.

Responsive – Fits any form factor: desktop, mobile, tablet, or whatever is next.

Connectivity independent – Enhanced with service workers to work offline or on low-quality networks.

App-like – Feels like an app, because the app shell model separates the application functionality from application content.

Fresh – Always up-to-date thanks to the service worker update process.

Safe – Served via HTTPS to prevent snooping and to ensure content hasn’t been tampered with.

Discoverable – Is identifiable as an “application” thanks to W3C manifest and service worker registration scope, allowing search engines to find it.

Re-engageable – Makes re-engagement easy through features like push notifications.

Installable – Allows users to add apps they find most useful to their home screen without the hassle of an app store.

Linkable – Easily share the application via URL, does not require complex installation.

Source: Your First Progressive Web App, By Pete LePage – Google Developer Advocate


The Audit Criteria, Tools and Methodology

We obtained the top 100 Australian online retailers from Australia based eCommerce consultancy firm Magenable. We then used the Lighthouse Audit Tool to identify which of of the progressive web app criterion were being met. For more details about Lighthouse please click here.

Using Lighthouse we selected 5 of the 11 total (non-manual) PWA checks to compare across the sites in the data set. We chose these 5 criteria because they illustrate a good mix of mobile and PWA-specific experiences:

  1. HTTPS – Is the site served over HTTPS?
  2. Service Worker – Does the site register a service worker?
  3. Speed– Is the site interactive in less than 10 seconds on a 3G connection?
  4. Add to Home Screen – Does the site prompt the user to ‘‘add to home screen’’?
  5. Content Sized for Mobile – Does the serve content that fits right to the device viewport, either by serving responsively or adaptively?

Source: Progressive Web App Checklist

As for methodology, after we ran the Lighthouse tool we manually recorded a checklist Y/N to show if the site passed the audit criteria.



HTTPS – Is the site served over HTTPS?

Using secure protocol provides additional security for personal data, such as credit card information or any other personal details. In addition many newer web technologies such as new browser features, PWA features and HTTP2 are designed for, or in some cases require HTTPS to work.



Service Worker – Does the site register a service worker?

Technically a service worker is a man in the middle that can manage push notifications, background sync and the delivery of some content whilst out of range of a mobile Internet connection. Particularly powerful when a user adds a site to home screen this feature can push content and contribute to a sense of ‘always-on’.



Speed – Is the site interactive in less than 10 seconds on a 3G connection?

Many mobile device users are still getting by with 3G connections which can contribute to a slow and frustrating experience. For that reason, we are looking for a faster experience from leading sites; therefore the measurement standard is a level of interactivity, TTFI (time to first interactive). The pass/fail mark here is a sub ten second TTFI. As we see, only four sites managed a sub-10 second TTFI.


This is way below the benchmark within the UK market, so we decided to dig into the data and find out where the median, lower and upper quartile ranges lay…


Time to First Interactivity (TTFI:  25% Percentile – 16.9s; Median – 21.7s; 75% Percentile – 27.05s)

The fastest retail sites in Australia load in 16.9 seconds on a mobile runtime config. Let that sink in… The fastest retail websites in Australia are still too slow to pass Lighthouse audit criteria.


Add to Home Screen – Does the site prompt the user to ‘‘add to home screen’’?

Along with the service worker script and the features it facilitates, the ability to ‘‘add to home screen’’, which is managed in the App Manifest, is the second main feature of a PWA that is specific to the app like characteristics.



Content Sized for Mobile – Does the site serve content that fits into the device viewport, either by serving responsively or adaptively?

One size does not fit all when it comes to mobile internet use. This criteria, along with HTTPS and time to interactivity are good practise criteria that work for mobile friendly internet use independent of the PWA features.




Whilst most of Australia’s leading retail sites are serving content optimised for mobile visitors and use a secured protocol, many of these are still not making use of Progressive Web App features.

There’s disparity of experience offered to mobile web users by these leading websites making us ask if many are ready for the upcoming Mobile First Index change by Google.

Our tips for success in both search and user experience terms are as follows:

  • Be fast, interactive and responsive
  • Embrace Progressive Web App features
  • Use HTTPS and redirect from HTTP. Don’t rely on canonical references at the expense of mobile users