Tools & Wizards About Us
support.cox.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

support.cox.com

Residential Support Overview | Cox Communications

Page Load Speed

2.4 sec in total

First Response

36 ms

Resources Loaded

2.2 sec

Page Rendered

180 ms

support.cox.com screenshot

About Website

Welcome to support.cox.com homepage info - get ready to check Support Cox best content for United States right away, or after learning these important things about support.cox.com

Welcome to Cox Support. Here you'll find tips for using your services, answers to your questions, and step-by-step troubleshooting guides to get the most out of your Cox services.

Visit support.cox.com

Key Findings

We analyzed Support.cox.com page load time and found that the first response time was 36 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

support.cox.com performance score

0

Network Requests Diagram

support.cox.com

36 ms

support.cox

1297 ms

presentation.css.jgz

67 ms

OmnitureLibrary.js.jgz

82 ms

lib.js.jgz

117 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Support.cox.com, 41% (35 requests) were made to Cox.com and 9% (8 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cox.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (74%)

Content Size

2.1 MB

After Optimization

555.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Support.cox.com 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. 45% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 66.2 kB

  • Original 79.3 kB
  • After minification 62.1 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 17.2 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 66.2 kB or 83% of the original size.

Image Optimization

-16%

Potential reduce by 11.9 kB

  • Original 73.5 kB
  • After minification 61.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. Obviously, Support Cox needs image optimization as it can save up to 11.9 kB or 16% 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.2 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 422.0 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.2 MB or 74% of the original size.

CSS Optimization

-84%

Potential reduce by 304.2 kB

  • Original 363.1 kB
  • After minification 360.2 kB
  • After compression 59.0 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. Support.cox.com needs all CSS files to be minified and compressed as it can save up to 304.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (59%)

Requests Now

80

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

support.cox.com

support.cox.com

36 ms

support.cox

support.cox

1297 ms

presentation.css.jgz

presentation.css.jgz

67 ms

OmnitureLibrary.js.jgz

OmnitureLibrary.js.jgz

82 ms

lib.js.jgz

lib.js.jgz

117 ms

mojo.js.jgz

mojo.js.jgz

54 ms

stdlib.js.jgz

stdlib.js.jgz

54 ms

cox.js.jgz

cox.js.jgz

102 ms

all.css.jgz

all.css.jgz

59 ms

residential.css.jgz

residential.css.jgz

100 ms

logoff.css

logoff.css

203 ms

mtagconfig.js

mtagconfig.js

70 ms

presentation.js.jgz

presentation.js.jgz

20 ms

cox-config.js

cox-config.js

51 ms

menu.png

menu.png

163 ms

contact-us-mobile-icon.png

contact-us-mobile-icon.png

161 ms

form-fields.png

form-fields.png

145 ms

Y294LWN1cnJlbnQtc2l0ZT0

Y294LWN1cnJlbnQtc2l0ZT0

151 ms

Y294LWN1cnJlbnQtc2l0ZT0

Y294LWN1cnJlbnQtc2l0ZT0

152 ms

Y294LWN1cnJlbnQtc2l0ZT0

Y294LWN1cnJlbnQtc2l0ZT0

153 ms

shop-mobile-menu-icon.png

shop-mobile-menu-icon.png

111 ms

supportt-mobile-menu-icon.png

supportt-mobile-menu-icon.png

112 ms

my-connectiont-mobile-menu-icon.png

my-connectiont-mobile-menu-icon.png

111 ms

my-account-mobile-menu-icon.png

my-account-mobile-menu-icon.png

111 ms

bg-button-combined.png

bg-button-combined.png

113 ms

info-box-bg.png

info-box-bg.png

112 ms

hdr-tv.png

hdr-tv.png

113 ms

arrow-more.gif

arrow-more.gif

113 ms

hdr-internet.png

hdr-internet.png

113 ms

hdr-phone.png

hdr-phone.png

113 ms

hdr-home-security.png

hdr-home-security.png

115 ms

hdr-billing.png

hdr-billing.png

115 ms

hdr-account.png

hdr-account.png

115 ms

icon-livechat.png

icon-livechat.png

113 ms

icon-contacts.png

icon-contacts.png

112 ms

icon-servicecenter.png

icon-servicecenter.png

115 ms

icon-phonesupport.png

icon-phonesupport.png

117 ms

bg-status-appointments.gif

bg-status-appointments.gif

115 ms

arrow-more.gif

arrow-more.gif

115 ms

help.png

help.png

116 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

165 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

109 ms

utag.js

utag.js

63 ms

messagecount.mapajax

messagecount.mapajax

88 ms

headerprofile

headerprofile

196 ms

rd

rd

40 ms

OpenSans-Bold-webfont.woff

OpenSans-Bold-webfont.woff

92 ms

OpenSans-Bold-webfont.woff

OpenSans-Bold-webfont.woff

66 ms

open-sans.semibold-webfont.woff

open-sans.semibold-webfont.woff

91 ms

open-sans.semibold-webfont.woff

open-sans.semibold-webfont.woff

95 ms

utag.46.js

utag.46.js

48 ms

utag.132.js

utag.132.js

45 ms

utag.242.js

utag.242.js

46 ms

utag.58.js

utag.58.js

46 ms

utag.124.js

utag.124.js

46 ms

utag.163.js

utag.163.js

44 ms

utag.179.js

utag.179.js

46 ms

id

id

68 ms

fbds.js

fbds.js

20 ms

6899.js

6899.js

58 ms

conversion_async.js

conversion_async.js

56 ms

fbevents.js

fbevents.js

10 ms

channel.js

channel.js

54 ms

oo_style.css

oo_style.css

94 ms

s31058908149134

s31058908149134

35 ms

event

event

57 ms

134 ms

150 ms

95 ms

s

s

90 ms

u

u

85 ms

42 ms

pixel

pixel

16 ms

mTag.js

mTag.js

144 ms

dest4.html

dest4.html

16 ms

oo_tab.png

oo_tab.png

19 ms

21 ms

oo_tab_icon.gif

oo_tab_icon.gif

20 ms

pixel

pixel

39 ms

362248.gif

362248.gif

9 ms

ibs:dpid=771&dpuuid=CAESEPv_2L0UNgEI2_hLkEnG9ew&google_cver=1

ibs:dpid=771&dpuuid=CAESEPv_2L0UNgEI2_hLkEnG9ew&google_cver=1

27 ms

ibs:dpid=1121&dpuuid=968344294056215662

ibs:dpid=1121&dpuuid=968344294056215662

8 ms

ibs:dpid=1175&dpuuid=h4-SAYGLwFef3cVQhojaUtTdxwWf2sYCh4gjAm6X

ibs:dpid=1175&dpuuid=h4-SAYGLwFef3cVQhojaUtTdxwWf2sYCh4gjAm6X

6 ms

gif

gif

21 ms

ibs:dpid=992&dpuuid=v6npc5m0gf7g

ibs:dpid=992&dpuuid=v6npc5m0gf7g

6 ms

SEO Factors

support.cox.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.cox.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Support.cox.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

support.cox.com

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