PLAY.FM Play.fm - Discover music scenes, together.

play.fm Website Information

Daily Unique Visits: 19,203

Daily Page Views: 115,218

Income Per Day: $230

Estimated Value: $165,600

play.fm is registered under .FM top-level domain. Please check other sites in .FM zone.

No name server records were found.

and is probably hosted by DIGITALOCEAN-ASN - DigitalOcean, LLC, US. See the full list of other websites hosted by DIGITALOCEAN-ASN - DigitalOcean, LLC, US.

The highest website play.fm position in Alexa rank database was 30691 and the lowest rank position was 995900. Current position of play.fm in Alexa rank database is 74686.

Desktop speed score of play.fm (66/100) is better than the results of 44.37% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of play.fm (72/100) is better than the results of 22.14% of other sites and means that the page is not mobile-friendly.

Mobile speed score of play.fm (42/100) is better than the results of 21.5% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

play.fm Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


play.fm whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


dotFM - 404 Error

dotFM® - The .FM Top-Level Domain Registry

HomeDomain AppsManage DomainsLog OutLog InRenew DomainsRegister DomainsTransfer DomainsDomain PricingWHOISBuy DomainsSearch DomainsPremiumPlus DomainsDropped DomainsRetail RegistrarsSell DomainsICANN Registrar ProgramiRRP Reseller ProgramAffiliate Program@RADIO Emails@RADIO.am Email@RADIO.fm EmailSupportKnowledgebaseManage DomainsSubmit a TicketView TicketAnnouncementsAbout UsContact Us
www..fm.am.radio.am.radio.fm.tv.com.net.org

dotFM® 404 Error - Document Not Found
The page you arelooking for may have been removed,
had its name changed, or is temporarily unavailable.

Please return to the dotFM Home Page: www.dot.fm

dotFM® - .FM Top-Level Domain
55 New Montgomery St. Ste 622
San Francisco CA 94105-3432
Toll Free US/CA: 1.888.DOT.AMFM (1.888.368.2636)
Intl/Tel: +1.415.424.4663

Home | About Us | Whois | Legal | Contact Us

1995-2016 dotFM® is a registered trademark of BRS Media Inc., All rights reserved. Please read our Domain, Dispute, Trademark,and Privacy PolicyStatements. Registrant Rights and Responsibilities (ICANN document)

play.fm server information

Servers Location

play.fm desktop page speed rank

Last tested: 2017-12-02


Desktop Speed Medium
66/100

play.fm Desktop Speed Test Quick Summary


priority - 17Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 163.7KiB (32% reduction).

Compressing https://www.play.fm/app/images/features/emilberliner.jpg could save 72.7KiB (41% reduction).
Compressing https://www.play.fm/app/images/features/shroombab.jpg could save 66.2KiB (35% reduction).
Compressing https://www.play.fm/app/images/features/spag.jpg could save 21KiB (16% reduction).
Compressing https://www.play.fm/images/icons-s7a6e5f8dd2.png could save 2.1KiB (16% reduction).
Compressing https://tpc.googlesyndication.com/simgad/15052041736907552382 could save 854B (92% reduction).
Compressing https://tpc.googlesyndication.com/simgad/7086329349867943475 could save 854B (92% reduction).

priority - 16Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.play.fm/bundles/fosjsrouting/js/router.js?19575f7
https://www.play.fm/app/js/app.js?19575f7

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Open+Sans:400,700,600
https://www.play.fm/app/css/app.css?19575f7

priority - 14Avoid landing page redirects

Your page has 3 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://play.fm/
https://play.fm/
http://www.play.fm/
https://www.play.fm/

priority - 4Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://imagesrv.adition.com/js/srp.js (expiration not specified)
https://syndication.twitter.com/settings (10 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://connect.facebook.net/en_US/all.js (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://js-agent.newrelic.com/nr-1044.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 2Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

None of the final above-the-fold content could be rendered even with the full HTML response.

priority - 1Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 6.1KiB (83% reduction).

Compressing https://ad1.adfarm1.adition.com/s?t=ijzq~EO&v=1&w=…203851*3203853*3428981 could save 6.1KiB (83% reduction).

play.fm Desktop Resource Breakdown

Total Resources123
Number of Hosts26
Static Resources59
JavaScript Resources30
CSS Resources2

play.fm mobile page speed rank

Last tested: 2017-11-28


Mobile Speed Bad
42/100

play.fm Mobile Speed Test Quick Summary


