Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dig.cards

デッキもカードも大会も。マジックの全ての情報がここに。|Dig マジック:ザ・ギャザリング<MTG>情報

Page Load Speed

10.3 sec in total

First Response

1.1 sec

Resources Loaded

8.4 sec

Page Rendered

760 ms

dig.cards screenshot

About Website

Welcome to dig.cards homepage info - get ready to check Dig best content for Japan right away, or after learning these important things about dig.cards

TCGのことならDigへ!各大会で優良な成績を残したデッキが見つかります。コラム、大会で結果を残したデッキの検索、ショップの検索、大会の検索などのコンテンツを用意しております。

Visit dig.cards

Key Findings

We analyzed Dig.cards page load time and found that the first response time was 1.1 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

dig.cards performance score

0

Network Requests Diagram

dig.cards

1122 ms

application_pc-d9d9d8c480247bdfe191eb776883cadd.css

889 ms

application-215a49d6b02c5b4877c528a314d7e248.js

1893 ms

jsapi

42 ms

js

60 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 16% of them (17 requests) were addressed to the original Dig.cards, 27% (28 requests) were made to D2dngmbhdh8kyf.cloudfront.net and 7% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source D2dngmbhdh8kyf.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (45%)

Content Size

3.2 MB

After Optimization

1.8 MB

In fact, the total size of Dig.cards 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. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 190.6 kB

  • Original 220.2 kB
  • After minification 200.4 kB
  • After compression 29.6 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 190.6 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 64.1 kB

  • Original 1.2 MB
  • After minification 1.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. Dig images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 877.8 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 503.8 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 877.8 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 306.8 kB

  • Original 372.8 kB
  • After minification 369.4 kB
  • After compression 66.0 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. Dig.cards needs all CSS files to be minified and compressed as it can save up to 306.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (41%)

Requests Now

99

After Optimization

58

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

SEO Factors

dig.cards SEO score

0

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 Dig.cards 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 Dig.cards 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 Dig. 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: