16.9 sec in total
4.5 sec
12.2 sec
252 ms
Visit music.dwango.jp now to see the best up-to-date Music Dwango content for Japan and also check out these interesting facts you probably never knew about music.dwango.jp
ドワンゴジェイピー(dwango.jp)
Visit music.dwango.jpWe analyzed Music.dwango.jp page load time and found that the first response time was 4.5 sec and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
music.dwango.jp performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value14.1 s
0/100
25%
Value14.5 s
1/100
10%
Value5,020 ms
0/100
30%
Value0.107
88/100
15%
Value18.2 s
3/100
10%
4490 ms
8 ms
585 ms
1310 ms
4 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Music.dwango.jp, 25% (39 requests) were made to Pc.dwango.jp and 13% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Pc.dwango.jp.
Page size can be reduced by 507.1 kB (16%)
3.2 MB
2.7 MB
In fact, the total size of Music.dwango.jp main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 80.3 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 80.3 kB or 84% of the original size.
Potential reduce by 80.2 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. Music Dwango images are well optimized though.
Potential reduce by 296.5 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 296.5 kB or 70% of the original size.
Potential reduce by 50.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. Music.dwango.jp needs all CSS files to be minified and compressed as it can save up to 50.2 kB or 79% of the original size.
Number of requests can be reduced by 33 (21%)
156
123
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Music Dwango. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
pc.dwango.jp
4490 ms
analytics.js
8 ms
application-7a4d1d94156097a9ae3159f80b906366.css
585 ms
application-e197c9705f7b7db772427df0b17f4bc6.js
1310 ms
collect
4 ms
collect
64 ms
image
562 ms
logo-79ae236c39fa88b49a9b06717ffe1282.png
166 ms
NEXCO_0213.jpg
783 ms
1x1-b8a8a4ea3d4dbaa249e869b59ae1407a.gif
178 ms
hashimoto_0223.jpg
619 ms
sonapoke_0224.jpg
746 ms
funky_0224.jpg
746 ms
ieiri_0217.jpg
524 ms
teshima_0210.jpg
372 ms
icon-ful-9ef6d58df9cd7f2673b43b94ccebf3b7.jpg
538 ms
bnr_sumo.png
1257 ms
ske48hatsunori_pc_sidebanner_250_70.png
767 ms
bnr_lovelock.jpg
900 ms
dwaiphone_logo.png
952 ms
dwango_logo.png
960 ms
call_logo.png
966 ms
android_bill_logo.png
963 ms
android_bill_logo_ios.png
1105 ms
kpop_logo.png
1167 ms
kisekae_logo.png
1184 ms
decome_logo.png
1144 ms
sumo_app.png
1184 ms
f_full_logo.png
1298 ms
f_uta_logo.png
1314 ms
f_toriho_logo.png
1387 ms
f_call_logo.png
1385 ms
f_billboard_logo.png
1398 ms
f_kpop_logo.png
1479 ms
f_decome_logo.png
1498 ms
f_voice_logo.png
1510 ms
f_kisekae_logo.png
1552 ms
f_sumo_logo.png
1610 ms
image
381 ms
image
554 ms
image
417 ms
image
562 ms
image
562 ms
image
740 ms
image
761 ms
image
953 ms
image
949 ms
image
971 ms
image
1137 ms
image
1296 ms
image
1297 ms
image
1316 ms
image
1315 ms
image
1317 ms
image
1771 ms
image
1841 ms
image
1895 ms
image
1867 ms
image
1904 ms
image
1719 ms
image
2307 ms
image
2163 ms
image
2424 ms
image
2242 ms
image
2426 ms
image
2426 ms
image
2715 ms
image
2766 ms
image
2859 ms
image
2943 ms
image
2969 ms
image
2974 ms
image
3300 ms
common_link_bg-85cabff8950eec8908c133ff8d5ab722.png
1489 ms
common_tab_bg-90c40d682a3b3d1b4c2ed0965f072aa7.png
1570 ms
icons-sa37a99883b-98ee36e20a47091594ad7591541905ff.png
1572 ms
widgets.js
23 ms
all.js
271 ms
bx_loader-3b3963f808340665792e3ce538452f97.gif
1526 ms
controls-1b6307f3417d93f53bd6b1709d223b26.png
1573 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
22 ms
syndication
92 ms
278112097747996673
395 ms
image
2948 ms
36 ms
image
2799 ms
xd_arbiter.php
232 ms
xd_arbiter.php
479 ms
image
2749 ms
image
2989 ms
image
2812 ms
image
3010 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
6 ms
cQAfOvG4_normal.png
110 ms
2dTeQiFl_normal.png
107 ms
JKMma28r_normal.jpeg
111 ms
tTugIAhT_normal.png
111 ms
CcOxDTfUcAAXmTb.jpg
111 ms
CcOUYg8UcAABrUM.jpg
115 ms
CcOREOiVIAA3e_8.jpg
115 ms
CcJcgMiUcAAaxUd.jpg
116 ms
CcJXncYUcAEWMdR.jpg:small
116 ms
CcIxnsaUcAAa1dA.jpg:small
118 ms
CcIDo6EVIAAg2_H.jpg:small
120 ms
CcHNMHoUYAAehop.jpg:small
122 ms
Cb-Y86SW0AAsqup.jpg
129 ms
Cb-u2AaUsAAlHeP.jpg:small
126 ms
Cb5Ah_LUUAAAO5B.png:small
143 ms
Cb3kn18VIAQ4PsA.jpg:small
142 ms
CbvYlfsUYAEg4Mx.jpg:small
122 ms
CbqtiSIUcAAbnkV.jpg:small
123 ms
image
3102 ms
image
3097 ms
image
2775 ms
image
2791 ms
image
2927 ms
jot
23 ms
image
2808 ms
image
2799 ms
image
3004 ms
image
3090 ms
image
2896 ms
image
2961 ms
image
2745 ms
image
2697 ms
image
2750 ms
image
2759 ms
xd_arbiter.php
138 ms
like_box.php
162 ms
siylcCr24Vv.css
289 ms
0q9EiyOzKa_.css
357 ms
YLIWaFzOgE1.css
429 ms
QpVb8YtVy_T.css
559 ms
OphU1GyEtJq.css
566 ms
_rx8naC75Dy.js
575 ms
x5F9OMjKyLw.js
627 ms
ICDbTSzjQEg.js
493 ms
TTCre3391I0.js
496 ms
njO1TPvGzoR.js
585 ms
b_6HNn_J2BZ.js
585 ms
7cm7D75Y0Sf.js
690 ms
rFmE1g6Dkoz.js
829 ms
336JejShbZp.js
648 ms
11892077_1019267588117438_5632040646541589334_n.png
346 ms
safe_image.php
357 ms
safe_image.php
442 ms
safe_image.php
510 ms
safe_image.php
556 ms
safe_image.php
560 ms
11891037_1019220081455522_6602413902606324731_n.png
406 ms
wL6VQj7Ab77.png
86 ms
s7jcwEQH7Sx.png
86 ms
QDwYpIaRyfG.png
86 ms
a-ZN6WoEOje.png
86 ms
I6-MnjEovm5.js
68 ms
vlXaquuXMrr.js
136 ms
music.dwango.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
music.dwango.jp 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
music.dwango.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Music.dwango.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 Music.dwango.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.
music.dwango.jp
Open Graph description is not detected on the main page of Music Dwango. 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: