Tools & Wizards About Us
contentious.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

contentious.com

contentious.com | Amy Gahran's news and musings on how we communicate in the online age.

Page Load Speed

7 sec in total

First Response

1 sec

Resources Loaded

3.4 sec

Page Rendered

2.6 sec

contentious.com screenshot

About Website

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

Visit contentious.com

Key Findings

We analyzed Contentious.com page load time and found that the first response time was 1 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

contentious.com performance score

0

Network Requests Diagram

www.contentious.com

1002 ms

wp-emoji-release.min.js

111 ms

style.css

106 ms

css

28 ms

jquery.js

176 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 33% of them (12 requests) were addressed to the original Contentious.com, 33% (12 requests) were made to Public.slidesharecdn.com and 11% (4 requests) were made to Slideshare.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Contentious.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.1 kB (51%)

Content Size

499.1 kB

After Optimization

245.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Contentious.com main page is 499.1 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 158.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 59.4 kB

  • Original 76.6 kB
  • After minification 73.9 kB
  • After compression 17.3 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 59.4 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 1.7 kB

  • Original 132.7 kB
  • After minification 131.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. Contentious images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 94.7 kB

  • Original 158.9 kB
  • After minification 158.5 kB
  • After compression 64.3 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 94.7 kB or 60% of the original size.

CSS Optimization

-75%

Potential reduce by 98.4 kB

  • Original 130.8 kB
  • After minification 124.6 kB
  • After compression 32.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. Contentious.com needs all CSS files to be minified and compressed as it can save up to 98.4 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (48%)

Requests Now

31

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.contentious.com

www.contentious.com

1002 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

111 ms

style.css

style.css

106 ms

css

css

28 ms

jquery.js

jquery.js

176 ms

jquery-migrate.min.js

jquery-migrate.min.js

74 ms

small-menu.js

small-menu.js

39 ms

wp-embed.min.js

wp-embed.min.js

39 ms

13752044

13752044

422 ms

line-pattern.png

line-pattern.png

174 ms

Oakland-zombie-map-300x214.jpg

Oakland-zombie-map-300x214.jpg

177 ms

Boulder-zombie-map-300x198.jpg

Boulder-zombie-map-300x198.jpg

177 ms

not-tall-enough.jpg

not-tall-enough.jpg

174 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

57 ms

Y_TKV6o8WovbUd3m_X9aAA.ttf

Y_TKV6o8WovbUd3m_X9aAA.ttf

49 ms

websymbols-regular-webfont.woff

websymbols-regular-webfont.woff

45 ms

combined_jquery.js

combined_jquery.js

891 ms

global.js

global.js

886 ms

combined_li_tracking.js

combined_li_tracking.js

885 ms

font-awesome.css

font-awesome.css

885 ms

combined_presentation.css

combined_presentation.css

917 ms

combined_player_presentation.js

combined_player_presentation.js

926 ms

combined_old_embed.js

combined_old_embed.js

958 ms

combined_base.js

combined_base.js

218 ms

ga.js

ga.js

212 ms

beacon.js

beacon.js

209 ms

5-affordable-ways-nonprofits-can-use-mobile-1-728.jpg

5-affordable-ways-nonprofits-can-use-mobile-1-728.jpg

163 ms

1x1.gif

1x1.gif

150 ms

logo_embed_20x20_v1.png

logo_embed_20x20_v1.png

151 ms

13752044

13752044

139 ms

lead-form

lead-form

291 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

89 ms

icons.svg

icons.svg

84 ms

status

status

87 ms

__utm.gif

__utm.gif

32 ms

__utm.gif

__utm.gif

91 ms

SEO Factors

contentious.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 Contentious.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 Contentious.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

contentious.com

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