8.1 sec in total
840 ms
6.6 sec
639 ms
Visit muty.jp now to see the best up-to-date Muty content and also check out these interesting facts you probably never knew about muty.jp
このページはチャップアップはどこで買える?やロフトや薬局で市販されているのは本当?、楽天やアマゾンで買うと高くなる?について記したサイトです
Visit muty.jpWe analyzed Muty.jp page load time and found that the first response time was 840 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
muty.jp performance score
840 ms
383 ms
360 ms
6 ms
556 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 38% of them (44 requests) were addressed to the original Muty.jp, 21% (24 requests) were made to O.twimg.com and 10% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Muty.jp.
Page size can be reduced by 316.7 kB (6%)
4.9 MB
4.6 MB
In fact, the total size of Muty.jp main page is 4.9 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 4.8 MB which makes up the majority of the site volume.
Potential reduce by 19.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. 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 19.5 kB or 71% of the original size.
Potential reduce by 239.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. Muty images are well optimized though.
Potential reduce by 14.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 14.6 kB or 35% of the original size.
Potential reduce by 43.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. Muty.jp needs all CSS files to be minified and compressed as it can save up to 43.2 kB or 82% of the original size.
Number of requests can be reduced by 38 (33%)
115
77
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Muty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
muty.jp
840 ms
base.css
383 ms
bgstretcher.css
360 ms
jquery.min.js
6 ms
jquery.bxslider.min.js
556 ms
jquery.bxslider.css
378 ms
fb.js
391 ms
bxslider.js
401 ms
muty.jp
1155 ms
ga.js
743 ms
style.css
380 ms
sub.css
385 ms
menu.css
389 ms
form.css
521 ms
slide.css
733 ms
fp.js
42 ms
banar.gif
530 ms
8831_ban.gif
708 ms
bg_page.png
1234 ms
logo.png
200 ms
hl_btn_login.gif
348 ms
hl_btn_regist.gif
370 ms
fbLoginSmall.png
405 ms
img_main.jpg
1378 ms
img_main03.jpg
1651 ms
04-2.jpg
892 ms
04-1.jpg
928 ms
img_about_thumb.jpg
927 ms
btn_free_entry.png
1270 ms
btn_about.png
1459 ms
lesson01.jpg
1851 ms
lesson02.jpg
2313 ms
lesson01.jpg
2419 ms
motomatsu.png
3679 ms
yanamoto.jpeg
1834 ms
yamashitashihori.jpeg
3085 ms
kobayashiyukie.jpeg
2540 ms
daichihayakawa.jpeg
4153 ms
yurisugiyama.jpeg
3555 ms
piano.jpg
3304 ms
camera.png
3206 ms
arm.jpg
3837 ms
all.js
115 ms
gmenu_new_home.png
3561 ms
gmenu_new_about.png
3632 ms
gmenu_new_p_s.png
3896 ms
gmenu_new_service.png
3936 ms
gmenu_new_instructor.png
3974 ms
widgets.js
119 ms
icon_h3title.png
3987 ms
offsite_event.php
52 ms
analytics.js
25 ms
linkid.js
6 ms
collect
46 ms
44 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
135 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
164 ms
xd_arbiter.php
67 ms
xd_arbiter.php
129 ms
syndication
97 ms
447541262074146817
274 ms
tweet_button.64a917b4a230f163048902c783e1530f.ja.html
41 ms
proxy.jpg
132 ms
proxy.jpg
124 ms
proxy.jpg
126 ms
proxy.jpg
123 ms
proxy.jpg
125 ms
proxy.jpg
122 ms
proxy.jpg
161 ms
proxy.jpg
224 ms
proxy.jpg
165 ms
proxy.jpg
156 ms
proxy.jpg
157 ms
proxy.jpg
265 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
27 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
118 ms
a5261ac3c3787ca4a4185246e9231012_normal.jpeg
221 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
19 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
74 ms
proxy.jpg
43 ms
proxy.jpg
44 ms
proxy.jpg
52 ms
proxy.jpg
35 ms
proxy.jpg
43 ms
proxy.jpg
44 ms
proxy.jpg
54 ms
proxy.jpg
320 ms
proxy.jpg
47 ms
proxy.jpg
54 ms
proxy.jpg
29 ms
proxy.jpg
125 ms
jot.html
32 ms
xd_arbiter.php
39 ms
like.php
62 ms
like_box.php
105 ms
ZJkxn0orVLU.js
138 ms
LVx-xkvaJ0b.png
117 ms
uEAXZbor9uc.css
64 ms
8LzBk4kQhcr.css
60 ms
XCdv7aD40Gm.js
92 ms
5frqWlpFEeI.js
118 ms
mn6tHWuLI-Y.js
73 ms
x8BMxYCqTb9.js
83 ms
1381918_547605685307833_1039219700_n.jpg
123 ms
25939_544804355587966_2145467422_n.jpg
106 ms
10380960_760223414010366_4492559195080851556_n.jpg
86 ms
11781864_991705397517607_131054699742395109_n.jpg
85 ms
10406772_858670087520404_3629763494719490718_n.jpg
84 ms
12494962_929492677086556_1368360386765429054_n.jpg
110 ms
11750606_1444412352552946_5273288793212789017_n.jpg
105 ms
11217571_1161181430575600_6345118515504191299_n.jpg
104 ms
12688122_880068098757576_4341002153542558129_n.jpg
134 ms
wL6VQj7Ab77.png
20 ms
s7jcwEQH7Sx.png
24 ms
VXcANLwwL5J.js
21 ms
50Trs1RKgUY.js
21 ms
muty.jp SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Muty.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 Muty.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.
muty.jp
Open Graph description is not detected on the main page of Muty. 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: