8 sec in total
832 ms
6.8 sec
397 ms
Click here to check amazing What Phone content for Australia. Otherwise, check out these important facts you probably never knew about whatphone.com.au
Find & compare the top SIM Only plans for your Australian mobile. Easy comparison and reviews to help you choose. Save up to 32%. Compare SIM Only Plans - BYO Mobile
Visit whatphone.com.auWe analyzed Whatphone.com.au page load time and found that the first response time was 832 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
whatphone.com.au performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value21.0 s
0/100
25%
Value31.8 s
0/100
10%
Value24,930 ms
0/100
30%
Value0
100/100
15%
Value34.4 s
0/100
10%
832 ms
1532 ms
31 ms
1176 ms
1350 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 12% of them (8 requests) were addressed to the original Whatphone.com.au, 46% (31 requests) were made to D2qk1acs7qlvt5.cloudfront.net and 10% (7 requests) were made to Static.olark.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source D2qk1acs7qlvt5.cloudfront.net.
Page size can be reduced by 340.4 kB (49%)
701.7 kB
361.3 kB
In fact, the total size of Whatphone.com.au main page is 701.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 281.5 kB which makes up the majority of the site volume.
Potential reduce by 110.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 110.1 kB or 76% of the original size.
Potential reduce by 20.5 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. What Phone images are well optimized though.
Potential reduce by 181.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 181.9 kB or 65% of the original size.
Potential reduce by 27.9 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 27.9 kB or 81% of the original size.
Number of requests can be reduced by 27 (45%)
60
33
The browser has sent 60 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 23 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
whatphone.com.au
832 ms
minify.php
1532 ms
css
31 ms
minify.php
1176 ms
minify.php
1350 ms
minify.php
1176 ms
minify.php
1171 ms
46f1eee3fbe4fca9813beddaa292bc8c.js
374 ms
minify.php
1000 ms
bootstrap.min.js
7 ms
minify.php
2453 ms
script.js
24 ms
26dcb4
35 ms
cse.js
46 ms
geolocAndWeather.php
209 ms
cse.js
160 ms
logo43.png
38 ms
BOOSTLOGO_BALCKTEXT_75x75.png
77 ms
Telechoice_Logo.png
520 ms
network_icon.png
528 ms
amaysim_icon.png
523 ms
find_phone.png
508 ms
sim_icon.png
509 ms
Optus-Logo.png
523 ms
amaysim_s.png
514 ms
vodafone_s.png
1007 ms
Lebara-Logo.png
516 ms
Vodafone-Network-or-MVNO.png
1663 ms
infographic3-1.png
1902 ms
Optus-Network-or-MVNO.png
1671 ms
Boost-Offer.gif
2216 ms
Boost-Special.gif
3928 ms
1x1.trans.gif
1105 ms
gtm.js
94 ms
app-icons-s80af0713c3.png
1076 ms
home_bg_patern.jpg
1462 ms
home_banner_left_bg.png
1949 ms
home_banner_right_bg.png
2178 ms
small_rating.png
2112 ms
sprites-s851b14ab2d.png
2762 ms
box_light.png
2451 ms
26DCB4_1_0.woff
4390 ms
26DCB4_0_0.woff
3261 ms
26DCB4_2_0.woff
4183 ms
jsapi
80 ms
icon_info_rosette.png
2808 ms
amaysim_s.png
3174 ms
Cmobile-Logo1.png
3293 ms
analytics.js
23 ms
collect
17 ms
collect
105 ms
default+en.css
8 ms
default.css
20 ms
default+en.I.js
23 ms
default.css
45 ms
ga-audiences
27 ms
loader0.js
85 ms
widgets.js
48 ms
9214-540-10-8594.js
30 ms
c
231 ms
application2.js
109 ms
storage.html
118 ms
storage.js
31 ms
visits
288 ms
jquery.js
52 ms
3971c742ac2346c431f086113e61d518.css
49 ms
nr-632.min.js
47 ms
whatphone.com.au accessibility score
ARIA
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.
Impact
Issue
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Names and labels
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.
Impact
Issue
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
whatphone.com.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
whatphone.com.au SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
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/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: