20.2 sec in total
1.7 sec
17.8 sec
589 ms
Click here to check amazing Carddass content for Japan. Otherwise, check out these important facts you probably never knew about carddass.com
カードダス公式サイト カードダスドットコム
Visit carddass.comWe analyzed Carddass.com page load time and found that the first response time was 1.7 sec and then it took 18.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
carddass.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value10.1 s
0/100
25%
Value14.8 s
1/100
10%
Value370 ms
71/100
30%
Value0.365
29/100
15%
Value10.3 s
24/100
10%
1736 ms
499 ms
1339 ms
521 ms
537 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Carddass.com, 3% (4 requests) were made to Spdmg-backend.i-mobile.co.jp and 2% (3 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source Sec.carddass.com.
Page size can be reduced by 4.2 MB (57%)
7.5 MB
3.2 MB
In fact, the total size of Carddass.com main page is 7.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. 60% of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.
Potential reduce by 87.4 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 13.1 kB, which is 12% 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 87.4 kB or 83% of the original size.
Potential reduce by 3.6 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. Obviously, Carddass needs image optimization as it can save up to 3.6 MB or 55% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 271.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 271.5 kB or 60% of the original size.
Potential reduce by 251.6 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. Carddass.com needs all CSS files to be minified and compressed as it can save up to 251.6 kB or 83% of the original size.
Number of requests can be reduced by 37 (28%)
132
95
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carddass. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
1736 ms
basic.css
499 ms
jquery-2.1.4.min.js
1339 ms
main.js
521 ms
jquery.easing.1.3.js
537 ms
jquery.matchHeight.js
558 ms
jquery.mousewheel.js
874 ms
jquery.jscrollpane.min.js
1384 ms
jquery.flexslider-min.js
1475 ms
common.js
1042 ms
top.css
1071 ms
jquery.jscrollpane.css
1416 ms
showmore.js
1569 ms
top.js
1595 ms
conversion.js
35 ms
s_retargeting.js
1414 ms
adv.js
250 ms
reset.css
1396 ms
layout.css
1983 ms
sdk.js
184 ms
analytics.js
151 ms
ico_arrow-more.png
207 ms
logo_card.png
206 ms
logo_club.png
212 ms
navi_top.png
591 ms
navi_topics.png
592 ms
navi_event.png
626 ms
navi_campaign.png
771 ms
navi_search.png
779 ms
navi_enquete.png
780 ms
img_banner-322.jpg
2088 ms
img_banner-215.jpg
2180 ms
img_banner-168.jpg
2287 ms
img_banner-133.jpg
2280 ms
img_banner-312.jpg
4439 ms
img_banner-308.jpg
2152 ms
img_banner-62.jpg
3617 ms
img_banner-265.jpg
3689 ms
img_banner-315.jpg
3763 ms
img_banner-316.jpg
3802 ms
img_banner-240.jpg
3947 ms
img_banner-22.jpg
5283 ms
img_banner-disney_09.jpg
4614 ms
img_banner-idolish7_01.jpg
4852 ms
img_banner-sailormoon_15.jpg
4697 ms
img_banner-sailormoon_14.jpg
4876 ms
img_banner-dbs_02.jpg
5589 ms
img_banner-sailormoon_12.jpg
5517 ms
img_banner-gintama02.jpg
5600 ms
img_banner-nekoatsume_02.jpg
5790 ms
img_banner-monster-strike_01.jpg
5823 ms
img_banner-sw.jpg
6190 ms
img_banner-sailormoon_13.jpg
6486 ms
img_banner-owarino-seraph.jpg
6710 ms
img_banner-aikatsu21.png
6591 ms
img_banner-sailormoon_11.jpg
6715 ms
player_api
179 ms
img_banner-ultrax_02.jpg
6760 ms
79 ms
collect
43 ms
dg_gateway.js
258 ms
adv_inner.js
37 ms
collect
51 ms
img_banner-cocotama.jpg
7155 ms
45 ms
www-widgetapi.js
34 ms
img_banner-gintama04.jpg
7359 ms
xd_arbiter.php
67 ms
img_banner-toukenranbu05.jpg
7461 ms
40 ms
QMFzcIiLrac
48 ms
www-embed-player-vflQrT_sR.css
4 ms
www-embed-player.js
21 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
29 ms
QMFzcIiLrac
132 ms
adv.aspx
885 ms
adv.aspx
1036 ms
ad_status.js
36 ms
img_banner-rascal.jpg
7182 ms
stit_news.png
6645 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
27 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
28 ms
stit_e-app.png
6680 ms
stit_favorite.png
7026 ms
stit_character.png
7070 ms
stit_topics.png
7093 ms
dgcore.js
47 ms
adSiteVisit.js
39 ms
tr_adv.ashx
165 ms
tr_adv.ashx
200 ms
img_logo-133.png
6349 ms
img_logo-62.png
6031 ms
img_logo-315.png
6523 ms
img_logo-215.png
6403 ms
img_logo-179.png
6425 ms
img_logo-168.png
5145 ms
img_logo-78.png
5051 ms
img_logo-265.png
5580 ms
img_logo-313.png
5767 ms
img_logo-322.png
5306 ms
img_logo-285.png
5173 ms
img_logo-308.png
4975 ms
img_logo-239.png
4577 ms
img_logo-297.png
5352 ms
img_logo-326.png
4940 ms
stit_product.png
4559 ms
img_ico-first.png
4586 ms
img_ico-mid.png
4511 ms
img_ico-last.png
4538 ms
stit_sitelist.png
4528 ms
logo_cd.png
4539 ms
img_logo-328.png
4444 ms
img_logo-312.png
4161 ms
img_logo-307.png
4461 ms
img_logo-276.png
4355 ms
logo_dcd.png
4110 ms
img_logo-253.png
4429 ms
img_logo-205.png
3912 ms
logo_ncd.png
3885 ms
img_logo-111.png
4308 ms
img_logo-226.png
4354 ms
img_logo-316.png
4334 ms
img_logo-325.png
4236 ms
img_logo-306.png
4300 ms
logo_iccd.png
3904 ms
img_banner-csgw.jpg
4955 ms
stit_support.png
4106 ms
img_banner-dcdst.png
4021 ms
img_banner-bds.png
3841 ms
img_banner-pb.png
3831 ms
logo_card02.png
3923 ms
logo_bandai.png
4106 ms
tit_bar-card.png
4194 ms
ico_pp.png
3808 ms
ico_env.png
3818 ms
ico_map.png
3796 ms
ico_contact.png
3806 ms
carddass.com 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-hidden="true"] elements contain focusable descendents
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
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
Links do not have a discernible name
carddass.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
carddass.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carddass.com 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 Carddass.com 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.
carddass.com
Open Graph data is detected on the main page of Carddass. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: