5.6 sec in total
1.2 sec
4.2 sec
308 ms
Welcome to dragonash.co.jp homepage info - get ready to check Dragon Ash best content for Japan right away, or after learning these important things about dragonash.co.jp
Dragon Ash Official Website 最新NEWSやライブ情報など
Visit dragonash.co.jpWe analyzed Dragonash.co.jp page load time and found that the first response time was 1.2 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
dragonash.co.jp performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value23.5 s
0/100
25%
Value17.7 s
0/100
10%
Value1,290 ms
18/100
30%
Value0
100/100
15%
Value31.8 s
0/100
10%
1156 ms
418 ms
636 ms
427 ms
23 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 34% of them (31 requests) were addressed to the original Dragonash.co.jp, 23% (21 requests) were made to Static.xx.fbcdn.net and 9% (8 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Dragonash.co.jp.
Page size can be reduced by 105.3 kB (10%)
1.1 MB
961.5 kB
In fact, the total size of Dragonash.co.jp main page is 1.1 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. 50% of websites need less resources to load. Images take 925.7 kB which makes up the majority of the site volume.
Potential reduce by 21.2 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 21.2 kB or 75% of the original size.
Potential reduce by 27.9 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. Dragon Ash images are well optimized though.
Potential reduce by 31.4 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 31.4 kB or 38% of the original size.
Potential reduce by 24.8 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. Dragonash.co.jp needs all CSS files to be minified and compressed as it can save up to 24.8 kB or 82% of the original size.
Number of requests can be reduced by 30 (34%)
89
59
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dragon Ash. 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 12 to 1 for CSS and as a result speed up the page load time.
dragonash.co.jp
1156 ms
cssreset-min.css
418 ms
jquery.bxslider.css
636 ms
jquery.jscrollpane.css
427 ms
css
23 ms
common.css
1055 ms
logo.png
856 ms
fb.png
421 ms
tw.png
419 ms
yt.png
434 ms
cart.png
626 ms
20160210_top.jpg
1683 ms
s_retargeting.js
734 ms
conversion.js
19 ms
jquery.min.js
33 ms
all.min.js
1279 ms
all.js
268 ms
news.jpg
854 ms
live-schedule.jpg
1078 ms
media-schedule.jpg
430 ms
profile.jpg
688 ms
bio.jpg
864 ms
disco.jpg
1054 ms
link.jpg
1055 ms
private.jpg
1036 ms
photo.jpg
1278 ms
movie.jpg
1293 ms
blog.jpg
1248 ms
ticket.jpg
1477 ms
store.jpg
1476 ms
fanclub.jpg
1494 ms
innovator.png
1460 ms
aog.png
1492 ms
mob.png
1507 ms
widgets.js
5 ms
nHiQo1BypvYzt95zlPq1TnYhjbSpvc47ee6xR_80Hnw.ttf
30 ms
ga.js
36 ms
__utm.gif
33 ms
48 ms
34 ms
52 ms
xd_arbiter.php
217 ms
xd_arbiter.php
424 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
52 ms
bx_loader.gif
988 ms
20160210_top.jpg
1680 ms
syndication
97 ms
373358685193383937
973 ms
like_box.php
235 ms
siylcCr24Vv.css
288 ms
0q9EiyOzKa_.css
356 ms
YLIWaFzOgE1.css
425 ms
OphU1GyEtJq.css
556 ms
QpVb8YtVy_T.css
566 ms
_rx8naC75Dy.js
625 ms
x5F9OMjKyLw.js
625 ms
ICDbTSzjQEg.js
491 ms
TTCre3391I0.js
491 ms
njO1TPvGzoR.js
573 ms
b_6HNn_J2BZ.js
573 ms
7cm7D75Y0Sf.js
688 ms
rFmE1g6Dkoz.js
848 ms
336JejShbZp.js
655 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
5 ms
IMG_0248_normal.jpg
118 ms
XaGWnbha_normal.jpeg
215 ms
mAHwLhn0_normal.png
232 ms
PSbTJtN-_normal.png
262 ms
_____normal.jpg
230 ms
_____5_normal.png
230 ms
d654589c38c418f44dbdf717832e90e6_normal.jpeg
231 ms
12688157_751875351511370_6552320292250877352_n.jpg
139 ms
safe_image.php
135 ms
10475675_572033249495582_2523908078050608443_n.jpg
136 ms
12799373_138895553166556_1083223821416630822_n.jpg
252 ms
12651350_115653988820042_1123028049318020974_n.jpg
156 ms
12366457_198509450491421_4885995724568946562_n.jpg
166 ms
12310645_662714700535124_299462054239913188_n.jpg
253 ms
12744542_174698522905930_6489495327501362383_n.jpg
206 ms
11021097_10205220455305072_3837380546271259105_n.jpg
139 ms
safe_image.php
150 ms
safe_image.php
137 ms
safe_image.php
139 ms
HEyyDkPknAC.png
172 ms
wL6VQj7Ab77.png
168 ms
s7jcwEQH7Sx.png
171 ms
QDwYpIaRyfG.png
171 ms
a-ZN6WoEOje.png
173 ms
I6-MnjEovm5.js
68 ms
vlXaquuXMrr.js
135 ms
jot
37 ms
dragonash.co.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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
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.
dragonash.co.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
dragonash.co.jp 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
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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dragonash.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Dragonash.co.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.
dragonash.co.jp
Open Graph description is not detected on the main page of Dragon Ash. 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: