Tools & Wizards About Us
mu-mo.net screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

mu-mo.net

mu-mo（ミュゥモ）｜音楽ダウンロードならmu-mo！

Page Load Speed

5.9 sec in total

First Response

1 sec

Resources Loaded

4.7 sec

Page Rendered

220 ms

mu-mo.net screenshot

About Website

Welcome to mu-mo.net homepage info - get ready to check Mu Mo best content for Japan right away, or after learning these important things about mu-mo.net

ビルボードジャパンチャートに反映！最新ヒット曲から懐かしの名曲まで充実のラインナップ！気になる楽曲をダウンロードできる音楽配信サイトです。

Visit mu-mo.net

Key Findings

We analyzed Mu-mo.net page load time and found that the first response time was 1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

mu-mo.net performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.284

42/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

sp-m.mu-mo.net

1003 ms

mumo-icon.min.css

198 ms

mumo_base.min.css

398 ms

mumo_haishin.min.css

861 ms

mumo_custom.css

522 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mu-mo.net, 5% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Sp-m.mu-mo.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 470.0 kB (40%)

Content Size

1.2 MB

After Optimization

707.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mu-mo.net main page is 1.2 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. 60% of websites need less resources to load. Images take 552.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 28.9 kB

  • Original 35.9 kB
  • After minification 31.8 kB
  • After compression 7.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 4.1 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 28.9 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 30.2 kB

  • Original 552.4 kB
  • After minification 522.3 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. Mu Mo images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 256.2 kB

  • Original 395.0 kB
  • After minification 379.8 kB
  • After compression 138.8 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 256.2 kB or 65% of the original size.

CSS Optimization

-80%

Potential reduce by 154.7 kB

  • Original 193.8 kB
  • After minification 191.7 kB
  • After compression 39.1 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. Mu-mo.net needs all CSS files to be minified and compressed as it can save up to 154.7 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (41%)

Requests Now

59

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sp-m.mu-mo.net

sp-m.mu-mo.net

1003 ms

mumo-icon.min.css

mumo-icon.min.css

198 ms

mumo_base.min.css

mumo_base.min.css

398 ms

mumo_haishin.min.css

mumo_haishin.min.css

861 ms

mumo_custom.css

mumo_custom.css

522 ms

jquery-ui-1.8.24.custom.css

jquery-ui-1.8.24.custom.css

700 ms

mumo_haishin_top.min.css

mumo_haishin_top.min.css

529 ms

swiper.min.css

swiper.min.css

699 ms

mumo_haishin_top.min.css

mumo_haishin_top.min.css

598 ms

jquery.js

jquery.js

1072 ms

jquery-ui.custom.min.js

jquery-ui.custom.min.js

945 ms

jquery.blockUI.js

jquery.blockUI.js

803 ms

jquery.gpobservetext.min.js

jquery.gpobservetext.min.js

946 ms

bases.js

bases.js

946 ms

common.js

common.js

1003 ms

muca.js

muca.js

1079 ms

libs.min.js

libs.min.js

1154 ms

mumo_haishin_ui.min.js

mumo_haishin_ui.min.js

1155 ms

globalmenu.js

globalmenu.js

1155 ms

swiper.min.js

swiper.min.js

1535 ms

1_13814354.jpg

1_13814354.jpg

367 ms

1_ANTCD-A0000013360.jpg

1_ANTCD-A0000013360.jpg

368 ms

1_VE3WT-10968.jpg

1_VE3WT-10968.jpg

407 ms

1_13819248.jpg

1_13819248.jpg

420 ms

1_13817102.jpg

1_13817102.jpg

417 ms

1_13819244.jpg

1_13819244.jpg

545 ms

1_ANTCD-55483.jpg

1_ANTCD-55483.jpg

555 ms

1_VE3WT-10947.jpg

1_VE3WT-10947.jpg

595 ms

1_13811310.jpg

1_13811310.jpg

593 ms

1_13810493.jpg

1_13810493.jpg

604 ms

1_13815671.jpg

1_13815671.jpg

723 ms

1_13809941.jpg

1_13809941.jpg

739 ms

1_ANTCD-A0000012963.jpg

1_ANTCD-A0000012963.jpg

775 ms

1_13814272.jpg

1_13814272.jpg

770 ms

1_13815654.jpg

1_13815654.jpg

782 ms

1_ANTCD-A0000013360.jpg

1_ANTCD-A0000013360.jpg

2076 ms

1_13786488.jpg

1_13786488.jpg

905 ms

1_ANTCD-A0000012829.jpg

1_ANTCD-A0000012829.jpg

2794 ms

1_13819248.jpg

1_13819248.jpg

949 ms

1_13796681.jpg

1_13796681.jpg

1277 ms

1_13793395.jpg

1_13793395.jpg

1386 ms

1_ANTCD-A0000013280.jpg

1_ANTCD-A0000013280.jpg

1998 ms

smp_top_bn_201201mu-moshop.jpg

smp_top_bn_201201mu-moshop.jpg

1324 ms

lmark.png

lmark.png

1493 ms

cdshop_out_S.png

cdshop_out_S.png

1694 ms

gtm.js

gtm.js

76 ms

sitename_pc.png

sitename_pc.png

1568 ms

mumo-icon-regular.woff

mumo-icon-regular.woff

1620 ms

Montserrat-Regular.ttf

Montserrat-Regular.ttf

1711 ms

js

js

83 ms

analytics.js

analytics.js

36 ms

uwt.js

uwt.js

20 ms

fbevents.js

fbevents.js

32 ms

bi.js

bi.js

930 ms

linkid.js

linkid.js

34 ms

collect

collect

20 ms

adsct

adsct

171 ms

adsct

adsct

150 ms

1208 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

1190 ms

Accessibility Review

mu-mo.net accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

mu-mo.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

mu-mo.net SEO score

90

Search Engine Optimization Advices

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mu-mo.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mu-mo.net 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

mu-mo.net

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