3 sec in total
552 ms
2.2 sec
219 ms
Click here to check amazing IIHF content for United States. Otherwise, check out these important facts you probably never knew about iihf.com
IIHF - Home
Visit iihf.comWe analyzed Iihf.com page load time and found that the first response time was 552 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
iihf.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value30.4 s
0/100
25%
Value13.0 s
2/100
10%
Value1,670 ms
11/100
30%
Value1.046
2/100
15%
Value30.3 s
0/100
10%
552 ms
107 ms
203 ms
205 ms
200 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 86% of them (59 requests) were addressed to the original Iihf.com, 4% (3 requests) were made to Ajax.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (686 ms) belongs to the original domain Iihf.com.
Page size can be reduced by 129.5 kB (30%)
426.3 kB
296.9 kB
In fact, the total size of Iihf.com main page is 426.3 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. 35% of websites need less resources to load. Images take 287.1 kB which makes up the majority of the site volume.
Potential reduce by 42.0 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 42.0 kB or 80% of the original size.
Potential reduce by 27.7 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. IIHF images are well optimized though.
Potential reduce by 6.7 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 6.7 kB or 26% of the original size.
Potential reduce by 53.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. Iihf.com needs all CSS files to be minified and compressed as it can save up to 53.0 kB or 87% of the original size.
Number of requests can be reduced by 24 (35%)
68
44
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IIHF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.iihf.com
552 ms
stylesheet_e28a30bf4b.css
107 ms
styles.css
203 ms
tt_news_fix_update.css
205 ms
javascript_93077bb238.js
200 ms
jquery.min.js
32 ms
jquery-ui.min.js
53 ms
jquery-ui.css
52 ms
ui.theme.css
10 ms
AC_OETags.js
226 ms
sdk.js
160 ms
ga.js
31 ms
bg.jpg
104 ms
row.jpg
203 ms
logo.gif
98 ms
header_1.gif
218 ms
navMain_off.jpg
99 ms
nav_statik_media.png
200 ms
nav_statik_extranet.png
199 ms
nav_statik_sitemap.png
215 ms
nav_statik_contact.png
215 ms
bgHeader_sub2.png
293 ms
navFederation_on.jpg
294 ms
navFederation_off.jpg
297 ms
social2.jpg
320 ms
pannel_small.png
320 ms
footer_small.png
316 ms
WM.gif
391 ms
ea42b1b25d.jpg
391 ms
0d1ee7457e.jpg
394 ms
arena_guide155.jpg
419 ms
pannel_big.png
422 ms
more_link_archive.jpg
419 ms
d4ac2d760c.jpg
490 ms
WC10_news_link.gif
487 ms
clear.gif
492 ms
d2225af178.jpg
521 ms
1029348782.jpg
522 ms
9fa24dce47.jpg
523 ms
spacer.gif
584 ms
footer_big.png
585 ms
more_link_intern.jpg
589 ms
Nike.jpg
623 ms
Tissot.jpg
625 ms
Bauer.jpg
627 ms
Busch3.gif
679 ms
CCM.jpg
680 ms
Easton2011.jpg
686 ms
__utm.gif
25 ms
Fischer2012.gif
638 ms
Frontier2012.gif
639 ms
Graf2011.jpg
636 ms
142 ms
xd_arbiter.php
131 ms
xd_arbiter.php
256 ms
Gufex.jpg
590 ms
Koho.jpg
589 ms
Reebok.jpg
597 ms
Sherwood2012.gif
623 ms
STX.gif
623 ms
Tackla.jpg
623 ms
True.gif
591 ms
Warrior2012.gif
592 ms
leer.gif
601 ms
72858d1ade.jpg
622 ms
413280a775.jpg
621 ms
RTEmagicC_hockeycentre.jpg.jpg
621 ms
RTEmagicC_hockeycentre_officials.jpg.jpg
589 ms
line.gif
588 ms
iihf.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
iihf.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
iihf.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iihf.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 Iihf.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.
iihf.com
Open Graph description is not detected on the main page of IIHF. 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: