Tools & Wizards About Us
carddass.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

carddass.com

カードダスドットコム 公式サイト | TOP

Page Load Speed

6.6 sec in total

First Response

1.6 sec

Resources Loaded

4.4 sec

Page Rendered

584 ms

carddass.com screenshot

About Website

Click here to check amazing Carddass content for Japan. Otherwise, check out these important facts you probably never knew about carddass.com

カードダス公式サイト カードダスドットコム

Visit carddass.com

Key Findings

We analyzed Carddass.com page load time and found that the first response time was 1.6 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

carddass.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value2,450 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.851

4/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

1581 ms

OtAutoBlock.js

83 ms

otSDKStub.js

117 ms

basic.css

493 ms

jquery-3.6.1.min.js

823 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Carddass.com, 4% (3 requests) were made to Cdn-apac.onetrust.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Sec.carddass.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 436.6 kB (53%)

Content Size

829.1 kB

After Optimization

392.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Carddass.com main page is 829.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 325.8 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 185.1 kB

  • Original 211.8 kB
  • After minification 205.2 kB
  • After compression 26.7 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 185.1 kB or 87% of the original size.

Image Optimization

-13%

Potential reduce by 42.7 kB

  • Original 325.8 kB
  • After minification 283.0 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. Obviously, Carddass needs image optimization as it can save up to 42.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 160.5 kB

  • Original 230.5 kB
  • After minification 193.2 kB
  • After compression 70.1 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 160.5 kB or 70% of the original size.

CSS Optimization

-79%

Potential reduce by 48.3 kB

  • Original 61.1 kB
  • After minification 58.8 kB
  • After compression 12.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. Carddass.com needs all CSS files to be minified and compressed as it can save up to 48.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (36%)

Requests Now

73

After Optimization

47

  • Images
  • JavaScript
  • CSS

The browser has sent 73 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 15 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

1581 ms

OtAutoBlock.js

OtAutoBlock.js

83 ms

otSDKStub.js

otSDKStub.js

117 ms

basic.css

basic.css

493 ms

jquery-3.6.1.min.js

jquery-3.6.1.min.js

823 ms

main.js

main.js

508 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

508 ms

jquery.matchHeight.js

jquery.matchHeight.js

528 ms

jquery.mousewheel.js

jquery.mousewheel.js

656 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

677 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

847 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

703 ms

common.js

common.js

820 ms

top.css

top.css

823 ms

timeline.css

timeline.css

845 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

877 ms

jquery.fancybox.css

jquery.fancybox.css

984 ms

showmore.js

showmore.js

984 ms

top.js

top.js

987 ms

jquery.fancybox.js

jquery.fancybox.js

1184 ms

16105eb1-8b2e-4f7a-b89c-3252da32fbac.json

16105eb1-8b2e-4f7a-b89c-3252da32fbac.json

39 ms

reset.css

reset.css

525 ms

layout.css

layout.css

736 ms

logo_card.png

logo_card.png

210 ms

logo_club.png

logo_club.png

210 ms

navi_top.png

navi_top.png

210 ms

navi_topics.png

navi_topics.png

208 ms

navi_event.png

navi_event.png

208 ms

navi_campaign.png

navi_campaign.png

211 ms

navi_search.png

navi_search.png

328 ms

navi_enquete.png

navi_enquete.png

329 ms

img_dammy.png

img_dammy.png

329 ms

stit_news.png

stit_news.png

340 ms

stit_e-app.png

stit_e-app.png

341 ms

stit_campaign.png

stit_campaign.png

350 ms

stit_favorite.png

stit_favorite.png

490 ms

stit_character.png

stit_character.png

491 ms

stit_topics.png

stit_topics.png

493 ms

img_logo-62.png

img_logo-62.png

505 ms

img_logo-570.png

img_logo-570.png

511 ms

img_logo-550.png

img_logo-550.png

524 ms

img_logo-503.png

img_logo-503.png

654 ms

img_logo-529.png

img_logo-529.png

660 ms

img_logo-418.png

img_logo-418.png

660 ms

img_logo-573.png

img_logo-573.png

673 ms

stit_product.png

stit_product.png

679 ms

img_ico-first.png

img_ico-first.png

698 ms

img_ico-last.png

img_ico-last.png

816 ms

stit_sitelist.png

stit_sitelist.png

821 ms

logo_cd.png

logo_cd.png

822 ms

img_logo-536.png

img_logo-536.png

841 ms

img_logo-527.png

img_logo-527.png

844 ms

img_logo-498.png

img_logo-498.png

871 ms

img_logo-516.png

img_logo-516.png

979 ms

logo_bcg.png

logo_bcg.png

982 ms

img_logo-583.png

img_logo-583.png

985 ms

logo_dcd.png

logo_dcd.png

1009 ms

img_logo-598.png

img_logo-598.png

1183 ms

img_banner-default.jpg

img_banner-default.jpg

954 ms

stit_support.png

stit_support.png

938 ms

img_banner-dcdst.png

img_banner-dcdst.png

940 ms

img_banner-bds.png

img_banner-bds.png

944 ms

img_banner-pb.png

img_banner-pb.png

973 ms

img_banner-bcs.png

img_banner-bcs.png

1014 ms

img_banner-cdo.png

img_banner-cdo.png

1040 ms

logo_card02.png

logo_card02.png

987 ms

logo_bandai.png

logo_bandai.png

991 ms

logo_bandainamco.png

logo_bandainamco.png

1020 ms

tit_bar-card.png

tit_bar-card.png

1014 ms

ico_pp.png

ico_pp.png

1058 ms

ico_env.png

ico_env.png

1122 ms

ico_map.png

ico_map.png

985 ms

ico_contact.png

ico_contact.png

992 ms

ico_arrow.png

ico_arrow.png

1026 ms

Accessibility Review

carddass.com accessibility score

92

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<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

High

Links do not have a discernible name

Best Practices

carddass.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

carddass.com 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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses 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 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.

Social Sharing Optimization

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: