Access whatphone.com.au. Compare Mobile Phone Plans in Australia

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

whatphone.com.au

1148 ms

optimize.js

74 ms

style.min.css

353 ms

classic-themes.min.css

30 ms

pagenavi-css.css

30 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 62% of them (66 requests) were addressed to the original Whatphone.com.au, 10% (11 requests) were made to Cdnjs.cloudflare.com and 10% (11 requests) were made to Ad.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Whatphone.com.au.

Content Size

2.1 MB

After Optimization

1.0 MB

In fact, the total size of Whatphone.com.au main page is 2.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 1.0 MB

Original 1.1 MB
After minification 859.6 kB
After compression 115.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 270.1 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.0 MB or 90% of the original size.

Image Optimization

-12%

Potential reduce by 51.6 kB

Original 438.5 kB
After minification 386.9 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, What Phone needs image optimization as it can save up to 51.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 9.8 kB

Original 402.3 kB
After minification 402.3 kB
After compression 392.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-24%

Potential reduce by 37.4 kB

Original 152.9 kB
After minification 140.3 kB
After compression 115.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Whatphone.com.au needs all CSS files to be minified and compressed as it can save up to 37.4 kB or 24% of the original size.

Requests Now

105

After Optimization

The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Phone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatphone.com.au can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Whatphone.com.au main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

whatphone.com.au

Open Graph data is detected on the main page of What Phone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Compare Mobile Phone Plans in Australia | WhatPhone

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

whatphone.com.au

optimize.js

style.min.css

classic-themes.min.css

pagenavi-css.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

whatphone.com.au

optimize.js

style.min.css

classic-themes.min.css

pagenavi-css.css

jquery.bxslider.min.css

nouislider.min.css

select2.css

flickity.min.css

featherlight.min.css

style.css

swiper-bundle.min.css

jquery-ui-1.10.3.custom.min.css

main.css

responsive.dataTables.min.css

tablepress-combined.min.css

tablepress-responsive-flip.min.css

jquery.min.js

script.js

best-selling-script.js

visits.js

jquery.cookie.js

analytics-talk-content-tracking.js

modernizr-custom.min.js

handlebars.js

bodyScrollLock.min.js

jquery.countdown.min.js

in-view.min.js

js

js

wp-emoji-release.min.js

gtm4wp-form-move-tracker.js

lazysizes.min.js

unveil.js

jquery.bxslider.min.js

script.js

bootstrap.min.js

jquery-ui-1.10.3.custom.min.js

popper.min.js

index.all.min.js

wNumb.min.js

nouislider.min.js

flickity.pkgd.min.js