6.4 sec in total
1.4 sec
4.2 sec
751 ms
Welcome to tocage.jp homepage info - get ready to check Tocage best content for Japan right away, or after learning these important things about tocage.jp
トレーディングカードゲームの総合コミュニティツール DuelPortal
Visit tocage.jpWe analyzed Tocage.jp page load time and found that the first response time was 1.4 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tocage.jp performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value5.1 s
25/100
25%
Value8.2 s
20/100
10%
Value620 ms
48/100
30%
Value0.002
100/100
15%
Value11.1 s
20/100
10%
1447 ms
315 ms
324 ms
529 ms
369 ms
Our browser made a total of 179 requests to load all elements on the main page. We found that 35% of them (62 requests) were addressed to the original Tocage.jp, 9% (16 requests) were made to Pbs.twimg.com and 6% (10 requests) were made to Jp-u.openx.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Tocage.jp.
Page size can be reduced by 345.1 kB (10%)
3.4 MB
3.0 MB
In fact, the total size of Tocage.jp main page is 3.4 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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 99.3 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 19.4 kB, which is 17% 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 99.3 kB or 86% of the original size.
Potential reduce by 22.4 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. Tocage images are well optimized though.
Potential reduce by 169.9 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 169.9 kB or 63% of the original size.
Potential reduce by 53.5 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. Tocage.jp needs all CSS files to be minified and compressed as it can save up to 53.5 kB or 90% of the original size.
Number of requests can be reduced by 78 (45%)
173
95
The browser has sent 173 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tocage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
tocage.jp
1447 ms
CommonStyle.css
315 ms
GlobalNaviTop.css
324 ms
TopStyle.css
529 ms
TopJack.css
369 ms
Icon.css
376 ms
tag_ctl.js
472 ms
shop_register.js
483 ms
imageSizeFix.js
550 ms
sh.adingo.jp
535 ms
show_ads.js
9 ms
sh.adingo.jp
612 ms
sh.adingo.jp
644 ms
sh.adingo.jp
693 ms
118_4_194_100.gif
166 ms
ga.js
34 ms
WrapperBG.png
159 ms
logo2014.jpg
189 ms
ma-top2-01.png
905 ms
tri.jpg
165 ms
avc-banner02.jpg
550 ms
105_1445235548s.png
395 ms
86_1377498725s.gif
471 ms
75_1355998185s.jpg
539 ms
helpindex.gif
398 ms
sync
672 ms
sync
577 ms
pixel
95 ms
cm
420 ms
sync
73 ms
sync
101 ms
jstag
72 ms
i.adingo.jp
398 ms
__utm.gif
39 ms
642 ms
pixel
18 ms
636 ms
628 ms
acj
65 ms
pd
11 ms
zrt_lookup.html
38 ms
show_ads_impl.js
50 ms
ri
20 ms
3817754f-1fea-e149-c502-fd7837de0a47
169 ms
pixel
34 ms
sd
5 ms
sd
129 ms
ads
397 ms
GNavigatinBG.jpg
208 ms
TopHover.png
255 ms
MypageHover.png
328 ms
Mypage.png
365 ms
NewsHover.png
366 ms
News.png
403 ms
ReleaseHover.png
432 ms
Release.png
489 ms
TenpoHover.png
536 ms
Tenpo.png
541 ms
StreetHover.png
588 ms
Street.png
656 ms
TradeHover.png
657 ms
Trade.png
687 ms
SinchakuHover.png
748 ms
Sinchaku.png
763 ms
DeckHover.png
779 ms
Deck.png
834 ms
koushinINDEX.jpg
868 ms
osd.js
61 ms
sd
34 ms
ads
317 ms
0229dn-thum02.jpg
786 ms
0229dn-thum.jpg
989 ms
0229mtgc-thum.jpg
904 ms
1103mtg-thum.jpg
1451 ms
sync
21 ms
i.adingo.jp
299 ms
acj
35 ms
pd
59 ms
ads
367 ms
0229wx-thum.jpg
1447 ms
0229gb-thum.jpg
1799 ms
0402dp-thum.jpg
875 ms
0229hb-thum.jpg
1114 ms
0229bh-thum.jpg
1350 ms
0809yg-thum.jpg
1391 ms
0215pc-thum.jpg
1309 ms
0226ma-thum.jpg
1469 ms
0226fw-thum.jpg
1667 ms
0226zx-thum.jpg
1918 ms
ri
34 ms
sync
13 ms
acj
28 ms
i.adingo.jp
458 ms
sd
149 ms
cs
1194 ms
sg.gif
330 ms
0225dm-thum.jpg
1516 ms
0226mv-thum.jpg
1883 ms
0226vg-thum.jpg
1780 ms
pd
27 ms
ads
290 ms
ri
18 ms
sync
12 ms
acj
41 ms
i.adingo.jp
404 ms
0209mtg-thum.jpg
1788 ms
322 ms
pd
31 ms
ads
215 ms
ri
17 ms
widgets.js
176 ms
0226mtg-thum.jpg
1675 ms
1118gx-thum.jpg
1798 ms
0226bf-thum.jpg
1987 ms
sd
6 ms
js
277 ms
13265072386833147624
53 ms
abg.js
54 ms
m_js_controller.js
65 ms
googlelogo_color_112x36dp.png
131 ms
0225wss-thum.jpg
1917 ms
1228aa-thum.jpg
1934 ms
637 ms
s
67 ms
x_button_blue2.png
66 ms
TopRightRankIndex.jpg
1759 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
301 ms
255 ms
emmaq59w_300x250.jpeg
172 ms
ca
150 ms
E53B30E9F7
153 ms
moatad.js
172 ms
js
247 ms
js
234 ms
sd
44 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
45 ms
733 ms
img
153 ms
AdImpression
461 ms
img
86 ms
img
71 ms
Q116_Wu_Com_AwarenessM_V5_D_468x60_EN_US.jpg
92 ms
lidar.js
25 ms
sbhK2lTE.js
24 ms
syndication
247 ms
306980796466601985
432 ms
Q116_Wu_Com_Awareness_V3_D_300x250_EN_US.jpg
148 ms
15-Q115_WU__1_Fee_V1_D_Update_Mobile_468x60_EN_US.png
146 ms
711 ms
cTrvNaRi.html
47 ms
693 ms
activeview
28 ms
activeview
16 ms
activeview
15 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
41 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
114 ms
VU9m9jwo_normal.png
228 ms
BegvAAv3_normal.jpg
256 ms
L4lh8MMV_normal.jpg
294 ms
OYyZ8NP1_normal.jpg
377 ms
D_cKOCsk_normal.jpg
390 ms
QwHNto4w_normal.jpg
347 ms
0LZvIPFf_normal.jpg
385 ms
J-rLCwGo_normal.jpg
408 ms
tZa2EGsz_normal.jpg
348 ms
liz_normal.jpg
372 ms
l8u9VUMS_normal.jpg
529 ms
A5C7pgH7_normal.jpg
398 ms
rRUTodz9_normal.png
511 ms
qdaKVFZ0_normal.jpg
411 ms
C2oyDcAa_normal.jpeg
541 ms
dPg3Naby_normal.png
530 ms
sd
11 ms
jot
29 ms
cap
30 ms
ca
9 ms
ca
15 ms
get
4 ms
get
8 ms
tocage.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
tocage.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
tocage.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tocage.jp 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 Tocage.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.
tocage.jp
Open Graph description is not detected on the main page of Tocage. 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: