Tools & Wizards About Us
iwhs.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

iwhs.com

Page Load Speed

4.1 sec in total

First Response

896 ms

Resources Loaded

3.2 sec

Page Rendered

80 ms

iwhs.com screenshot

About Website

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

Visit iwhs.com

Key Findings

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

Performance Metrics

iwhs.com performance score

0

Network Requests Diagram

iwhs.com

896 ms

v_1442344211478_879

1728 ms

videoPlayerMain.css

40 ms

videoPlayer.theme2.css

66 ms

font-awesome.css

70 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Iwhs.com, 73% (29 requests) were made to V.myclip.com and 8% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source V.myclip.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 919.4 kB (73%)

Content Size

1.3 MB

After Optimization

334.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iwhs.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. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-29%

Potential reduce by 60 B

  • Original 210 B
  • After minification 210 B
  • After compression 150 B

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 60 B or 29% of the original size.

Image Optimization

-1%

Potential reduce by 39 B

  • Original 5.2 kB
  • After minification 5.2 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. Iwhs images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 840.2 kB

  • Original 1.2 MB
  • After minification 1.0 MB
  • After compression 314.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 840.2 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 79.1 kB

  • Original 94.0 kB
  • After minification 68.8 kB
  • After compression 14.9 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. Iwhs.com needs all CSS files to be minified and compressed as it can save up to 79.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (87%)

Requests Now

39

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iwhs.com

iwhs.com

896 ms

v_1442344211478_879

v_1442344211478_879

1728 ms

videoPlayerMain.css

videoPlayerMain.css

40 ms

videoPlayer.theme2.css

videoPlayer.theme2.css

66 ms

font-awesome.css

font-awesome.css

70 ms

style.css

style.css

68 ms

sharegg.css

sharegg.css

66 ms

jquery.js

jquery.js

99 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

115 ms

froogaloop.js

froogaloop.js

70 ms

IScroll4Custom.js

IScroll4Custom.js

94 ms

THREEx.FullScreen.js

THREEx.FullScreen.js

91 ms

videoPlayer.js

videoPlayer.js

132 ms

Playlist.js

Playlist.js

94 ms

font-awesome.min.css

font-awesome.min.css

7 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

67 ms

ibacor_share.min.js

ibacor_share.min.js

93 ms

ibacor-sosmed-button.css

ibacor-sosmed-button.css

128 ms

addthis_widget.js

addthis_widget.js

33 ms

jquery.min.js

jquery.min.js

207 ms

jquery.sharegg.js

jquery.sharegg.js

127 ms

analytics.js

analytics.js

69 ms

count.donreach.com

count.donreach.com

297 ms

300lo.json

300lo.json

52 ms

buffer.png

buffer.png

53 ms

delicious.png

delicious.png

53 ms

digg.png

digg.png

52 ms

facebook.png

facebook.png

52 ms

google_plus.png

google_plus.png

53 ms

linkedin.png

linkedin.png

51 ms

pinterest.png

pinterest.png

86 ms

pocket.png

pocket.png

85 ms

reddit.png

reddit.png

86 ms

stumbleupon.png

stumbleupon.png

85 ms

tumblr.png

tumblr.png

86 ms

twitter.png

twitter.png

86 ms

vkontakte.png

vkontakte.png

101 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

37 ms

collect

collect

26 ms

layers.e5ea973510bf60b3db41.js

layers.e5ea973510bf60b3db41.js

7 ms

SEO Factors

iwhs.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iwhs.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Iwhs.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

iwhs.com

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