Tools & Wizards About Us
worldcupwesteros.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

worldcupwesteros.com

College of History and literature

Page Load Speed

10.4 sec in total

First Response

556 ms

Resources Loaded

1.7 sec

Page Rendered

8.2 sec

worldcupwesteros.com screenshot

About Website

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

Every 2014 World Cup team gets the Game of Thrones House treatment.

Visit worldcupwesteros.com

Key Findings

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

Performance Metrics

worldcupwesteros.com performance score

0

Network Requests Diagram

worldcupwesteros.com

556 ms

pre_tumblelog.js

14 ms

main-min.css

20 ms

tumblelog_post_message_queue.js

11 ms

jquery.min.js

91 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Worldcupwesteros.com, 21% (9 requests) were made to Assets.tumblr.com and 19% (8 requests) were made to 41.media.tumblr.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source 36.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 696.1 kB (6%)

Content Size

11.1 MB

After Optimization

10.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worldcupwesteros.com main page is 11.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 10.3 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 162.0 kB

  • Original 176.3 kB
  • After minification 107.2 kB
  • After compression 14.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. This page needs HTML code to be minified as it can gain 69.1 kB, which is 39% 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 162.0 kB or 92% of the original size.

Image Optimization

-1%

Potential reduce by 137.3 kB

  • Original 10.3 MB
  • After minification 10.2 MB

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. Worldcupwesteros images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 356.6 kB

  • Original 561.8 kB
  • After minification 561.8 kB
  • After compression 205.2 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 356.6 kB or 63% of the original size.

CSS Optimization

-77%

Potential reduce by 40.2 kB

  • Original 52.0 kB
  • After minification 51.9 kB
  • After compression 11.8 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. Worldcupwesteros.com needs all CSS files to be minified and compressed as it can save up to 40.2 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (28%)

Requests Now

40

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

worldcupwesteros.com

worldcupwesteros.com

556 ms

pre_tumblelog.js

pre_tumblelog.js

14 ms

main-min.css

main-min.css

20 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

11 ms

jquery.min.js

jquery.min.js

91 ms

main-min.js

main-min.js

89 ms

index.build.js

index.build.js

124 ms

avatar_026bd48ab57b_128.png

avatar_026bd48ab57b_128.png

284 ms

tumblr_n7jxbownYA1tf11nfo1_1280.jpg

tumblr_n7jxbownYA1tf11nfo1_1280.jpg

618 ms

like_iframe.html

like_iframe.html

272 ms

tumblr_n7jxavQaTi1tf11nfo1_1280.jpg

tumblr_n7jxavQaTi1tf11nfo1_1280.jpg

277 ms

tumblr_n7jx5m2GM71tf11nfo1_1280.jpg

tumblr_n7jx5m2GM71tf11nfo1_1280.jpg

1074 ms

tumblr_n7jwppz2ZF1tf11nfo1_1280.jpg

tumblr_n7jwppz2ZF1tf11nfo1_1280.jpg

583 ms

tumblr_n7jwnvRN2s1tf11nfo1_1280.jpg

tumblr_n7jwnvRN2s1tf11nfo1_1280.jpg

620 ms

tumblr_static_2qig8nnf5mqsc8cckkswkco4k.jpg

tumblr_static_2qig8nnf5mqsc8cckkswkco4k.jpg

240 ms

tumblr_n7jx4t4Wuy1tf11nfo1_1280.jpg

tumblr_n7jx4t4Wuy1tf11nfo1_1280.jpg

674 ms

tumblr_n7jwxybaQj1tf11nfo1_1280.jpg

tumblr_n7jwxybaQj1tf11nfo1_1280.jpg

546 ms

tumblr_n7jwn1gPdQ1tf11nfo1_1280.jpg

tumblr_n7jwn1gPdQ1tf11nfo1_1280.jpg

687 ms

tumblr_n7jx9cjBoL1tf11nfo1_1280.jpg

tumblr_n7jx9cjBoL1tf11nfo1_1280.jpg

282 ms

tumblr_n7jx8fUwbE1tf11nfo1_1280.jpg

tumblr_n7jx8fUwbE1tf11nfo1_1280.jpg

236 ms

tumblr_n7jx7mTmD91tf11nfo1_1280.jpg

tumblr_n7jx7mTmD91tf11nfo1_1280.jpg

238 ms

tumblr_n7jx6bNRAb1tf11nfo1_1280.jpg

tumblr_n7jx6bNRAb1tf11nfo1_1280.jpg

240 ms

tumblr_n7jx0vx8CN1tf11nfo1_1280.jpg

tumblr_n7jx0vx8CN1tf11nfo1_1280.jpg

242 ms

tumblr_n7jwweyrmj1tf11nfo1_1280.jpg

tumblr_n7jwweyrmj1tf11nfo1_1280.jpg

242 ms

tumblr_n7jwokZiFV1tf11nfo1_1280.jpg

tumblr_n7jwokZiFV1tf11nfo1_1280.jpg

282 ms

analytics.js

analytics.js

204 ms

impixu

impixu

255 ms

impixu

impixu

349 ms

analytics.html

analytics.html

181 ms

8EN1DX6pvX3m1fBD9AETcHqcA

8EN1DX6pvX3m1fBD9AETcHqcA

19 ms

login_check.html

login_check.html

59 ms

collect

collect

106 ms

iframe_logo.png

iframe_logo.png

79 ms

avatar_026bd48ab57b_40.png

avatar_026bd48ab57b_40.png

112 ms

rapid-3.36.1.js

rapid-3.36.1.js

13 ms

rapidworker-1.2.js

rapidworker-1.2.js

20 ms

ga.js

ga.js

70 ms

analytics.js

analytics.js

62 ms

cs.js

cs.js

108 ms

yql

yql

249 ms

__utm.gif

__utm.gif

18 ms

cedexis.radar.js

cedexis.radar.js

6 ms

SEO Factors

worldcupwesteros.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Worldcupwesteros.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Worldcupwesteros.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

worldcupwesteros.com

Open Graph data is detected on the main page of Worldcupwesteros. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: