4.2 sec in total
81 ms
3.2 sec
964 ms
Welcome to mus.io homepage info - get ready to check Mus best content right away, or after learning these important things about mus.io
Get endless inspiration with Musio: an always-growing catalog of instruments by Cinesamples in a sleek, modern sampler.
Visit mus.ioWe analyzed Mus.io page load time and found that the first response time was 81 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mus.io performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value20.4 s
0/100
25%
Value19.1 s
0/100
10%
Value7,210 ms
0/100
30%
Value0
100/100
15%
Value35.0 s
0/100
10%
81 ms
160 ms
156 ms
432 ms
168 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mus.io, 80% (126 requests) were made to Musio.com and 4% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (922 ms) relates to the external source Musio.com.
Page size can be reduced by 255.9 kB (9%)
3.0 MB
2.7 MB
In fact, the total size of Mus.io main page is 3.0 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. Only a small number of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 201.6 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. 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 201.6 kB or 83% of the original size.
Potential reduce by 22.5 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. Mus images are well optimized though.
Potential reduce by 12.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. This website has mostly compressed JavaScripts.
Potential reduce by 19.2 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. Mus.io has all CSS files already compressed.
Number of requests can be reduced by 110 (76%)
145
35
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 75 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.
mus.io
81 ms
www.musio.com
160 ms
musio.com
156 ms
musio.com
432 ms
sonaar-music-public.css
168 ms
basic.min.css
190 ms
theme-ie11.min.css
194 ms
theme.min.css
195 ms
dashicons.min.css
285 ms
custom-frontend-lite.min.css
248 ms
general.min.css
256 ms
eael-7618.css
255 ms
styles.css
256 ms
secondline-psb-styles.css
258 ms
secondline-audio.css
312 ms
sonaar-music-pro-public.css
331 ms
style.css
405 ms
style.css
319 ms
mediaelementplayer-legacy.min.css
327 ms
wp-mediaelement.min.css
346 ms
style.css
374 ms
css
41 ms
fontawesome.min.css
391 ms
Genericons-Neue.min.css
415 ms
secondline_themes_custom_styles.css
395 ms
frontend.min.css
411 ms
swiper.min.css
434 ms
post-1000.css
450 ms
custom-pro-frontend-lite.min.css
451 ms
post-11226.css
460 ms
castos-player.min.css
473 ms
subscribe-buttons.css
468 ms
post-3715.css
496 ms
post-7618.css
511 ms
default.css
514 ms
front.min.css
522 ms
ytprefs.min.css
532 ms
lity.min.css
536 ms
jquery.min.js
590 ms
api.js
50 ms
js
77 ms
rw.js
25 ms
custom-pro-widget-nav-menu.min.css
511 ms
rs6.css
444 ms
jquery-migrate.min.js
408 ms
jquery.json.min.js
427 ms
gravityforms.min.js
468 ms
utils.min.js
472 ms
moxie.min.js
431 ms
plupload.min.js
417 ms
conditional_logic.min.js
413 ms
front.min.js
413 ms
lity.min.js
471 ms
ytprefs.min.js
453 ms
sonaar-music-pro-public.js
419 ms
list.min.js
421 ms
perfect-scrollbar.min.js
413 ms
wp-polyfill-inert.min.js
570 ms
regenerator-runtime.min.js
542 ms
wp-polyfill.min.js
568 ms
dom-ready.min.js
519 ms
hooks.min.js
501 ms
i18n.min.js
499 ms
a11y.min.js
549 ms
vendor-theme.min.js
524 ms
scripts-theme.min.js
508 ms
placeholders.jquery.min.js
508 ms
general.min.js
498 ms
index.js
551 ms
index.js
527 ms
modal.min.js
512 ms
rbtools.min.js
607 ms
rs6.min.js
627 ms
mediaelement-and-player.min.js
646 ms
mediaelement-migrate.min.js
548 ms
wp-mediaelement.min.js
518 ms
vendors.min.js
618 ms
secondline-script.js
599 ms
castos-player.min.js
598 ms
vue-multiselect.min.js
599 ms
vue.min.js
798 ms
vue-slider-component.min.js
839 ms
fitvids.min.js
834 ms
sonaar-music-public.js
897 ms
00.moments.min.js
895 ms
00.wavesurfer.min.js
809 ms
core.min.js
845 ms
mouse.min.js
847 ms
slider.min.js
843 ms
w.js
225 ms
fbevents.js
222 ms
iron-audioplayer.js
832 ms
913035672
410 ms
pDckeGxoJJ8
349 ms
913036093
317 ms
913036255
342 ms
913045794
431 ms
draggable.min.js
734 ms
sonaarPlayer.js
669 ms
premium-wrapper-link.min.js
668 ms
jquery.smartmenus.min.js
676 ms
webpack-pro.runtime.min.js
675 ms
webpack.runtime.min.js
678 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
129 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
135 ms
frontend-modules.min.js
678 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf
130 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf
133 ms
frontend.min.js
632 ms
waypoints.min.js
633 ms
frontend.min.js
635 ms
elements-handlers.min.js
635 ms
sr-scripts.js
635 ms
jquery.sticky.min.js
771 ms
underscore.min.js
707 ms
wp-util.min.js
710 ms
frontend.min.js
704 ms
Inter-Regular.ttf
922 ms
settings.luckyorange.net
19 ms
Inter-Bold.ttf
715 ms
musio-a1-1000-x-1000.png
709 ms
Musio-Hero-Banner-Background-Fix-1-scaled.jpg
664 ms
www-player.css
12 ms
www-embed-player.js
99 ms
base.js
127 ms
Hero-foreground.webp
655 ms
Banner-1-Cam-2.jpg
610 ms
tiles_musio.jpg
866 ms
douchebag-in-the-studio.jpg
744 ms
Group-41.webp
724 ms
Group-42.webp
709 ms
ad_status.js
337 ms
Group-40.webp
475 ms
Catalog-4-Web-Hi-Res-Fixed.png
733 ms
Group-37.webp
401 ms
Group-39.webp
400 ms
Group-38.webp
392 ms
Artist-Poster-Gradient.webp
505 ms
Group-24.webp
502 ms
Group-25.webp
499 ms
Group-26.webp
499 ms
Group-27.webp
499 ms
Group-28.webp
652 ms
Producer-2.jpg
646 ms
musio_carrot.webp
497 ms
full_grain.webp
816 ms
widescreen_grain_overlay2.png
642 ms
Hg8RJ6IYDEt2XfeS9TTatHSj5NgA1bkUUg8jx44YVvw.js
140 ms
embed.js
86 ms
HcULVMhZuSZKY55vJ6f6Js9aOumron9Ypbbq2s4cko6Wd6Q3QRA7mWq0-nyO80PikIZQV8cjkg=s68-c-k-c0x00ffffff-no-rj
231 ms
recaptcha__en.js
219 ms
clickstream.legacy.js
203 ms
id
148 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
137 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
138 ms
Create
152 ms
GenerateIT
16 ms
mus.io accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
mus.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
mus.io SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mus.io 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 Mus.io 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.
mus.io
Open Graph data is detected on the main page of Mus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: