10.3 sec in total
1.1 sec
8.4 sec
760 ms
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.cardsWe 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.
dig.cards performance score
1122 ms
889 ms
1893 ms
42 ms
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 size can be reduced by 1.4 MB (45%)
3.2 MB
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.
Potential reduce by 190.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.
Potential reduce by 64.1 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. Dig images are well optimized though.
Potential reduce by 877.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.
Potential reduce by 306.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. 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.
Number of requests can be reduced by 41 (41%)
99
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.
dig.cards
1122 ms
application_pc-d9d9d8c480247bdfe191eb776883cadd.css
889 ms
application-215a49d6b02c5b4877c528a314d7e248.js
1893 ms
jsapi
42 ms
js
60 ms
platform.js
181 ms
adsbygoogle.js
30 ms
line-button.js
843 ms
bookmark_button.js
660 ms
gtm.js
237 ms
all.js
298 ms
logo-d937d2f8b6618c8ec59c4b9e3a131172.png
182 ms
mtg_logo-74682fe0ae1ad1f88e273f92636bcf20.png
211 ms
fontawesome-webfont-14a0acb0e78c3989db7dee7a8618437d.woff
988 ms
thumb_b3fef91e-b95a-4162-b4fa-b5b2536f8e5c.jpg
938 ms
button-only@2x.png
218 ms
mana_white-aff11882aa22f3528572e823b4fca1e6.png
218 ms
mana_black-35ef13f60310fa8d1308097728b5ffc2.png
288 ms
mana_red-3f0b836cf0953a95a1a28311f2c8561e.png
438 ms
mana_blue-0ec5acf406bbe302b1e95e2081ba7b31.png
711 ms
mana_green-8a48eddeb0d6f84a2ba14f626a60c3b3.png
709 ms
thumb_4770e3c8-7bac-4020-b394-cf1b0efb4bde.jpg
1439 ms
thumb_bc7ff6e5-e633-427a-870e-11b174a370dd.jpg
954 ms
thumb_a21a76e4-8e5c-4a36-b0f3-cb8910bf50f5.jpg
985 ms
thumb_d490822e-4f8b-4e4d-a726-87dc7306f544.jpg
1407 ms
thumb_6ea29899-b802-4fd2-a353-46c507f969eb.jpg
1257 ms
thumb_bdc56975-4e6b-40df-ae64-4634d0059cca.jpg
1799 ms
thumb_3dced62e-9423-42e0-b85c-64b5bb5646d7.jpg
1630 ms
thumb_63a62698-b8f2-415c-95b5-7b6aff5b3d2f.jpg
1797 ms
bg_bottom.png
876 ms
thumb_4fff7982-31f3-43f3-8080-09813da51849.jpg
2115 ms
thumb_094a94cd-0dc5-4db6-abd9-79ef8e79e510.jpg
2191 ms
31c25ed9-01d1-4731-aa22-e7d28b54045b.jpg
2543 ms
25983b7d-acd3-4259-be55-ea834db31cb5.jpg
2324 ms
32814a23-779f-46a7-b144-9c1dac8462f5.jpg
2550 ms
foundation-icons.woff
709 ms
ca-pub-4033358270369188.js
78 ms
zrt_lookup.html
131 ms
show_ads_impl.js
142 ms
analytics.js
203 ms
235 ms
xd_arbiter.php
493 ms
ui-bg_flat_75_ffffff_40x100-bb0051ba9b6d87ef3f9425d05cb2f7f8.png
493 ms
ui-bg_highlight-soft_75_cccccc_1x100-7984ba05f627254dfdbdde97f999f415.png
768 ms
ui-bg_glass_75_e6e6e6_1x400-6522c988bbf45e6b805b6ed4adf70079.png
768 ms
ui-bg_glass_65_ffffff_1x400-e50e57d636a734253c3c0b4cb4cef861.png
762 ms
d2bd3e3f-c21f-4746-aded-7496a977d9ce.jpg
2471 ms
dca9deef-5f24-4c3c-a86e-abc4d5aa4b5a.jpg
2929 ms
515dec33-749f-46d4-8b8e-b330c8ff1f45.jpg
3340 ms
0e463c3f-e79d-48ad-8b32-19cc9b241b23.jpg
2990 ms
89f002a7-2ecc-471b-aa8e-0d177de717e2.jpg
3203 ms
deb0550a-3f01-496d-850b-6b2709da3eeb.jpg
3399 ms
ba0f0e47-91b5-4c93-a76b-58c1af14ac02.jpg
3407 ms
a7e41afa-5feb-455f-8ac8-ea6d719cecb9.jpg
3983 ms
6f13e8e3-90fa-444a-abb4-8958f0ff4779.jpg
3792 ms
19c5fc39-9558-400b-8dca-bb291319edf9.jpg
4176 ms
7b300e9a-36d8-46bf-aad5-c05538dd32f3.jpg
4147 ms
6fa95bbe-e910-4cbe-b983-cd242bedf6b2.jpg
4358 ms
1c55d349-7dd8-464e-b3f3-935a01ea3dd4.jpg
4239 ms
cea2bbf9-ed07-4074-867e-cae8999fc98d.jpg
4613 ms
ads
379 ms
osd.js
79 ms
collect
307 ms
ads
580 ms
ads
570 ms
widgets.js
566 ms
1218 ms
cb=gapi.loaded_0
80 ms
cb=gapi.loaded_1
78 ms
sharebutton
276 ms
like.php
124 ms
3384096164867997740
271 ms
abg.js
399 ms
m_js_controller.js
447 ms
googlelogo_color_112x36dp.png
267 ms
postmessageRelay
375 ms
rU2ubZ6l1Q5.js
604 ms
LVx-xkvaJ0b.png
621 ms
rs=AGLTcCMjQOKLzmHw4jAL4LZH64_0PwYekw
174 ms
rs=AGLTcCNg3nB9ViJ--ci26eSpjZeFJ_EieQ
165 ms
grlryt2bdKIyfMSOhzd1eA.woff
357 ms
vxNK-E6B13CyehuDCmvQvw.woff
449 ms
13250232331523409936
232 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
243 ms
s
136 ms
x_button_blue2.png
135 ms
api.js
139 ms
core:rpc:shindig.random:shindig.sha1.js
247 ms
2536007149-postmessagerelay.js
241 ms
nessie_icon_tiamat_white.png
53 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
23 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
126 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
147 ms
reset.css
157 ms
entry-button.css
309 ms
jot.html
27 ms
bbtn-l_v3.png
154 ms
activeview
14 ms
nr-885.min.js
132 ms
common.js
9 ms
util.js
32 ms
stats.js
29 ms
ui
31 ms
ba05d657a2
107 ms
AuthenticationService.Authenticate
71 ms
dig.cards SEO score
JA
N/A
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.
dig.cards
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: