Tools & Wizards About Us
superbuzzland.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

superbuzzland.com

Page Load Speed

4 sec in total

First Response

56 ms

Resources Loaded

3.7 sec

Page Rendered

217 ms

superbuzzland.com screenshot

About Website

Click here to check amazing Superbuzzland content. Otherwise, check out these important facts you probably never knew about superbuzzland.com

CLEVELAND, OH -- The following information was released by the Cleveland Division of the... | Article from States News Service July 18, 2011

Visit superbuzzland.com

Key Findings

We analyzed Superbuzzland.com page load time and found that the first response time was 56 ms 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.

Performance Metrics

superbuzzland.com performance score

0

Network Requests Diagram

1G1-263224944.html

56 ms

1G1-263224944.html

851 ms

base.css

73 ms

shorthand.css

111 ms

jquery-ui-1.8.4.css

197 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Superbuzzland.com, 8% (8 requests) were made to Apis.google.com and 5% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Highbeam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (68%)

Content Size

1.9 MB

After Optimization

606.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Superbuzzland.com main page is 1.9 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 159.7 kB

  • Original 201.6 kB
  • After minification 176.3 kB
  • After compression 41.9 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 25.3 kB, which is 13% 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 159.7 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 2.6 kB

  • Original 40.1 kB
  • After minification 37.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. Superbuzzland images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 976.9 kB

  • Original 1.5 MB
  • After minification 1.4 MB
  • After compression 498.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 976.9 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 154.5 kB

  • Original 183.9 kB
  • After minification 132.6 kB
  • After compression 29.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. Superbuzzland.com needs all CSS files to be minified and compressed as it can save up to 154.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (75%)

Requests Now

87

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1G1-263224944.html

1G1-263224944.html

56 ms

1G1-263224944.html

1G1-263224944.html

851 ms

base.css

base.css

73 ms

shorthand.css

shorthand.css

111 ms

jquery-ui-1.8.4.css

jquery-ui-1.8.4.css

197 ms

doc.css

doc.css

244 ms

MicrosoftAjax.js

MicrosoftAjax.js

195 ms

MicrosoftMvcAjax.js

MicrosoftMvcAjax.js

233 ms

jquery-1.7.min.js

jquery-1.7.min.js

204 ms

jquery-ui.min.js

jquery-ui.min.js

331 ms

common.js

common.js

280 ms

topics.js

topics.js

302 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

313 ms

homepage.js

homepage.js

346 ms

jquery.cycle.all.js

jquery.cycle.all.js

374 ms

json2.js

json2.js

411 ms

mrc.js

mrc.js

1492 ms

ea.js

ea.js

904 ms

malt.js

malt.js

461 ms

doc.js

doc.js

1546 ms

fieldfunctions.js

fieldfunctions.js

1036 ms

searchresults.js

searchresults.js

482 ms

publication.js

publication.js

545 ms

typeahead.js

typeahead.js

613 ms

mbox.js

mbox.js

679 ms

jquery.ui.autocomplete.html.js

jquery.ui.autocomplete.html.js

1198 ms

responsive.css

responsive.css

705 ms

doc-responsive.css

doc-responsive.css

732 ms

addthis_widget.js

addthis_widget.js

75 ms

adsbygoogle.js

adsbygoogle.js

40 ms

omniture_s_code.js

omniture_s_code.js

824 ms

tag.js

tag.js

39 ms

omniture.js

omniture.js

866 ms

gpt.js

gpt.js

68 ms

logo_189.png

logo_189.png

62 ms

header_sprite.png

header_sprite.png

77 ms

tools-icon-sprite.png

tools-icon-sprite.png

61 ms

cengage_brain_study_tools_300x100.png

cengage_brain_study_tools_300x100.png

61 ms

ca-pub-1767711865744298.js

ca-pub-1767711865744298.js

15 ms

zrt_lookup.html

zrt_lookup.html

110 ms

show_ads_impl.js

show_ads_impl.js

110 ms

pubads_impl_82.js

pubads_impl_82.js

166 ms

print.css

print.css

100 ms

footer-shadow.png

footer-shadow.png

94 ms

footer-sprite.png

footer-sprite.png

94 ms

tag

tag

240 ms

layers.e5ea973510bf60b3db41.js

layers.e5ea973510bf60b3db41.js

138 ms

300lo.json

300lo.json

236 ms

plusone.js

plusone.js

240 ms

all.js&version=v2.0

all.js&version=v2.0

414 ms

widgets.js

widgets.js

203 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

139 ms

ads

ads

314 ms

osd.js

osd.js

111 ms

ads

ads

336 ms

ads

ads

381 ms

container.html

container.html

139 ms

unsupportedbrowser

unsupportedbrowser

156 ms

ga.js

ga.js

153 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

28 ms

s43217282930854

s43217282930854

123 ms

5488.gif

5488.gif

123 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

28 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

26 ms

fastbutton

fastbutton

105 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

58 ms

postmessageRelay

postmessageRelay

199 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

48 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

48 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

227 ms

__utm.gif

__utm.gif

127 ms

m_js_controller.js

m_js_controller.js

40 ms

abg.js

abg.js

126 ms

favicon

favicon

191 ms

favicon

favicon

176 ms

favicon

favicon

182 ms

favicon

favicon

175 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

178 ms

favicon

favicon

201 ms

favicon

favicon

217 ms

favicon

favicon

224 ms

favicon

favicon

233 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

143 ms

jot

jot

264 ms

114 ms

collect

collect

165 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

134 ms

rpc:shindig_random.js

rpc:shindig_random.js

100 ms

s

s

86 ms

favicon

favicon

66 ms

x_button_blue2.png

x_button_blue2.png

36 ms

favicon

favicon

50 ms

xd_arbiter.php

xd_arbiter.php

202 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

26 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

15 ms

unsupportedbrowser

unsupportedbrowser

86 ms

SEO Factors

superbuzzland.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Superbuzzland.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 Superbuzzland.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

superbuzzland.com

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