Tools & Wizards About Us
blog.imogenheap.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blog.imogenheap.com

Imogen Heap's iBlog

Page Load Speed

21 sec in total

First Response

196 ms

Resources Loaded

20.6 sec

Page Rendered

186 ms

blog.imogenheap.com screenshot

About Website

Click here to check amazing Blog Imogen Heap content for United States. Otherwise, check out these important facts you probably never knew about blog.imogenheap.com

Tweeting from China / Bhutan / India until 23/12/11. New songs released from my 4th solo album as I complete them. 4 out already! More at www.imogenheap.com

Visit blog.imogenheap.com

Key Findings

We analyzed Blog.imogenheap.com page load time and found that the first response time was 196 ms and then it took 20.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

blog.imogenheap.com performance score

0

Network Requests Diagram

blog.imogenheap.com

196 ms

pre_tumblelog.js

4 ms

tumblelog_post_message_queue.js

8 ms

stylesheet.css

10 ms

tumblr_header.png

62 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original Blog.imogenheap.com, 38% (17 requests) were made to Assets.tumblr.com and 11% (5 requests) were made to 68.media.tumblr.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source 68.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.0 kB (66%)

Content Size

529.9 kB

After Optimization

180.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.imogenheap.com main page is 529.9 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. 75% 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. CSS take 259.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 68.3 kB

  • Original 82.3 kB
  • After minification 73.3 kB
  • After compression 14.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. This page needs HTML code to be minified as it can gain 9.0 kB, which is 11% 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 68.3 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 139 B

  • Original 27.0 kB
  • After minification 26.9 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. Blog Imogen Heap images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 66.6 kB

  • Original 161.2 kB
  • After minification 161.1 kB
  • After compression 94.6 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 66.6 kB or 41% of the original size.

CSS Optimization

-83%

Potential reduce by 214.1 kB

  • Original 259.4 kB
  • After minification 259.3 kB
  • After compression 45.3 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. Blog.imogenheap.com needs all CSS files to be minified and compressed as it can save up to 214.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (57%)

Requests Now

28

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.imogenheap.com

blog.imogenheap.com

196 ms

pre_tumblelog.js

pre_tumblelog.js

4 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

8 ms

stylesheet.css

stylesheet.css

10 ms

tumblr_header.png

tumblr_header.png

62 ms

tumblr_mvqxeck1gf1qzgghwo1_500.png

tumblr_mvqxeck1gf1qzgghwo1_500.png

20369 ms

MxRJtsigX3s

MxRJtsigX3s

146 ms

tumblr_muriujZb9U1qzgghwo1_500.jpg

tumblr_muriujZb9U1qzgghwo1_500.jpg

20367 ms

tumblr_murirfSNC31qzgghwo1_500.jpg

tumblr_murirfSNC31qzgghwo1_500.jpg

20368 ms

tumblr_muripasCxI1qzgghwo1_500.jpg

tumblr_muripasCxI1qzgghwo1_500.jpg

20368 ms

avatar_06538e871e04_128.png

avatar_06538e871e04_128.png

20368 ms

ga.js

ga.js

17 ms

impixu

impixu

243 ms

shadow-post.png

shadow-post.png

48 ms

avatar-bg.png

avatar-bg.png

45 ms

sidebar-follow-on-en_US.png

sidebar-follow-on-en_US.png

48 ms

button-rss.png

button-rss.png

46 ms

button-random.png

button-random.png

45 ms

button-archive.png

button-archive.png

47 ms

button-mobile.png

button-mobile.png

135 ms

sidebar-bottom.png

sidebar-bottom.png

133 ms

iblog-grid-bg.jpg

iblog-grid-bg.jpg

20357 ms

analytics.html

analytics.html

50 ms

index.build.js

index.build.js

50 ms

impixu

impixu

237 ms

__utm.gif

__utm.gif

18 ms

rapid-3.42.2.js

rapid-3.42.2.js

86 ms

rapidworker-1.2.js

rapidworker-1.2.js

87 ms

showads.js

showads.js

114 ms

px.js

px.js

118 ms

login_check.html

login_check.html

14 ms

www-player-vflMqr8uC.css

www-player-vflMqr8uC.css

83 ms

www-embed-player.js

www-embed-player.js

102 ms

base.js

base.js

111 ms

ga.js

ga.js

314 ms

analytics.js

analytics.js

272 ms

cs.js

cs.js

267 ms

px.js

px.js

171 ms

id

id

165 ms

8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js

8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js

161 ms

ad_status.js

ad_status.js

156 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

94 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

98 ms

logo_ringo-vflOpz8ZI.png

logo_ringo-vflOpz8ZI.png

92 ms

1-13960-radar10.min.js

1-13960-radar10.min.js

5 ms

SEO Factors

blog.imogenheap.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.imogenheap.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 Blog.imogenheap.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

blog.imogenheap.com

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