7.7 sec in total
716 ms
6.8 sec
148 ms
Visit 160.com.au now to see the best up-to-date 160 content for Australia and also check out these interesting facts you probably never knew about 160.com.au
Get your message across with our SMS gateway and bulk SMS service. Whether you need to send reminders or run a marketing campaign, you're covered!
Visit 160.com.auWe analyzed 160.com.au page load time and found that the first response time was 716 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
160.com.au performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value12.6 s
0/100
25%
Value11.3 s
6/100
10%
Value3,160 ms
3/100
30%
Value0.019
100/100
15%
Value16.9 s
5/100
10%
716 ms
558 ms
421 ms
664 ms
49 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 86% of them (83 requests) were addressed to the original 160.com.au, 7% (7 requests) were made to Apis.google.com and 2% (2 requests) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain 160.com.au.
Page size can be reduced by 57.4 kB (37%)
155.8 kB
98.4 kB
In fact, the total size of 160.com.au main page is 155.8 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. 30% of websites need less resources to load. Images take 64.7 kB which makes up the majority of the site volume.
Potential reduce by 35.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. 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 35.5 kB or 79% of the original size.
Potential reduce by 1.2 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. 160 images are well optimized though.
Potential reduce by 12.2 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 12.2 kB or 34% of the original size.
Potential reduce by 8.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. 160.com.au needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 80% of the original size.
Number of requests can be reduced by 61 (65%)
94
33
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 160. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
160.com.au
716 ms
www.160.com.au
558 ms
skin1.css
421 ms
tools.js
664 ms
plusone.js
49 ms
social.css
437 ms
gplus-32.png
71 ms
aplus.gif
236 ms
aminus.gif
212 ms
flash_wap_btn.gif
238 ms
twitter.png
237 ms
facebook.png
421 ms
sm_home.gif
457 ms
menuvr.gif
453 ms
sm_pricing.gif
459 ms
sm_feature.gif
451 ms
sm_about.gif
464 ms
lg-share-en.gif
629 ms
fav.gif
669 ms
ask.gif
674 ms
backflip.gif
678 ms
ballhype.gif
678 ms
bebo.gif
694 ms
blinklist.gif
864 ms
blogmarks.gif
888 ms
delicious.gif
897 ms
digg.gif
902 ms
diigo.gif
904 ms
facebook.gif
926 ms
fark.gif
1073 ms
faves.gif
1105 ms
friendfeed.gif
1126 ms
google.gif
1127 ms
kaboodle.gif
1128 ms
linkagogo.gif
1156 ms
linkedin.gif
1290 ms
live.gif
1324 ms
misterwong.gif
1349 ms
mixx.gif
1352 ms
multiply.gif
1353 ms
myaol.gif
1419 ms
myspace.gif
1499 ms
cb=gapi.loaded_0
67 ms
netvouz.gif
1519 ms
ga.js
58 ms
cb=gapi.loaded_1
13 ms
fastbutton
73 ms
__utm.gif
12 ms
postmessageRelay
38 ms
api.js
50 ms
core:rpc:shindig.random:shindig.sha1.js
65 ms
2536007149-postmessagerelay.js
27 ms
newsvine.gif
1367 ms
cb=gapi.loaded_0
21 ms
cb=gapi.loaded_1
29 ms
propeller.gif
1348 ms
reddit.gif
1349 ms
segnalo.gif
1421 ms
simpy.gif
1293 ms
slashdot.gif
1315 ms
spurl.gif
1349 ms
squidoo.gif
1352 ms
stumbleupon.gif
1351 ms
tailrank.gif
1429 ms
technorati.gif
1295 ms
twitter.gif
1319 ms
yahoo.gif
1353 ms
yardbarker.gif
1358 ms
but1.gif
1358 ms
but2.gif
1435 ms
demo2.png
1684 ms
ad_0.jpg
1345 ms
ftr19.jpg
1353 ms
ftr18.gif
1357 ms
ftr1.gif
1357 ms
ftr2.gif
1435 ms
ftr3.gif
1380 ms
ftr4.gif
1368 ms
ftr12.gif
1362 ms
ftr5.gif
1372 ms
ftr11.gif
1464 ms
ftr6.gif
1514 ms
ftr15.gif
1407 ms
ftr8.gif
1389 ms
ftr9.gif
1374 ms
ftr10.gif
1403 ms
ftr14.gif
1469 ms
ftr13.gif
1469 ms
ftr7.gif
1428 ms
ftr16.gif
1395 ms
trust.png
1454 ms
menubg.gif
1386 ms
greyback.gif
1488 ms
butbg.gif
1452 ms
demo.jpg
1664 ms
blueproduct.gif
1402 ms
160.com.au accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
160.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
160.com.au SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 160.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 160.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.
160.com.au
Open Graph description is not detected on the main page of 160. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: