Analyze

blip.fm: DEV Free Music | Listen to Music Online | Free Streaming Radio | Blip.fm

Search for free music to stream. Listen to free music recommended by real people. Create your own free internet radio station.

Page load speed analysis

  • 39/100

    Normal result
  • 3

    Successful tests
  • 5

    Failed tests
  • First response

    204 ms

  • Resources loaded

    31.2 sec

  • Page rendered

    6.4 sec

  • Total page load time

    37.9 sec

Visit blip.fm now to see the best up-to-date Blip content for India and also check out these interesting facts you probably never knew about blip.fm

We analyzed Blip.fm page load time and found that the first response time was 204 ms and then it took 37.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Page optimization

  • HTML 20.5 kB
    Images 11.1 kB
    Javascripts 1.4 MB
    CSS 281.5 kB

    In fact, the total size of Blip.fm main page is 1.7 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. 65% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.

    • Original 20.5 kB
    • After minification 17.3 kB
    • After compression 5.5 kB

    HTML optimization

    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 3.2 kB, which is 16% 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 15.0 kB or 73% of the original size.

    • Original 11.1 kB
    • After optimization 10.2 kB

    Image optimization

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

    • Original 1.4 MB
    • After minification 1.4 MB
    • After compression 434.8 kB

    JavaScript optimization

    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 950.5 kB or 69% of the original size.

    • Original 281.5 kB
    • After minification 271.6 kB
    • After compression 119.7 kB

    CSS optimization

    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. Blip.fm needs all CSS files to be minified and compressed as it can save up to 161.8 kB or 57% of the original size.

Network requests diagram

  • blip.fm
  • blip.fm
  • merge.v4.2.112668.js
  • gpt.js
  • api.js
  • videojs-ie8.min.js
  • video-js.css
  • base.19.css.cgz
  • index.19.css.cgz
  • base.19.js.jgz
  • index.19.js.jgz
  • quant.js
  • gendmuid
  • pubads_impl_147.js
  • recaptcha__en.js
  • bid
  • jpt
  • ;alias=;cmd=bid;cors=yes;bidfloor=0;v=2;cfp=1;rndc=55649223
  • getjs.static.js
  • container.html
  • sync.html
  • sitebg.jpg
  • ga.js
  • blipfm_lg.png
  • activity;src=2053556;dcnet=4591;boom=22507;sz=1x1;ord=1
  • spinner.gif
  • login.png
  • twitter.png
  • facebook.png
  • friendfeed.png
  • tumblr.png
  • livejournal.png
  • audioscrobbler.png
  • pingfm.png
  • dmio_sync.js
  • sprite-uber.png
  • menubg.png
  • inputbg.png
  • juicy-signup.png
  • ads
  • dm
  • rules-p-b0cBKofGeCYKg.js
  • rules-p-c4o3JsfzdTxY6.js
  • anchor
  • noticebg-black.png
  • close.png
  • alert.png
  • dialogbg.png
  • styles__ltr.css
  • container.html
  • osd.js
  • collect
  • logo_48.png
  • b74UPo3_igVccGeHOnfuS0OSqia1wD3kZRAauYJXgWA.js
  • webworker.js
  • QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
  • RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
  • mnpfi9pxYH-Go5UiibESIiZ2oysoEQEeKwjgmXLRnTc.ttf
  • bframe
  • m_js_controller.js
  • abg.js
  • m_window_focus_non_hydra.js
  • osd_listener.js
  • nessie_icon_tiamat_black.png
  • pixel;r=1205509706;rf=0;a=p-b0cBKofGeCYKg;url=https%3A%2F%2Fblip.fm%2F;fpan=1;fpa=P0-50496663-1504623037405;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504623037405;tzo=-180;ogl=
  • x_button_blue2.png
  • pixel;r=1817232469;rf=0;a=p-c4o3JsfzdTxY6;url=https%3A%2F%2Fblip.fm%2F;fpan=0;fpa=P0-50496663-1504623037405;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504623037720;tzo=-180;ogl=
  • recaptcha__en.js
  • recaptcha__en.js
  • iconx2-000000.png
  • s
  • googlelogo_dark_color_84x28dp.png
  • activeview

Our browser made a total of 73 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Blip.fm, 32% (23 requests) were made to D1uswytv6491xe.cloudfront.net and 11% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (14.9 sec) relates to the external source Um2.eqads.com.

Additional info on blip.fm

Requests

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

27

Javascripts

29

Images

4

CSS

7

AJAX

67

All

Possible request optimization

1

Javascripts

12

Images

1

CSS

7

AJAX

46

Optimized

21

All

Normal result

Redirects

As for redirects, our browser was forwarded to https://blip.fm/ before it reached this domain.

IP address

Blip.fm uses IP address which is currently shared with 2 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

blip.fm

sessions.blip.fm

blipstage.com

54.163.233.121

DNS records

Type Host Target/ip TTL Other
A

blip.fm

54.163.233.121 300
NS

blip.fm

dns1.idnz.net 300
NS

blip.fm

dns2.idnz.net 300
SOA

blip.fm

300 Mname: dns1.idnz.net
Rname: soacontact.dnsprovision.com
Serial: 1442640068
Refresh: 14400
Retry: 7200
Expire: 950400
Minimum-ttl: 7200
MX

blip.fm

ALT4.ASPMX.L.GOOGLE.COM 300 Pri: 10

Language and encoding

Good result

Language

EN en language flag

Detected

EN en language flag

Claimed

Encoding

UTF-8

Claimed

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

HTTPS certificate

SSL Certificate

Blip.fm has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 61.8% of all visits is India. It lies approximately 8040 miles away from the server location (United States) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up Blip.fm page load time for the majority of users is moving the server to India or just closer to the user base.

Poor result

Poor result

Social Sharing Optimization

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

blip.fm

Share this report in social media

Analyze another website

Analyze