priority - 64Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.play.fm/bundles/fosjsrouting/js/router.js?19575f7
https://www.play.fm/app/js/app.js?19575f7

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Open+Sans:400,700,600
https://www.play.fm/app/css/app.css?19575f7

priority - 51Avoid landing page redirects

Your page has 3 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://play.fm/
https://play.fm/
http://www.play.fm/
https://www.play.fm/

priority - 18Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 172KiB (31% reduction).

Compressing https://www.play.fm/app/images/features/emilberliner.jpg could save 72.7KiB (41% reduction).
Compressing https://www.play.fm/app/images/features/shroombab.jpg could save 66.2KiB (35% reduction).
Compressing https://www.play.fm/app/images/features/spag.jpg could save 21KiB (16% reduction).
Compressing https://s2.adform.net/Banners/Elements/Files/14736…ath_258/background.jpg could save 5KiB (28% reduction).
Compressing https://www.play.fm/images/icons-retina-s0574a09e77.png could save 4.5KiB (12% reduction).
Compressing https://tpc.googlesyndication.com/simgad/15052041736907552382 could save 854B (92% reduction).
Compressing https://tpc.googlesyndication.com/simgad/7086329349867943475 could save 854B (92% reduction).
Compressing https://tpc.googlesyndication.com/simgad/9958363546698714078 could save 854B (92% reduction).

priority - 9Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://imagesrv.adition.com/js/adition.js (expiration not specified)
https://imagesrv.adition.com/js/srp.js (expiration not specified)
https://adfarm1.adition.com/js?wp_id=3697314&kid=2…26sr%3D0%26clickurl%3D (10 minutes)
https://syndication.twitter.com/settings (10 minutes)
https://s0.2mdn.net/ads/studio/Enabler.js (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://connect.facebook.net/en_US/all.js (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://js-agent.newrelic.com/nr-1044.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
https://s2.adform.net/Banners/Elements/Files/14736…t/bvpath_258/txt01.png (7.4 hours)
https://s2.adform.net/Banners/Elements/Files/14736…path_258/logo_icon.png (11.6 hours)

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

None of the final above-the-fold content could be rendered even with the full HTML response.

priority - 1Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 6.7KiB (83% reduction).

Compressing https://ad1.adfarm1.adition.com/s?t=ijeTxqj&v=1&w=…203851*3203853*3428981 could save 6.7KiB (83% reduction).

play.fm Mobile Resource Breakdown

Total Resources147
Number of Hosts30
Static Resources74
JavaScript Resources40
CSS Resources2

play.fm mobile page usability

Last tested: 2017-11-28


Mobile Usability Medium
72/100

play.fm Mobile Usability Test Quick Summary


priority - 15Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

DISCOVER renders only 5 pixels tall (12 CSS pixels).

SIGN UP and 1 others render only 5 pixels tall (12 CSS pixels).

OR renders only 5 pixels tall (12 CSS pixels).

UPLOAD MIXES renders only 5 pixels tall (12 CSS pixels).

Mindestvertrag…sende kündbar. and 1 others render only 4 pixels tall (11 CSS pixels).

Play.fm uses c…u agree to our and 1 others render only 6 pixels tall (16 CSS pixels).

cookie policy and 2 others render only 6 pixels tall (16 CSS pixels).

JOIN US renders only 5 pixels tall (12 CSS pixels).

Tell me more renders only 6 pixels tall (15 CSS pixels).

Emil Berliner and 1 others render only 5 pixels tall (12 CSS pixels).

Vienna/AT renders only 5 pixels tall (12 CSS pixels).

VIEW ALL and 2 others render only 4 pixels tall (11 CSS pixels).

Marco Young Glo... and 8 others render only 5 pixels tall (12 CSS pixels).

/ 1h59m 33.273 plays and 5 others render only 5 pixels tall (12 CSS pixels).

Peter Kruder,…one - das F... and 8 others render only 5 pixels tall (12 CSS pixels).

Progressive House and 12 others render only 5 pixels tall (12 CSS pixels).

PROGRESSIVE TRANCE and 79 others render only 5 pixels tall (13 CSS pixels).
Terms of Service and 6 others render only 4 pixels tall (11 CSS pixels).
supported by renders only 4 pixels tall (11 CSS pixels).

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 7Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a id="login" href="/login" class="login-button gaq">Log In</a> and 1 others are close to other tap targets.

The tap target <a href="http://adclick…play.fm%2f;C=1"> is close to 1 other tap targets.

The tap target <a id="cookies_accept" href="#" class="accept-cookies">OK</a> is close to 4 other tap targets.

The tap target <div id="page-container" class="container"></div> is close to 1 other tap targets.

The tap target <div id="hero-container">Let´s Play.fm!…supported by</div> and 3 others are close to other tap targets.

The tap target <div id="hero-container">Let´s Play.fm!…supported by</div> and 1 others are close to other tap targets.
The tap target <a id="register" href="/register" class="btn btn-block…signup-button">Join us</a> is close to 1 other tap targets.

The tap target <a href="/static/about" class="tell-more-button">Tell me more</a> is close to 1 other tap targets.

The tap target <a href="/emilberliner" class="page-link">Emil Berliner</a> is close to 1 other tap targets.

The tap target <a href="/city/vienna" class="city-link">Vienna/AT</a> is close to 1 other tap targets.

The tap target <div class="bx-pager bx-default-pager">12345678</div> is close to 3 other tap targets.

The tap target <a href="" class="bx-pager-link">1</a> and 6 others are close to other tap targets.

The tap target <a href="" class="bx-pager-link active">2</a> is close to 3 other tap targets.

The tap target <a href="/mixes/discover/trending" class="playfm-carousel-header">Trending Mixes</a> and 2 others are close to other tap targets.

The tap target <a href="/mixes/discover/trending" class="playfm-carousel-subheader">View all</a> and 2 others are close to other tap targets.

The tap target <a href="/dj-deepwater">dj-deepwater</a> and 8 others are close to other tap targets.

The tap target <a href="/dj-deepwater/night-mode">Night Mode</a> and 6 others are close to other tap targets.

The tap target <a href="" class="bx-next"></a> and 2 others are close to other tap targets.

The tap target <a href="/tag/house" class="">House</a> and 3 others are close to other tap targets.
The tap target <a href="/tag/techno" class="">Techno</a> and 3 others are close to other tap targets.
The tap target <a href="/tag/techno" class="">Techno</a> and 3 others are close to other tap targets.
The tap target <li>Dubstep</li> and 29 others are close to other tap targets.
The tap target <a href="/tag/techhouse">Techhouse</a> and 24 others are close to other tap targets.
The tap target <a href="https://www.fa…om/www.play.fm"></a> and 1 others are close to other tap targets.
The tap target <a href="/static/about">About</a> and 2 others are close to other tap targets.
The tap target <a href="https://kapper.net"></a> is close to 2 other tap targets.

priority - 3Avoid plugins

Your page uses plugins, which prevents portions of your page from being used on many platforms. Find alternatives for plugin based content to increase compatibility.

Find alternatives for the following Flash plugins.

https://www.play.fm/flash/soundmanager2_flash9.swf (8 x 8).

priority - 3Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,280 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <div></div> falls outside the viewport.
The element <div></div> falls outside the viewport.
The element <i class="fa fa-facebook"> falls outside the viewport.
The element <i class="fa fa-twitter"> falls outside the viewport.
The element <div class="klangfarbe-logo"> falls outside the viewport.
The element <div class="kapper-logo"> falls outside the viewport.

play.fm HTML validation

Errors

Attribute “xmlns:og” not allowed here.

Line: 2 Column: 16 - 74
"...TYPE html> <html lang="en" xmlns:og="http://opengraphprotocol.org/schema/" dir="ltr"> <head..."

Warnings

Attribute with the local name “xmlns:og” is not serializable as XML 1.0.

Line: 2 Column: 16 - 74
"...TYPE html> <html lang="en" xmlns:og="http://opengraphprotocol.org/schema/" dir="ltr"> <head..."

play.fm similar domains

Similar domains:
www.play.com
www.play.net
www.play.org
www.play.info
www.play.biz
www.play.us
www.play.mobi
www.lay.fm
www.play.fm
www.olay.fm
www.polay.fm
www.oplay.fm
www.llay.fm
www.pllay.fm
www.lplay.fm
www.pay.fm
www.ppay.fm
www.plpay.fm
www.pplay.fm
www.poay.fm
www.ploay.fm
www.pkay.fm
www.plkay.fm
www.pklay.fm
www.ply.fm
www.plqy.fm
www.plaqy.fm
www.plqay.fm
www.plwy.fm
www.plawy.fm
www.plway.fm
www.plsy.fm
www.plasy.fm
www.plsay.fm
www.plzy.fm
www.plazy.fm
www.plzay.fm
www.pla.fm
www.plat.fm
www.playt.fm
www.platy.fm
www.plag.fm
www.playg.fm
www.plagy.fm
www.plah.fm
www.playh.fm
www.plahy.fm
www.plau.fm
www.playu.fm
www.plauy.fm

play.fm Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


play.fm TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.