5.5 sec in total
1.5 sec
3.6 sec
344 ms
Welcome to community.optus.com.au homepage info - get ready to check Community Optus best content for Australia right away, or after learning these important things about community.optus.com.au
Find the help you need with Optus. Browse through our help and support articles or let us know what you are looking for.
Visit community.optus.com.auWe analyzed Community.optus.com.au page load time and found that the first response time was 1.5 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
community.optus.com.au performance score
1469 ms
227 ms
36 ms
38 ms
160 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Community.optus.com.au, 41% (26 requests) were made to Optus.i.lithium.com and 27% (17 requests) were made to Smb.optus.com.au. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Community.optus.com.au.
Page size can be reduced by 2.5 MB (81%)
3.1 MB
589.0 kB
In fact, the total size of Community.optus.com.au main page is 3.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. 60% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 197.0 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 49.9 kB, which is 22% 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 197.0 kB or 86% of the original size.
Potential reduce by 2.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. Obviously, Community Optus needs image optimization as it can save up to 2.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.3 MB
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 1.3 MB or 76% of the original size.
Potential reduce by 938.4 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. Community.optus.com.au needs all CSS files to be minified and compressed as it can save up to 938.4 kB or 89% of the original size.
Number of requests can be reduced by 39 (67%)
58
19
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Optus. 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 9 to 1 for CSS and as a result speed up the page load time.
community.optus.com.au
1469 ms
optus_jan_2015-439108329.css
227 ms
frameworkStyles.css
36 ms
optus-style.css
38 ms
fonts.css
160 ms
font-awesome.min.css
176 ms
community.css
202 ms
leaderboard.css
176 ms
modernizr.js
76 ms
modernizr.custom.cssfilters.js
181 ms
lia-scripts-head-min.js
184 ms
optus-style-blessed2.css
49 ms
optus-style-blessed1.css
67 ms
lia-scripts-common-min.js
431 ms
lia-scripts-body-min.js
127 ms
logo_optus.png
128 ms
original
611 ms
header_hero.png
68 ms
yes_CommunityManager.png
69 ms
icon-view-2x.png
65 ms
icon-reply-2x.png
66 ms
user-favicon.png
67 ms
yes_Moderator.png
66 ms
button_fbconnect_secondary.png
67 ms
original
270 ms
icon-network-status.png
68 ms
message
270 ms
message
270 ms
message
271 ms
100x100
271 ms
TradeGothicLTPro.woff
116 ms
TradeGothicLTPro.woff
116 ms
TradeGothicLTPro-Bold.woff
159 ms
TradeGothicLTPro-Bold.woff
115 ms
TradeGothicLTPro-BdCn20.woff
250 ms
TradeGothicLTPro-BdCn20.woff
114 ms
optus-icons.ttf
528 ms
optus-icons.ttf
204 ms
gtm.js
249 ms
tag.js
247 ms
mainFull.js
194 ms
sdk.js
843 ms
custom.optus.leaderboard-metrics-endpoint
627 ms
tag
326 ms
callback=parseLotameAudiences
131 ms
analytics.js
143 ms
cc_af.js
250 ms
browserFix.js
57 ms
lodash.underscore.js
56 ms
globalHeaderNavMain.js
71 ms
486ae25a922309dc6cdbfe2037f7e4b27e3e2038.js
39 ms
mainPostload.js
35 ms
collect
55 ms
globalHeaderNavDesktop.js
53 ms
globalHeaderNavMobile.js
17 ms
827463604.js
345 ms
f1b96f04b509ba67a2ad55be3150d489d96da116.js
644 ms
177 ms
xd_arbiter.php
316 ms
geo2.js
146 ms
event
47 ms
event
50 ms
event
6 ms
community.optus.com.au SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.optus.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 Community.optus.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.
community.optus.com.au
Open Graph description is not detected on the main page of Community Optus. 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: