Tools & Wizards About Us
worldwomen2013.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

worldwomen2013.com

Frontpage - WW - International Ice Hockey Federation IIHF

Page Load Speed

7.1 sec in total

First Response

2.1 sec

Resources Loaded

4.8 sec

Page Rendered

225 ms

worldwomen2013.com screenshot

About Website

Visit worldwomen2013.com now to see the best up-to-date Worldwomen 2013 content and also check out these interesting facts you probably never knew about worldwomen2013.com

Visit worldwomen2013.com

Key Findings

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

Performance Metrics

worldwomen2013.com performance score

0

Network Requests Diagram

www.worldwomen2013.com

2100 ms

resets.css

194 ms

styles.css

307 ms

live-ticker.css

209 ms

schedule.css

213 ms

Our browser made a total of 152 requests to load all elements on the main page. We found that 70% of them (106 requests) were addressed to the original Worldwomen2013.com, 12% (18 requests) were made to Stats.iihf.com and 7% (11 requests) were made to Api.channels.iihf.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Worldwomen2013.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 422.6 kB (32%)

Content Size

1.3 MB

After Optimization

915.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 66.9 kB

  • Original 77.1 kB
  • After minification 71.2 kB
  • After compression 10.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 66.9 kB or 87% of the original size.

Image Optimization

-12%

Potential reduce by 110.1 kB

  • Original 918.9 kB
  • After minification 808.8 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, Worldwomen 2013 needs image optimization as it can save up to 110.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 161.0 kB

  • Original 240.8 kB
  • After minification 201.4 kB
  • After compression 79.8 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 161.0 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 84.6 kB

  • Original 101.7 kB
  • After minification 76.9 kB
  • After compression 17.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. Worldwomen2013.com needs all CSS files to be minified and compressed as it can save up to 84.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 76 (51%)

Requests Now

148

After Optimization

72

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.worldwomen2013.com

www.worldwomen2013.com

2100 ms

resets.css

resets.css

194 ms

styles.css

styles.css

307 ms

live-ticker.css

live-ticker.css

209 ms

schedule.css

schedule.css

213 ms

footer.css

footer.css

206 ms

teams.css

teams.css

281 ms

media.css

media.css

294 ms

games.css

games.css

308 ms

standings.css

standings.css

306 ms

statistics.css

statistics.css

313 ms

fancybox.css

fancybox.css

379 ms

scoringleaders.css

scoringleaders.css

384 ms

game-summary.css

game-summary.css

405 ms

playoffs.css

playoffs.css

407 ms

anythingslider.css

anythingslider.css

408 ms

DynamicCss

DynamicCss

861 ms

css

css

46 ms

css

css

57 ms

jquery-1.8.1.min.js

jquery-1.8.1.min.js

717 ms

schedule_v2.js

schedule_v2.js

472 ms

jquery.fancybox.js

jquery.fancybox.js

574 ms

jquery.anythingslider.min.js

jquery.anythingslider.min.js

500 ms

fancybox.js

fancybox.js

504 ms

generic.js

generic.js

506 ms

accordion.js

accordion.js

567 ms

hydra_widgets.js

hydra_widgets.js

598 ms

jquery.jsonp-2.4.0.min.js

jquery.jsonp-2.4.0.min.js

605 ms

scrollingcarousel.2.0.min.js

scrollingcarousel.2.0.min.js

608 ms

date.format.js

date.format.js

663 ms

countdown.js

countdown.js

670 ms

maps.js

maps.js

697 ms

js

js

44 ms

print.css

print.css

98 ms

ga.js

ga.js

40 ms

bg_crystal.jpg

bg_crystal.jpg

115 ms

logo_iihf_tiny.png

logo_iihf_tiny.png

174 ms

bg_chanel_dropdown.png

bg_chanel_dropdown.png

114 ms

transparency.png

transparency.png

116 ms

2013_wm.png

2013_wm.png

116 ms

2013%20WMIA.png

2013%20WMIA.png

116 ms

2013%20WMIIA.png

2013%20WMIIA.png

195 ms

2013_wmib.png

2013_wmib.png

217 ms

2013%20WMIIB.png

2013%20WMIIB.png

241 ms

2013%20WMIII.png

2013%20WMIII.png

239 ms

2013%20WMIIIQ.png

2013%20WMIIIQ.png

238 ms

wm20.png

wm20.png

272 ms

2013%20WM20IA.png

2013%20WM20IA.png

294 ms

2013%20WM20IIA.png

2013%20WM20IIA.png

319 ms

2013%20WM20IB.png

2013%20WM20IB.png

332 ms

2013%20WM20IIB.png

2013%20WM20IIB.png

326 ms

2013%20WM20III.png

2013%20WM20III.png

337 ms

2013%20WM18.png

2013%20WM18.png

380 ms

2013%20WM18IA.png

2013%20WM18IA.png

398 ms

2013%20WM18IIA.png

2013%20WM18IIA.png

423 ms

2013%20WM18IIIA.png

2013%20WM18IIIA.png

432 ms

2013_wm18ib_hor_col.png

2013_wm18ib_hor_col.png

440 ms

2013%20WM18IIB.png

2013%20WM18IIB.png

444 ms

2013%20WM18IIIB.png

2013%20WM18IIIB.png

484 ms

2013_ww.png

2013_ww.png

503 ms

2013%20WWIA.png

2013%20WWIA.png

531 ms

2013%20WWIIA.png

2013%20WWIIA.png

549 ms

wwib.png

wwib.png

549 ms

2013_wwiib_spain.png

2013_wwiib_spain.png

551 ms

2013%20WWIIBQ.png

2013%20WWIIBQ.png

592 ms

2013%20WW18.png

2013%20WW18.png

602 ms

2013%20WW18I.png

2013%20WW18I.png

623 ms

2013%20WW18IQ.png

2013%20WW18IQ.png

639 ms

2013_ww.png

2013_ww.png

658 ms

ca.png

ca.png

652 ms

um.png

um.png

694 ms

bg_top_new.png

bg_top_new.png

105 ms

navibar.png

navibar.png

200 ms

main-navi-spacer.png

main-navi-spacer.png

206 ms

main_navi_active.png

main_navi_active.png

203 ms

main_navi.png

main_navi.png

202 ms

slider_nav.png

slider_nav.png

204 ms

columnbox_header.png

columnbox_header.png

229 ms

btn_small.png

btn_small.png

276 ms

2koEo4AKFSvK4B52O_MwaonF5uFdDttMLvmWuJdhhgs.ttf

2koEo4AKFSvK4B52O_MwaonF5uFdDttMLvmWuJdhhgs.ttf

32 ms

EvPKapBawcLZ3hbihjhqAaCWcynf_cDxXwCLxiixG1c.ttf

EvPKapBawcLZ3hbihjhqAaCWcynf_cDxXwCLxiixG1c.ttf

32 ms

__utm.gif

__utm.gif

45 ms

tweet_button.html

tweet_button.html

161 ms

fastbutton

fastbutton

75 ms

widget_en_2013_ww_scoreboard.html

widget_en_2013_ww_scoreboard.html

412 ms

widget_en_2013_ww_schedule_simple.html

widget_en_2013_ww_schedule_simple.html

434 ms

widget_en_2013_ww_playoffs.html

widget_en_2013_ww_playoffs.html

318 ms

widget_en_2013_ww_scoring_leaders.html

widget_en_2013_ww_scoring_leaders.html

433 ms

bg_crystal_footer.jpg

bg_crystal_footer.jpg

310 ms

ch.png

ch.png

603 ms

fi.png

fi.png

615 ms

se.png

se.png

630 ms

ru.png

ru.png

646 ms

de.png

de.png

651 ms

rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw

rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw

10 ms

like.php

like.php

213 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

27 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

34 ms

cz.png

cz.png

632 ms

ios_platform.png

ios_platform.png

610 ms

android_platform.png

android_platform.png

606 ms

jot

jot

102 ms

bb_platform.png

bb_platform.png

608 ms

wp_platform.png

wp_platform.png

624 ms

200px-Esso_logo_svg.png

200px-Esso_logo_svg.png

632 ms

200px-Logo_NIKE_svg.png

200px-Logo_NIKE_svg.png

637 ms

200px-Royal_Bank_of_Canada_svg.png

200px-Royal_Bank_of_Canada_svg.png

612 ms

200px-Telus-Logo_svg.png

200px-Telus-Logo_svg.png

607 ms

facebook.png

facebook.png

620 ms

twitter.png

twitter.png

634 ms

key_visual_top_left.png

key_visual_top_left.png

637 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

293 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

332 ms

key_visual_top_right.png

key_visual_top_right.png

624 ms

key_visual_bottom_left.png

key_visual_bottom_left.png

610 ms

SUI.png

SUI.png

112 ms

RUS.png

RUS.png

188 ms

FIN.png

FIN.png

195 ms

GER.png

GER.png

197 ms

CAN.png

CAN.png

197 ms

USA.png

USA.png

202 ms

key_visual_bottom_right.png

key_visual_bottom_right.png

595 ms

IMG_3302_Channel%20Homepage%20Slider.JPG

IMG_3302_Channel%20Homepage%20Slider.JPG

1012 ms

AR4_3602_Channel%20Homepage%20Slider.JPG

AR4_3602_Channel%20Homepage%20Slider.JPG

1037 ms

CHYT0945_Channel%20Homepage%20Slider.JPG

CHYT0945_Channel%20Homepage%20Slider.JPG

939 ms

fran-rider-pic_Channel%20Homepage%20Slider.jpg

fran-rider-pic_Channel%20Homepage%20Slider.jpg

903 ms

bg_slider_nav.png

bg_slider_nav.png

608 ms

RUS.png

RUS.png

103 ms

GER.png

GER.png

192 ms

FIN.png

FIN.png

189 ms

SUI.png

SUI.png

202 ms

SWE.png

SWE.png

204 ms

CZE.png

CZE.png

204 ms

CAN.png

CAN.png

213 ms

USA.png

USA.png

291 ms

transparency_blank.png

transparency_blank.png

585 ms

pager_button.png

pager_button.png

194 ms

slider_vert_divider.png

slider_vert_divider.png

662 ms

iihf_loading_grey.gif

iihf_loading_grey.gif

663 ms

bdr_image_small.png

bdr_image_small.png

764 ms

Sue-1_News%20Preview.jpg

Sue-1_News%20Preview.jpg

724 ms

WD9Z7784_News%20Preview.JPG

WD9Z7784_News%20Preview.JPG

839 ms

lina-backlin-6_News%20Preview.jpg

lina-backlin-6_News%20Preview.jpg

794 ms

ohc_News%20Preview.bmp

ohc_News%20Preview.bmp

849 ms

AR4_2730_News%20Preview.JPG

AR4_2730_News%20Preview.JPG

833 ms

CHYT0281_News%20Preview.JPG

CHYT0281_News%20Preview.JPG

862 ms

CHYT9403_News%20Preview.JPG

CHYT9403_News%20Preview.JPG

853 ms

tissot.jpg

tissot.jpg

847 ms

logo_iihf.png

logo_iihf.png

859 ms

border_bottom.png

border_bottom.png

844 ms

bg_table_top_column_3_of_3.png

bg_table_top_column_3_of_3.png

833 ms

SEO Factors

worldwomen2013.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 Worldwomen2013.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 Worldwomen2013.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

worldwomen2013.com

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