muses.org Website Information

Daily Unique Visits: 746

Daily Page Views: 1,492

Income Per Day: $5

Estimated Value: $1,200

This website is located in United States and is using following IP address 69.64.59.235. See the complete list of popular websites hosted in United States.

muses.org is registered under .ORG top-level domain. Please check other sites in .ORG zone.

Website muses.org is using the following name servers:

dns3.dokkogroup.com.ar
dns4.dokkogroup.com.ar
dns2.dokkogroup.com.ar
dns1.dokkogroup.com.ar

and is probably hosted by HEG-US - HEG US Inc., US. See the full list of other websites hosted by HEG-US - HEG US Inc., US.

The highest website muses.org position in Alexa rank database was 36781 and the lowest rank position was 999384. Current position of muses.org in Alexa rank database is 961606.

Desktop speed score of muses.org (57/100) is better than the results of 31.79% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of muses.org (94/100) is better than the results of 36.81% of other sites and means that the page is mobile-friendly.

Mobile speed score of muses.org (47/100) is better than the results of 28.68% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

muses.org 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.

muses.org 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.

muses.org server information

Servers Location

muses.org desktop page speed rank

Last tested: 2018-11-11

Desktop Speed Bad

57/100

muses.org Desktop Speed Test Quick Summary

priority - 52Enable 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 507KiB (71% reduction).

Compressing https://static.xx.fbcdn.net/rsrc.php/v3iEpO4/y6/l/en_US/s8WClR75CD2.js could save 356.8KiB (72% reduction).
Compressing https://connect.facebook.net/en_US/all.js?hash=785…50dfce54dbcddb9ae91e5e could save 122.1KiB (69% reduction).
Compressing https://staticxx.facebook.com/connect/xd_arbiter/r…z3h5RzMx.js?version=42 could save 26.5KiB (68% reduction).
Compressing https://connect.facebook.net/en_US/all.js could save 1.6KiB (48% reduction).

priority - 15Optimize images

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

Optimize the following images to reduce their size by 143.8KiB (53% reduction).

Compressing https://www.muses.org/images/en/+750M@2x.jpg could save 50.3KiB (72% reduction).
Compressing https://www.muses.org/images/en/+70K@2x.jpg could save 41.6KiB (71% reduction).
Compressing https://www.muses.org/images/en/supported@2x.jpg could save 11.2KiB (27% reduction).
Compressing https://www.muses.org/images/en/what-is.jpg could save 8.8KiB (59% reduction).
Compressing https://www.muses.org/images/en/download-now.jpg could save 7.9KiB (68% reduction).
Compressing https://www.muses.org/images/ads/internet-radio.png could save 5.9KiB (35% reduction).
Compressing https://www.muses.org/images/en/muses-numbers-2.png could save 4.8KiB (33% reduction).
Compressing https://www.muses.org/images/en/+60M@2x.jpg could save 4.4KiB (28% reduction).
Compressing https://www.muses.org/images/ads/browser-stack.png could save 2.8KiB (27% reduction).
Compressing https://www.muses.org/images/footer.jpg could save 2.5KiB (71% reduction).
Compressing https://images.sourceforge.net/images/project-support.jpg could save 2KiB (53% reduction).
Compressing https://hosted.muses.org/2.4.4/ffmp3-radiovoz/bg.png could save 775B (32% reduction).
Compressing https://widget.uservoice.com/dcache/widget/feedbac…Feedback&c=ffffff&r=90 could save 287B (19% reduction).
Compressing https://www.muses.org/images/up-arrow.png could save 144B (37% reduction).
Compressing https://www.muses.org/images/down-arrow.png could save 142B (36% reduction).
Compressing https://www.muses.org/images/news-pointer.png could save 138B (38% reduction).
Compressing https://www.muses.org/images/last-news-pointer.png could save 136B (24% reduction).
Compressing https://www.muses.org/images/flag-uk.png could save 105B (20% reduction).

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

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

Remove render-blocking JavaScript:

https://hosted.muses.org/mrp.js
https://hosted.muses.org/mrp.js

Optimize CSS Delivery of the following:

https://www.muses.org/styles/flexslider.css
https://www.muses.org/styles/common.css?2
https://www.muses.org/styles/cookieconsent.min.css

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://connect.facebook.net/en_US/all.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/184802…8329?v=2.8.33&r=stable (20 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://stats.g.doubleclick.net/dc.js (2 hours)
https://widget.uservoice.com/zmM7n2Ekns3L7jmpptrLKw.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 5.9KiB (38% reduction).

Minifying https://www.muses.org/js/jquery.flexslider.js could save 4.4KiB (39% reduction) after compression.
Minifying https://connect.facebook.net/en_US/all.js could save 1.1KiB (33% reduction).
Minifying https://www.muses.org/js/jquery.mousewheel.js could save 404B (43% reduction) after compression.

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.1KiB (20% reduction).

Minifying https://www.muses.org/styles/common.css?2 could save 606B (17% reduction) after compression.
Minifying https://www.muses.org/styles/flexslider.css could save 342B (24% reduction) after compression.
Minifying https://www.muses.org/styles/jquery.jscrollpane.css could save 179B (28% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 956B (13% reduction).

Minifying https://www.muses.org/ could save 956B (13% reduction) after compression.

muses.org Desktop Resource Breakdown

Total Resources	103
Number of Hosts	28
Static Resources	66
JavaScript Resources	33
CSS Resources	4

muses.org mobile page speed rank

Last tested: 2018-11-11

Mobile Speed Bad

47/100

muses.org Mobile Speed Test Quick Summary

priority - 52Enable 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 507KiB (71% reduction).

Compressing https://static.xx.fbcdn.net/rsrc.php/v3iEpO4/y6/l/en_US/s8WClR75CD2.js could save 356.8KiB (72% reduction).
Compressing https://connect.facebook.net/en_US/all.js?hash=77f…7c738d95d9f8384145992b could save 122.1KiB (69% reduction).
Compressing https://staticxx.facebook.com/connect/xd_arbiter/r…z3h5RzMx.js?version=42 could save 26.5KiB (68% reduction).
Compressing https://connect.facebook.net/en_US/all.js could save 1.6KiB (48% reduction).

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

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

Remove render-blocking JavaScript:

https://hosted.muses.org/mrp.js
https://hosted.muses.org/mrp.js
https://www.muses.org/js/jquery.min.js
https://www.muses.org/js/jquery.flexslider.js
https://www.muses.org/js/jquery.mousewheel.js
https://www.muses.org/js/jquery.jscrollpane.min.js
https://www.muses.org/js/cookieconsent.min.js

Optimize CSS Delivery of the following:

https://www.muses.org/styles/flexslider.css
https://www.muses.org/styles/common.css?2
https://www.muses.org/styles/cookieconsent.min.css
https://www.muses.org/styles/jquery.jscrollpane.css

priority - 15Optimize images

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

Optimize the following images to reduce their size by 146.1KiB (53% reduction).

Compressing https://www.muses.org/images/en/+750M@2x.jpg could save 50.3KiB (72% reduction).
Compressing https://www.muses.org/images/en/+70K@2x.jpg could save 41.6KiB (71% reduction).
Compressing https://www.muses.org/images/en/supported@2x.jpg could save 11.2KiB (27% reduction).
Compressing https://www.muses.org/images/en/what-is.jpg could save 8.8KiB (59% reduction).
Compressing https://www.muses.org/images/en/download-now.jpg could save 7.9KiB (68% reduction).
Compressing https://www.muses.org/images/ads/internet-radio.png could save 5.9KiB (35% reduction).
Compressing https://www.muses.org/images/en/muses-numbers-2.png could save 4.8KiB (33% reduction).
Compressing https://www.muses.org/images/en/+60M@2x.jpg could save 4.4KiB (28% reduction).
Compressing https://www.muses.org/images/ads/browser-stack.png could save 2.8KiB (27% reduction).
Compressing https://images.sourceforge.net/images/project-support.jpg could save 2KiB (53% reduction).
Compressing https://hosted.muses.org/2.4.4/ffmp3-darkconsole/bg.jpg could save 1.9KiB (46% reduction).
Compressing https://lh3.googleusercontent.com/7eC9ElRXP2D0y6GJ…6-n-rw-rj-sc0x00ffffff could save 1.7KiB (43% reduction).
Compressing https://lh3.googleusercontent.com/T-dIe4RzWKBZOe2O…1-n-rw-rj-sc0x00ffffff could save 823B (37% reduction).
Compressing https://hosted.muses.org/2.4.4/ffmp3-darkconsole/playclick.jpg could save 488B (50% reduction).
Compressing https://hosted.muses.org/2.4.4/ffmp3-darkconsole/stopclick.jpg could save 466B (50% reduction).
Compressing https://widget.uservoice.com/dcache/widget/feedbac…Feedback&c=ffffff&r=90 could save 287B (19% reduction).
Compressing https://hosted.muses.org/2.4.4/ffmp3-darkconsole/stop.jpg could save 245B (36% reduction).
Compressing https://hosted.muses.org/2.4.4/ffmp3-darkconsole/play.jpg could save 213B (35% reduction).
Compressing https://www.muses.org/images/news-pointer.png could save 138B (38% reduction).
Compressing https://www.muses.org/images/last-news-pointer.png could save 136B (24% reduction).
Compressing https://www.muses.org/images/flag-uk.png could save 105B (20% reduction).

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.

Only about 56% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the HTML response:

priority - 6Leverage 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://connect.facebook.net/en_US/all.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/184802…8329?v=2.8.33&r=stable (20 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
https://www.googletagservices.com/activeview/js/cu…ner.js?cache=r20110914 (50 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://stats.g.doubleclick.net/dc.js (2 hours)
https://widget.uservoice.com/zmM7n2Ekns3L7jmpptrLKw.js (2 hours)

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 5.9KiB (38% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.1KiB (20% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 958B (13% reduction).

Minifying https://www.muses.org/ could save 958B (13% reduction) after compression.

muses.org Mobile Resource Breakdown

Total Resources	98
Number of Hosts	23
Static Resources	70
JavaScript Resources	36
CSS Resources	5

muses.org mobile page usability

Last tested: 2018-11-11

Mobile Usability Good

94/100

muses.org Mobile Usability Test Quick Summary

priority - 5Size 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 href="https://en.wik…ki/HTTP_cookie" class="cc-link">Learn more</a> is close to 1 other tap targets.

The tap target <div></div> and 1 others are close to other tap targets.

The tap target <div class="rhstoreicon"></div> is close to 2 other tap targets.

The tap target <span class="rhpromotext rhdefaultcolored">12 Best Entertainment App</span> is close to 1 other tap targets.

The tap target <span class="rhbody rhdefaultcolored">Free Podcast A…listening now.</span> is close to 3 other tap targets.

The tap target <a href="https://www.muses.org/">Home</a> and 12 others are close to other tap targets.

The tap target <ins class="ee"></ins> is close to 5 other tap targets.

The tap target <ins class="ee"></ins> and 1 others are close to other tap targets.

The tap target <a href="https://google…/goldmine-demo" class="rhtitle rhdefaultcolored">Powerful CRM</a> is close to 3 other tap targets.

The tap target <span class="rhbody">Simple Affordable Proven</span> is close to 2 other tap targets.

The tap target <a href="https://google…/goldmine-demo" class="rhurl rhdefaultcolored">info.goldmine.com</a> is close to 1 other tap targets.

The tap target <div id="abgc" class="abgc"></div> is close to 5 other tap targets.

The tap target <div id="abgc" class="abgc"></div> is close to 4 other tap targets.

muses.org HTML validation

Errors

Obsolete doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 109
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <htm..."

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

Line: 12 Column: 2 - 51
"....ico" /> <meta http-equiv="content-language" content="en"/> <met..."

Attribute “keywords” not allowed on element “meta” at this point.

Element “meta” is missing one or more of the following attributes: “charset”, “content”, “http-equiv”, “itemprop”, “name”, “property”.

Line: 15 Column: 2 - 261
"...o.png"/> <meta keywords="ffmp3, muses, muses radio player, html5 radio player, javascript radio player, flash radio player, radio player, icecast, shoutcast, free radio player, mp3 radio player, ogg radio player, aac radio player, mp3 player, ogg player, aac player" /> <met..." Line: 16 Column: 2 - 115
"...ayer" /> <meta description="Muses Radio Player: The best MP3/OGG/AAC Radio Player for Icecast and Shoutcast. It's free!" /> <..."

Attribute “description” not allowed on element “meta” at this point.

Line: 16 Column: 2 - 115
"...ayer" /> <meta description="Muses Radio Player: The best MP3/OGG/AAC Radio Player for Icecast and Shoutcast. It's free!" /> <..."

Bad start tag in “img” in “head”.

Line: 46 Column: 11 - 2
"...<noscript><img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1848020178548329&ev=PageView&noscript=1" /></nosc..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 46 Column: 11 - 2
"...<noscript><img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1848020178548329&ev=PageView&noscript=1" /></nosc..." Line: 79 Column: 2 - 32
"...eader" > <img src="images/flag-uk.png"/> <a h..." Line: 80 Column: 16 - 46
"...ref="es/"><img src="images/flag-es.png"/></a> <..." Line: 96 Column: 47 - 99
"...esPlayer"><img style="border:none;" src="images/twitter.png" /></a> ..." Line: 131 Column: 2 - 32
"...emenu" > <img src="images/flag-uk.png"/> <a h..." Line: 132 Column: 16 - 46
"...ref="es/"><img src="images/flag-es.png"/></a> <..." Line: 148 Column: 47 - 99
"...esPlayer"><img style="border:none;" src="images/twitter.png" /></a> ..." Line: 521 Column: 5 - 64
"...ne;"> <img src="images/en/download-now.jpg" style="border:none;"/> <..." Line: 532 Column: 5 - 64
"...ne;"> <img src="images/en/download-now.jpg" style="border:none;"/> <..." Line: 543 Column: 3 - 36
"...obile"> <img src="images/en/what-is.jpg"/> <di..." Line: 555 Column: 71 - 109
"...nofollow"><img src="images/ads/reliastream.gif"/></a> <..." Line: 557 Column: 73 - 114
"...nofollow"><img src="images/ads/internet-radio.png"/></a> <..." Line: 559 Column: 71 - 111
"...nofollow"><img src="images/ads/browser-stack.png"/></a> <..." Line: 605 Column: 47 - 99
"...esPlayer"><img style="border:none;" src="images/twitter.png" /></a> ..."

Stray end tag “noscript”.

Line: 46 Column: 3 - 13
"...ript=1" /></noscript> <!-- ..."

Stray end tag “head”.

Line: 50 Column: 3 - 9
"...e --> </head> <bo..."

Start tag “body” seen but an element of the same type was already open.

Line: 51 Column: 3 - 8
"...</head> <body> ..."

Duplicate ID “cerrar-menu”.

Line: 105 Column: 5 - 49
"...span> <a class="menu-icon cerrar" id="cerrar-menu"></a> ..."

Bad value “88px” for attribute “width” on element “img”: Expected a digit but saw “p” instead.

Line: 611 Column: 70 - 205
"...d=271273"><img src="https://images.sourceforge.net/images/project-support.jpg" width="88px" height="32px" border="0" alt="Support This Project" /></a> ..."

Bad value “32px” for attribute “height” on element “img”: Expected a digit but saw “p” instead.

Line: 611 Column: 70 - 205
"...d=271273"><img src="https://images.sourceforge.net/images/project-support.jpg" width="88px" height="32px" border="0" alt="Support This Project" /></a> ..."

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

Line: 17 Column: 5 - 132
"...!" /> <meta name="viewport" content="width=device-width, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no, initial-scale=1.0" /> <s..."

The first occurrence of ID “cerrar-menu” was here.

Line: 104 Column: 5 - 27
"...enu"> <span id="cerrar-menu"></span..."

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 611 Column: 70 - 205
"...d=271273"><img src="https://images.sourceforge.net/images/project-support.jpg" width="88px" height="32px" border="0" alt="Support This Project" /></a> ..."

muses.org similar domains

Similar domains:

www.muses.com
www.muses.net
www.muses.org
www.muses.info
www.muses.biz
www.muses.us
www.muses.mobi
www.uses.org
www.muses.org
www.nuses.org
www.mnuses.org
www.nmuses.org
www.juses.org
www.mjuses.org
www.jmuses.org
www.kuses.org
www.mkuses.org
www.kmuses.org
www.mses.org
www.myses.org
www.muyses.org
www.myuses.org
www.mhses.org
www.muhses.org
www.mhuses.org
www.mjses.org
www.mujses.org
www.mises.org
www.muises.org
www.miuses.org
www.mues.org
www.muwes.org
www.muswes.org
www.muwses.org
www.muees.org
www.musees.org
www.mueses.org
www.mudes.org
www.musdes.org
www.mudses.org
www.muzes.org
www.muszes.org
www.muzses.org
www.muxes.org
www.musxes.org
www.muxses.org
www.muaes.org
www.musaes.org
www.muases.org
www.muss.org
www.musws.org
www.musews.org
www.musss.org
www.musess.org
www.musses.org
www.musds.org
www.museds.org
www.musrs.org
www.musers.org
www.musres.org
www.muse.org
www.musew.org
www.musesw.org
www.musee.org
www.musese.org
www.mused.org
www.musesd.org
www.musez.org
www.musesz.org
www.musezs.org
www.musesx.org
www.musea.org
www.musesa.org
www.museas.org

muses.org 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.

muses.org 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.

MUSES.ORG Muses Radio Player - The HTML5 MP3/OGG/AAC Live Stream Player!

muses.org Website Information

Advertisement

muses.org Alexa Rank

muses.org whois

muses.org server information

Servers Location

muses.org desktop page speed rank

muses.org Desktop Speed Test Quick Summary

priority - 52Enable 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 507KiB (71% reduction).

priority - 15Optimize images

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

Optimize the following images to reduce their size by 143.8KiB (53% reduction).

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

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:

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 5.9KiB (38% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.1KiB (20% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 956B (13% reduction).

muses.org Desktop Resource Breakdown

muses.org mobile page speed rank

muses.org Mobile Speed Test Quick Summary

priority - 52Enable 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 507KiB (71% reduction).

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 15Optimize images

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

Optimize the following images to reduce their size by 146.1KiB (53% reduction).

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.

priority - 6Leverage 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:

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 5.9KiB (38% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.1KiB (20% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 958B (13% reduction).

muses.org Mobile Resource Breakdown

muses.org mobile page usability

muses.org Mobile Usability Test Quick Summary

priority - 5Size 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.

muses.org HTML validation

Errors

Obsolete doctype. Expected “<!DOCTYPE html>”.

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

Attribute “keywords” not allowed on element “meta” at this point.

Element “meta” is missing one or more of the following attributes: “charset”, “content”, “http-equiv”, “itemprop”, “name”, “property”.

Attribute “description” not allowed on element “meta” at this point.

Bad start tag in “img” in “head”.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Stray end tag “noscript”.

Stray end tag “head”.

Start tag “body” seen but an element of the same type was already open.

Duplicate ID “cerrar-menu”.

Bad value “88px” for attribute “width” on element “img”: Expected a digit but saw “p” instead.

Bad value “32px” for attribute “height” on element “img”: Expected a digit but saw “p” instead.

Warnings