Tools & Wizards About Us
mayusan.jp screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

mayusan.jp

VOCALOID™3 Library MAYU

Page Load Speed

5.3 sec in total

First Response

1 sec

Resources Loaded

4.1 sec

Page Rendered

129 ms

mayusan.jp screenshot

About Website

Welcome to mayusan.jp homepage info - get ready to check MAYU San best content right away, or after learning these important things about mayusan.jp

2012年12月5日、EXIT TUNES初のボカロVOCALOID™3 Library MAYU 遂にデビュー！！VOCALOID™3 Library＋総勢30名を超える参加アーティストのスペシャル2枚組みCD同梱！！『MAYU』のキャラクターデザイン＆イラストは「左」描き下ろし！！数量限定！全6種マウスパッド＆ストラップいずれか封入＆「cosMo＠暴走P」「DJ UTO」「Ryu☆」「ピノキオ...

Visit mayusan.jp

Key Findings

We analyzed Mayusan.jp page load time and found that the first response time was 1 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

mayusan.jp performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

mayusan.jp

1016 ms

jquery-1.8.2.min.js

1147 ms

jquery-ui-1.9.0.custom.min.js

825 ms

jquery.jplayer.min.js

842 ms

jplayer.playlist.min.js

527 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 67% of them (55 requests) were addressed to the original Mayusan.jp, 10% (8 requests) were made to Apis.google.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Mayusan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.0 kB (19%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mayusan.jp main page is 1.5 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 27.9 kB

  • Original 35.4 kB
  • After minification 30.0 kB
  • After compression 7.5 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 5.4 kB, which is 15% 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 27.9 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 64.0 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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

JavaScript Optimization

-66%

Potential reduce by 183.7 kB

  • Original 278.3 kB
  • After minification 261.3 kB
  • After compression 94.7 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 183.7 kB or 66% of the original size.

CSS Optimization

-78%

Potential reduce by 9.5 kB

  • Original 12.2 kB
  • After minification 9.1 kB
  • After compression 2.7 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. Mayusan.jp needs all CSS files to be minified and compressed as it can save up to 9.5 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (46%)

Requests Now

80

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mayusan.jp

mayusan.jp

1016 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

1147 ms

jquery-ui-1.9.0.custom.min.js

jquery-ui-1.9.0.custom.min.js

825 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

842 ms

jplayer.playlist.min.js

jplayer.playlist.min.js

527 ms

loader.js

loader.js

365 ms

scroll.js

scroll.js

721 ms

nikodou.js

nikodou.js

655 ms

main.js

main.js

702 ms

main.css

main.css

821 ms

bookmark_button.js

bookmark_button.js

365 ms

ga.js

ga.js

81 ms

widgets.js

widgets.js

127 ms

plusone.js

plusone.js

161 ms

button-only.gif

button-only.gif

199 ms

logo.png

logo.png

370 ms

mayu_shadow.png

mayu_shadow.png

196 ms

detail.png

detail.png

204 ms

amazon.png

amazon.png

188 ms

taiken.png

taiken.png

202 ms

important_panel.png

important_panel.png

195 ms

important.png

important.png

343 ms

japan_b.png

japan_b.png

345 ms

english_b.png

english_b.png

349 ms

english_manual.png

english_manual.png

377 ms

info.png

info.png

915 ms

rules.png

rules.png

441 ms

minimum_operation_b.png

minimum_operation_b.png

503 ms

inquiry.png

inquiry.png

506 ms

inquiry_url.png

inquiry_url.png

515 ms

important.png

important.png

552 ms

eta.jp.png

eta.jp.png

605 ms

t.png

t.png

667 ms

base.png

base.png

669 ms

1.png

1.png

1020 ms

2.png

2.png

1079 ms

dl.png

dl.png

771 ms

info.png

info.png

830 ms

top.png

top.png

831 ms

profile.png

profile.png

935 ms

special.png

special.png

997 ms

movie.png

movie.png

995 ms

presents.png

presents.png

1091 ms

contact.png

contact.png

1100 ms

sound_on.png

sound_on.png

1160 ms

copy.png

copy.png

1160 ms

loading-logo.png

loading-logo.png

1185 ms

loading.png

loading.png

1252 ms

demo_t.png

demo_t.png

1270 ms

demo_dl.png

demo_dl.png

1265 ms

text.png

text.png

1326 ms

__utm.gif

__utm.gif

29 ms

245 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

137 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

28 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

16 ms

fastbutton

fastbutton

69 ms

postmessageRelay

postmessageRelay

76 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

20 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

21 ms

transparent.gif

transparent.gif

1145 ms

usanomimi.png

usanomimi.png

1336 ms

demo_t.png

demo_t.png

1239 ms

mayu.png

mayu.png

1750 ms

sound_off.png

sound_off.png

1255 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

22 ms

rpc:shindig_random.js

rpc:shindig_random.js

48 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

44 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

reset.css

reset.css

14 ms

entry-button.css

entry-button.css

15 ms

download.png

download.png

1206 ms

button-counter.gif

button-counter.gif

5 ms

download_on.png

download_on.png

1156 ms

like.php

like.php

371 ms

panel.png

panel.png

1979 ms

taiken_on.png

taiken_on.png

1288 ms

jot

jot

79 ms

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

19 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

549 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

615 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

202 ms

Accessibility Review

mayusan.jp accessibility score

65

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

mayusan.jp 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

mayusan.jp SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Mayusan.jp 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 Mayusan.jp 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

mayusan.jp

Open Graph data is detected on the main page of MAYU San. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: