Tools & Wizards About Us
richardroeper.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

richardroeper.com

Page Load Speed

1.5 sec in total

First Response

102 ms

Resources Loaded

1.1 sec

Page Rendered

242 ms

richardroeper.com screenshot

About Website

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

Visit richardroeper.com

Key Findings

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

Performance Metrics

richardroeper.com performance score

0

Network Requests Diagram

richardroeper.com

102 ms

www.richardroeper.com

238 ms

css

26 ms

style.css

129 ms

jquery.js

151 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 66% of them (45 requests) were addressed to the original Richardroeper.com, 10% (7 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (256 ms) relates to the external source Syndication.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 740.7 kB (47%)

Content Size

1.6 MB

After Optimization

820.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Richardroeper.com main page is 1.6 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. 50% of websites need less resources to load. Images take 602.3 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 111.1 kB

  • Original 157.3 kB
  • After minification 155.4 kB
  • After compression 46.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. 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 111.1 kB or 71% of the original size.

Image Optimization

-3%

Potential reduce by 17.4 kB

  • Original 602.3 kB
  • After minification 584.9 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. Richardroeper images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 340.6 kB

  • Original 475.6 kB
  • After minification 383.9 kB
  • After compression 135.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 340.6 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 271.6 kB

  • Original 325.6 kB
  • After minification 307.7 kB
  • After compression 54.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. Richardroeper.com needs all CSS files to be minified and compressed as it can save up to 271.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (37%)

Requests Now

59

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

richardroeper.com

richardroeper.com

102 ms

www.richardroeper.com

www.richardroeper.com

238 ms

css

css

26 ms

style.css

style.css

129 ms

jquery.js

jquery.js

151 ms

ui.core.min.js

ui.core.min.js

77 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

72 ms

jquery.bgiframe.js

jquery.bgiframe.js

70 ms

superfish.js

superfish.js

90 ms

jcarousellite.js

jcarousellite.js

111 ms

jquery.mousewheel.js

jquery.mousewheel.js

91 ms

ui.stars.js

ui.stars.js

93 ms

jquery.cycle.all.js

jquery.cycle.all.js

118 ms

jquery.thickbox-byrne.js

jquery.thickbox-byrne.js

114 ms

jquery.truncate.js

jquery.truncate.js

114 ms

sitescript.js

sitescript.js

134 ms

functions.js.aspx

functions.js.aspx

139 ms

swfobject2.js

swfobject2.js

134 ms

WebResource.axd

WebResource.axd

73 ms

ga.js

ga.js

33 ms

bdywrprexp.jpg

bdywrprexp.jpg

152 ms

logo.png

logo.png

136 ms

mainNavArea.png

mainNavArea.png

22 ms

sprite1.gif

sprite1.gif

31 ms

sprite2.gif

sprite2.gif

30 ms

sprite3.gif

sprite3.gif

28 ms

sprite4.gif

sprite4.gif

136 ms

sprite5.gif

sprite5.gif

135 ms

reviewshdng.gif

reviewshdng.gif

139 ms

MV5BMTUxOTc5MTU1NF5BMl5BanBnXkFtZTgwODYyNTA1NzE@__V1_UX182_CR0_0_182_268_AL_.jpg

MV5BMTUxOTc5MTU1NF5BMl5BanBnXkFtZTgwODYyNTA1NzE@__V1_UX182_CR0_0_182_268_AL_.jpg

138 ms

gradessprite.gif

gradessprite.gif

137 ms

MV5BMTg0NDg2NDAwNl5BMl5BanBnXkFtZTgwMzk1Njk0NzE@__V1_UX182_CR0_0_182_268_AL_.jpg

MV5BMTg0NDg2NDAwNl5BMl5BanBnXkFtZTgwMzk1Njk0NzE@__V1_UX182_CR0_0_182_268_AL_.jpg

140 ms

MV5BMTU0NDcxMzczMV5BMl5BanBnXkFtZTgwODkxNTUwODE@__V1_UX182_CR0_0_182_268_AL_.jpg

MV5BMTU0NDcxMzczMV5BMl5BanBnXkFtZTgwODkxNTUwODE@__V1_UX182_CR0_0_182_268_AL_.jpg

143 ms

search-submit-icon.png

search-submit-icon.png

142 ms

richard_roeper_picture.jpg

richard_roeper_picture.jpg

146 ms

www_weathertech.png

www_weathertech.png

173 ms

richard-roeper-05.jpg

richard-roeper-05.jpg

142 ms

FullSizeRender-5.jpg

FullSizeRender-5.jpg

144 ms

MV5BMTkyMzI2MzQ1N15BMl5BanBnXkFtZTgwNDg0MzQxNzE@__V1_SY317_CR1_0_214_317_AL_1.jpg

MV5BMTkyMzI2MzQ1N15BMl5BanBnXkFtZTgwNDg0MzQxNzE@__V1_SY317_CR1_0_214_317_AL_1.jpg

143 ms

MV5BMjM1MDc2OTQ3NV5BMl5BanBnXkFtZTgwNzQ0NjQ1NjE@__V1_SX214_AL_1.jpg

MV5BMjM1MDc2OTQ3NV5BMl5BanBnXkFtZTgwNzQ0NjQ1NjE@__V1_SX214_AL_1.jpg

146 ms

MV5BNzg0ODI3NDQxNF5BMl5BanBnXkFtZTgwMzgzNDA0NjE@__V1_UX182_CR0_0_182_268_AL_.jpg

MV5BNzg0ODI3NDQxNF5BMl5BanBnXkFtZTgwMzgzNDA0NjE@__V1_UX182_CR0_0_182_268_AL_.jpg

147 ms

Roeper_NutsonClark_.png

Roeper_NutsonClark_.png

193 ms

follow247.png

follow247.png

164 ms

follow-icons.png

follow-icons.png

166 ms

signup-download-icons.png

signup-download-icons.png

165 ms

powered-by-american-eagle.png

powered-by-american-eagle.png

169 ms

cIFypx4yrWPDz3zOxk7hIQLUuEpTyoUstqEm5AMlJo4.woff

cIFypx4yrWPDz3zOxk7hIQLUuEpTyoUstqEm5AMlJo4.woff

128 ms

CcKI4k9un7TZVWzRVT-T873hpw3pgy2gAi-Ip7WPMi0.woff

CcKI4k9un7TZVWzRVT-T873hpw3pgy2gAi-Ip7WPMi0.woff

129 ms

-_Ctzj9b56b8RgXW8FArib3hpw3pgy2gAi-Ip7WPMi0.woff

-_Ctzj9b56b8RgXW8FArib3hpw3pgy2gAi-Ip7WPMi0.woff

133 ms

JbtMzqLaYbbbCL9X6EvaI73hpw3pgy2gAi-Ip7WPMi0.woff

JbtMzqLaYbbbCL9X6EvaI73hpw3pgy2gAi-Ip7WPMi0.woff

133 ms

1ImRNPx4870-D9a1EBUdPL3hpw3pgy2gAi-Ip7WPMi0.woff

1ImRNPx4870-D9a1EBUdPL3hpw3pgy2gAi-Ip7WPMi0.woff

134 ms

__utm.gif

__utm.gif

49 ms

624168472235352064

624168472235352064

168 ms

thickbox-loading.gif

thickbox-loading.gif

42 ms

hyzQjVUmIxk

hyzQjVUmIxk

92 ms

timeline.b67ffafa652943d0ebac45e422e410f7.default.css

timeline.b67ffafa652943d0ebac45e422e410f7.default.css

4 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

96 ms

www-embed-player.js

www-embed-player.js

130 ms

base.js

base.js

200 ms

GhTQUOyn_normal.jpeg

GhTQUOyn_normal.jpeg

111 ms

syndication

syndication

256 ms

ELTqFOCi_normal.jpeg

ELTqFOCi_normal.jpeg

83 ms

c0KHFx9G_normal.jpg

c0KHFx9G_normal.jpg

105 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

61 ms

ad_status.js

ad_status.js

45 ms

jot.html

jot.html

52 ms

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

87 ms

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

87 ms

SEO Factors

richardroeper.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 Richardroeper.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 Richardroeper.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

richardroeper.com

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