Tools & Wizards About Us
tocage.jp screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

tocage.jp

DuelPortal トレーディングカードゲームコミュニケーションツール

Page Load Speed

7.9 sec in total

First Response

1.9 sec

Resources Loaded

5.7 sec

Page Rendered

337 ms

tocage.jp screenshot

About Website

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.jp

Key Findings

We analyzed Tocage.jp page load time and found that the first response time was 1.9 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

tocage.jp performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

tocage.jp

1850 ms

GlobalNaviUni.css

333 ms

CommonStyle.css

333 ms

GlobalNaviTop.css

331 ms

TopStyle.css

682 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 58% of them (43 requests) were addressed to the original Tocage.jp, 7% (5 requests) were made to Googleads.g.doubleclick.net and 5% (4 requests) were made to Cdn-fluct.sh.adingo.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Tocage.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 530.5 kB (27%)

Content Size

2.0 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 93.2 kB

  • Original 109.1 kB
  • After minification 90.2 kB
  • After compression 15.9 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 18.9 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 93.2 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 2.1 kB

  • Original 1.0 MB
  • After minification 1.0 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. Tocage images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 368.3 kB

  • Original 754.2 kB
  • After minification 500.0 kB
  • After compression 385.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 368.3 kB or 49% of the original size.

CSS Optimization

-89%

Potential reduce by 66.8 kB

  • Original 75.4 kB
  • After minification 57.9 kB
  • After compression 8.6 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 66.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (44%)

Requests Now

73

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tocage.jp

tocage.jp

1850 ms

GlobalNaviUni.css

GlobalNaviUni.css

333 ms

CommonStyle.css

CommonStyle.css

333 ms

GlobalNaviTop.css

GlobalNaviTop.css

331 ms

TopStyle.css

TopStyle.css

682 ms

TopJack.css

TopJack.css

343 ms

Icon.css

Icon.css

663 ms

Prizeresearch.css

Prizeresearch.css

496 ms

jquery.js

jquery.js

1690 ms

tag_ctl.js

tag_ctl.js

514 ms

lity.min.js

lity.min.js

663 ms

imageSizeFix.js

imageSizeFix.js

686 ms

f.js

f.js

24 ms

adsbygoogle.js

adsbygoogle.js

102 ms

f.js

f.js

3 ms

f.js

f.js

7 ms

f.js

f.js

10 ms

widgets.js

widgets.js

94 ms

ga.js

ga.js

42 ms

WrapperBG.png

WrapperBG.png

174 ms

logo2018ora.jpg

logo2018ora.jpg

1702 ms

105_1445235548s.png

105_1445235548s.png

173 ms

1_1246696294s.jpg

1_1246696294s.jpg

174 ms

helpindex.gif

helpindex.gif

677 ms

sh.adingo.jp

sh.adingo.jp

691 ms

__utm.gif

__utm.gif

13 ms

show_ads.js

show_ads.js

66 ms

i.adingo.jp

i.adingo.jp

688 ms

adsbygoogle.js

adsbygoogle.js

145 ms

koushinINDEX.jpg

koushinINDEX.jpg

173 ms

show_ads_impl.js

show_ads_impl.js

248 ms

0506kw-thum07.jpg

0506kw-thum07.jpg

343 ms

0506kw-thum06.jpg

0506kw-thum06.jpg

500 ms

0506kw-thum05.jpg

0506kw-thum05.jpg

695 ms

0506kw-thum04.jpg

0506kw-thum04.jpg

696 ms

sh.adingo.jp

sh.adingo.jp

178 ms

0506kw-thum03.jpg

0506kw-thum03.jpg

509 ms

0506kw-thum02.jpg

0506kw-thum02.jpg

464 ms

0506kw-thum01.jpg

0506kw-thum01.jpg

700 ms

0505kw-thum03.jpg

0505kw-thum03.jpg

529 ms

0505kw-thum02.jpg

0505kw-thum02.jpg

631 ms

0505kw-thum01.jpg

0505kw-thum01.jpg

662 ms

0719ua-thum01.jpg

0719ua-thum01.jpg

833 ms

0504ab-thum02.jpg

0504ab-thum02.jpg

857 ms

0504ab-thum01.jpg

0504ab-thum01.jpg

705 ms

0503kk-thum01.jpg

0503kk-thum01.jpg

797 ms

0503mv-thum01.jpg

0503mv-thum01.jpg

1000 ms

0503bs-thum01.jpg

0503bs-thum01.jpg

876 ms

0502kt-thum08.jpg

0502kt-thum08.jpg

882 ms

0502kt-thum10.jpg

0502kt-thum10.jpg

963 ms

0502kt-thum07.jpg

0502kt-thum07.jpg

1002 ms

0502kt-thum09.jpg

0502kt-thum09.jpg

1032 ms

0502kt-thum06.jpg

0502kt-thum06.jpg

1050 ms

0502kt-thum04.jpg

0502kt-thum04.jpg

1058 ms

0502kt-thum05.jpg

0502kt-thum05.jpg

1130 ms

0502kt-thum03.jpg

0502kt-thum03.jpg

1169 ms

TopRightRankIndex.jpg

TopRightRankIndex.jpg

172 ms

i.adingo.jp

i.adingo.jp

460 ms

sh.adingo.jp

sh.adingo.jp

177 ms

zrt_lookup.html

zrt_lookup.html

51 ms

ads

ads

214 ms

ads

ads

178 ms

ads

ads

167 ms

j

j

528 ms

i.adingo.jp

i.adingo.jp

311 ms

v1

v1

675 ms

sh.adingo.jp

sh.adingo.jp

180 ms

j

j

513 ms

i.adingo.jp

i.adingo.jp

168 ms

v1

v1

169 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

57 ms

ads

ads

157 ms

settings

settings

74 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

24 ms

Accessibility Review

tocage.jp accessibility score

57

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

tocage.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

tocage.jp 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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

Social Sharing Optimization

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: