Tools & Wizards About Us
optus.intelliresponse.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

optus.intelliresponse.com

Contact us - Optus

Page Load Speed

3.4 sec in total

First Response

186 ms

Resources Loaded

2.8 sec

Page Rendered

403 ms

optus.intelliresponse.com screenshot

About Website

Visit optus.intelliresponse.com now to see the best up-to-date Optus Intelliresponse content for Canada and also check out these interesting facts you probably never knew about optus.intelliresponse.com

If you have a question or need help with your Optus service, you can contact us via messaging or through one of our other available options

Visit optus.intelliresponse.com

Key Findings

We analyzed Optus.intelliresponse.com page load time and found that the first response time was 186 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

optus.intelliresponse.com performance score

0

Network Requests Diagram

optus.intelliresponse.com

186 ms

app.css

67 ms

jquery-ui.css

3 ms

247tag.js

68 ms

modernizr.js

469 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 20% of them (9 requests) were addressed to the original Optus.intelliresponse.com, 47% (21 requests) were made to Smb.optus.com.au and 7% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Smb.optus.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.1 MB (79%)

Content Size

4.0 MB

After Optimization

841.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Optus.intelliresponse.com main page is 4.0 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. Javascripts take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 58.3 kB

  • Original 75.6 kB
  • After minification 66.3 kB
  • After compression 17.2 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 9.3 kB, which is 12% 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 58.3 kB or 77% of the original size.

Image Optimization

-13%

Potential reduce by 14.3 kB

  • Original 106.3 kB
  • After minification 92.0 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, Optus Intelliresponse needs image optimization as it can save up to 14.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 1.7 MB

  • Original 2.3 MB
  • After minification 2.2 MB
  • After compression 599.8 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 1.7 MB or 74% of the original size.

CSS Optimization

-91%

Potential reduce by 1.3 MB

  • Original 1.5 MB
  • After minification 1.0 MB
  • After compression 132.1 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. Optus.intelliresponse.com needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (56%)

Requests Now

41

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

optus.intelliresponse.com

optus.intelliresponse.com

186 ms

app.css

app.css

67 ms

jquery-ui.css

jquery-ui.css

3 ms

247tag.js

247tag.js

68 ms

modernizr.js

modernizr.js

469 ms

mainFull.js

mainFull.js

489 ms

frameworkStyles.css

frameworkStyles.css

1344 ms

optus-style.css

optus-style.css

416 ms

jquery-ui.min.js

jquery-ui.min.js

5 ms

s_code.js

s_code.js

69 ms

247px.js

247px.js

34 ms

247px.js

247px.js

4 ms

spacer.gif

spacer.gif

429 ms

pxt.js

pxt.js

266 ms

personalize.js

personalize.js

3 ms

optus-style-blessed2.css

optus-style-blessed2.css

471 ms

optus-style-blessed1.css

optus-style-blessed1.css

372 ms

browserFix.js

browserFix.js

126 ms

lodash.underscore.js

lodash.underscore.js

803 ms

pwrdbyir[transparent].gif

pwrdbyir[transparent].gif

49 ms

olympic-footer-logo.png

olympic-footer-logo.png

16 ms

gtm.js

gtm.js

47 ms

Optus-logo-desktop.png

Optus-logo-desktop.png

92 ms

title_lets-talk.png

title_lets-talk.png

59 ms

yes.png

yes.png

124 ms

TradeGothicLTPro.woff

TradeGothicLTPro.woff

59 ms

TradeGothicLTPro-Bold.woff

TradeGothicLTPro-Bold.woff

59 ms

markpro-heavy.woff

markpro-heavy.woff

153 ms

TradeGothicLTPro-BdCn20.woff

TradeGothicLTPro-BdCn20.woff

122 ms

markpro-medium.woff

markpro-medium.woff

121 ms

markpro.woff

markpro.woff

122 ms

markpro.woff

markpro.woff

214 ms

markpro-bold.woff

markpro-bold.woff

194 ms

markpro-medium.woff

markpro-medium.woff

214 ms

optus-icons.ttf

optus-icons.ttf

95 ms

tag.js

tag.js

64 ms

ui-bg_inset-hard_100_fcfdfd_1x100.png

ui-bg_inset-hard_100_fcfdfd_1x100.png

5 ms

activityi;src=3306388;type=conta633;cat=gtmco520;ord=9714473184408;~oref=http%3A%2F%2Foptus.intelliresponse.com%2F

activityi;src=3306388;type=conta633;cat=gtmco520;ord=9714473184408;~oref=http%3A%2F%2Foptus.intelliresponse.com%2F

31 ms

mainPostload.js

mainPostload.js

279 ms

tag

tag

15 ms

16b374f7d042f2cfa6d29e37ee844433bdf33487.js

16b374f7d042f2cfa6d29e37ee844433bdf33487.js

3 ms

phonenum.jsp

phonenum.jsp

1075 ms

02e57a1ed55fd0605cfdf52bb203ee30d706cc8e.js

02e57a1ed55fd0605cfdf52bb203ee30d706cc8e.js

21 ms

optus.intelliresponse.com

optus.intelliresponse.com

77 ms

scrollToTopController.js

scrollToTopController.js

66 ms

SEO Factors

optus.intelliresponse.com SEO score

0

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 Optus.intelliresponse.com 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 Optus.intelliresponse.com 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

optus.intelliresponse.com

Open Graph description is not detected on the main page of Optus Intelliresponse. 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: