Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

dccard.co.jp

クレジットカードなら三菱UFJニコス

Page Load Speed

12 sec in total

First Response

535 ms

Resources Loaded

9.6 sec

Page Rendered

1.9 sec

dccard.co.jp screenshot

About Website

Visit dccard.co.jp now to see the best up-to-date Dccard content for Japan and also check out these interesting facts you probably never knew about dccard.co.jp

信頼のクレジットカード、三菱UFJニコスの公式サイト。三菱UFJフィナンシャル・グループだからこそ実現できたセキュリティの高さと利便性をあなたに。お申込みはこちらから。

Visit dccard.co.jp

Key Findings

We analyzed Dccard.co.jp page load time and found that the first response time was 535 ms and then it took 11.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.

Performance Metrics

dccard.co.jp performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value20.2 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value1.08

2/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

dccard.co.jp

535 ms

www.cr.mufg.jp

360 ms

www.cr.mufg.jp

516 ms

reset.css

533 ms

parts_sp.css

1025 ms

Our browser made a total of 183 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dccard.co.jp, 60% (109 requests) were made to Cr.mufg.jp and 3% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Cr.mufg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (23%)

Content Size

4.5 MB

After Optimization

3.5 MB

In fact, the total size of Dccard.co.jp main page is 4.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. 65% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 97.7 kB

  • Original 117.4 kB
  • After minification 105.9 kB
  • After compression 19.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 97.7 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 265.4 kB

  • Original 3.4 MB
  • After minification 3.2 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. Dccard images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 327.9 kB

  • Original 520.1 kB
  • After minification 476.0 kB
  • After compression 192.2 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 327.9 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 324.5 kB

  • Original 381.9 kB
  • After minification 343.8 kB
  • After compression 57.4 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. Dccard.co.jp needs all CSS files to be minified and compressed as it can save up to 324.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 97 (56%)

Requests Now

173

After Optimization

76

The browser has sent 173 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dccard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

dccard.co.jp accessibility score

90

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dccard.co.jp best practices score

67

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dccard.co.jp SEO score

92

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dccard.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Dccard.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Dccard. 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: