Tools & Wizards About Us
verdy.co.jp screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

verdy.co.jp

東京ヴェルディ / Tokyo Verdy

Page Load Speed

6.1 sec in total

First Response

564 ms

Resources Loaded

4.9 sec

Page Rendered

627 ms

verdy.co.jp screenshot

About Website

Click here to check amazing Verdy content for Japan. Otherwise, check out these important facts you probably never knew about verdy.co.jp

東京ヴェルディの公式WEBサイトへようこそ！最新ニュース、試合データ＆テキスト速報、チーム情報、観戦ガイド、ファン向けコンテンツなどあらゆる情報をお届けします。

Visit verdy.co.jp

Key Findings

We analyzed Verdy.co.jp page load time and found that the first response time was 564 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

verdy.co.jp performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value36.4 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

verdy.co.jp

564 ms

gtm.js

51 ms

style.css

243 ms

chatbot.css

713 ms

jquery-3.3.1.min.gz.js

876 ms

Our browser made a total of 146 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Verdy.co.jp, 41% (60 requests) were made to Verdy.s3-ap-northeast-1.amazonaws.com and 25% (36 requests) were made to Verdy.s3.ap-northeast-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Verdy.s3.ap-northeast-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (13%)

Content Size

8.3 MB

After Optimization

7.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Verdy.co.jp main page is 8.3 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. Images take 7.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 59.5 kB

  • Original 73.5 kB
  • After minification 71.8 kB
  • After compression 13.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. 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 59.5 kB or 81% of the original size.

Image Optimization

-12%

Potential reduce by 905.3 kB

  • Original 7.8 MB
  • After minification 6.9 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. Obviously, Verdy needs image optimization as it can save up to 905.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 107.8 kB

  • Original 398.2 kB
  • After minification 398.2 kB
  • After compression 290.4 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 107.8 kB or 27% of the original size.

CSS Optimization

-14%

Potential reduce by 358 B

  • Original 2.6 kB
  • After minification 2.6 kB
  • After compression 2.2 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. Verdy.co.jp needs all CSS files to be minified and compressed as it can save up to 358 B or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (45%)

Requests Now

138

After Optimization

76

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

verdy.co.jp

verdy.co.jp

564 ms

gtm.js

gtm.js

51 ms

style.css

style.css

243 ms

chatbot.css

chatbot.css

713 ms

jquery-3.3.1.min.gz.js

jquery-3.3.1.min.gz.js

876 ms

jquery.easing.min.gz.js

jquery.easing.min.gz.js

828 ms

slick.min.gz.js

slick.min.gz.js

835 ms

jquery.matchHeight.gz.js

jquery.matchHeight.gz.js

835 ms

script.gz.js

script.gz.js

835 ms

jquery.lazy.min.gz.js

jquery.lazy.min.gz.js

836 ms

jquery.lazy.iframe.min.gz.js

jquery.lazy.iframe.min.gz.js

910 ms

script.gz.js

script.gz.js

1015 ms

js

js

46 ms

analytics.js

analytics.js

14 ms

destination

destination

31 ms

ytag.js

ytag.js

744 ms

collect

collect

31 ms

collect

collect

22 ms

ga-audiences

ga-audiences

96 ms

tokyov.html

tokyov.html

626 ms

62581_1000x280_65c304fb3bbce.png

62581_1000x280_65c304fb3bbce.png

704 ms

12810_5bad923ef0d6a.gz.svg

12810_5bad923ef0d6a.gz.svg

285 ms

9874_5b73c009817e7.gz.svg

9874_5b73c009817e7.gz.svg

290 ms

15726_5c415ef9bc845.gz.svg

15726_5c415ef9bc845.gz.svg

288 ms

flag_jpn.gz.svg

flag_jpn.gz.svg

355 ms

flag_uk.gz.svg

flag_uk.gz.svg

376 ms

flag_esp.gz.svg

flag_esp.gz.svg

467 ms

flag_bra.gz.svg

flag_bra.gz.svg

465 ms

flag_tha.gz.svg

flag_tha.gz.svg

477 ms

flag_id.gz.svg

flag_id.gz.svg

476 ms

icon_cart.gz.svg

icon_cart.gz.svg

508 ms

icon_search-white.gz.svg

icon_search-white.gz.svg

544 ms

icon_search.gz.svg

icon_search.gz.svg

646 ms

emblem_verdy_ac.gz.svg

emblem_verdy_ac.gz.svg

648 ms

9909_5b74e5e762e11.gz.svg

9909_5b74e5e762e11.gz.svg

651 ms

icon_menu-right-white.gz.svg

icon_menu-right-white.gz.svg

649 ms

lastest_match_bg.png

lastest_match_bg.png

903 ms

9914_5b74e6bd47a1c.gz.svg

9914_5b74e6bd47a1c.gz.svg

761 ms

9891_5b73e4bb14399.gz.svg

9891_5b73e4bb14399.gz.svg

860 ms

icon_ticket.gz.svg

icon_ticket.gz.svg

859 ms

9901_5b74e42b4e1e6.gz.svg

9901_5b74e42b4e1e6.gz.svg

861 ms

32_5b6934c1a327b.gz.svg

32_5b6934c1a327b.gz.svg

862 ms

9907_5b74e5c7020d2.gz.svg

9907_5b74e5c7020d2.gz.svg

909 ms

9912_5b74e63c45462.gz.svg

9912_5b74e63c45462.gz.svg

1007 ms

icon_bars-all-white.gz.svg

icon_bars-all-white.gz.svg

1004 ms

icon_pitch.gz.svg

icon_pitch.gz.svg

1010 ms

icon_building.gz.svg

icon_building.gz.svg

1017 ms

icon_academy.gz.svg

icon_academy.gz.svg

1048 ms

icon_futbol.gz.svg

icon_futbol.gz.svg

1088 ms

62582_1000x280_65c305074ff98.png

62582_1000x280_65c305074ff98.png

759 ms

45299_500x140_6246abe6e47ff.png

45299_500x140_6246abe6e47ff.png

902 ms

emblem_beleza_ac_w.gz.svg

emblem_beleza_ac_w.gz.svg

756 ms

64908_2560x1080_6634acb146ade.png

64908_2560x1080_6634acb146ade.png

1945 ms

64908_1800x2363_6634acb320138.png

64908_1800x2363_6634acb320138.png

1890 ms

visual_body_bg_ne.png

visual_body_bg_ne.png

902 ms

64895_560x260_6631eaf44edd7.png

64895_560x260_6631eaf44edd7.png

1402 ms

64384_560x260_661c62d020b9c.png

64384_560x260_661c62d020b9c.png

1562 ms

50403_560x260_631aebeacc43b.png

50403_560x260_631aebeacc43b.png

1416 ms

63017_560x260_65d8993919f78.png

63017_560x260_65d8993919f78.png

1566 ms

64084_560x260_660bae8b99de7.png

64084_560x260_660bae8b99de7.png

1577 ms

24689_5e0b6c911f70a.gz.svg

24689_5e0b6c911f70a.gz.svg

1583 ms

24884_5e254082e1039.gz.svg

24884_5e254082e1039.gz.svg

1745 ms

ranking_bg_verdy_ac_2.png

ranking_bg_verdy_ac_2.png

1747 ms

icon_verdy_ac.gz.svg

icon_verdy_ac.gz.svg

1761 ms

43322_61ea3b905493e.gz.svg

43322_61ea3b905493e.gz.svg

1761 ms

64881_480x270_6631bc0730301.png

64881_480x270_6631bc0730301.png

1945 ms

64874_480x270_663195ebe8cf6.png

64874_480x270_663195ebe8cf6.png

2105 ms

63170_480x270_65e1b6fa14778.png

63170_480x270_65e1b6fa14778.png

1948 ms

64788_480x270_662a1589cd61f.png

64788_480x270_662a1589cd61f.png

1946 ms

64737_480x270_6628a6a1972eb.png

64737_480x270_6628a6a1972eb.png

2103 ms

64730_480x270_662890eddda7f.png

64730_480x270_662890eddda7f.png

2107 ms

64170_480x270_660e272b5cc88.png

64170_480x270_660e272b5cc88.png

2123 ms

62575_480x270_65c0c0cad1ee4.png

62575_480x270_65c0c0cad1ee4.png

2122 ms

61326_480x270_656981188d3b2.png

61326_480x270_656981188d3b2.png

2135 ms

emblem_beleza_ac.gz.svg

emblem_beleza_ac.gz.svg

2259 ms

icon_partner.gz.svg

icon_partner.gz.svg

2280 ms

43460_470x120_61f0d891ea6da.png

43460_470x120_61f0d891ea6da.png

2282 ms

40298_470x120_615eb557e41b5.png

40298_470x120_615eb557e41b5.png

2304 ms

43458_470x120_61f0d7ea3fbb5.png

43458_470x120_61f0d7ea3fbb5.png

2301 ms

43459_470x120_61f0d8643a9e6.png

43459_470x120_61f0d8643a9e6.png

2317 ms

icon_twitter-footer.gz.svg

icon_twitter-footer.gz.svg

2438 ms

icon_tiktok-footer.gz.svg

icon_tiktok-footer.gz.svg

2464 ms

BFBonn-Bold.woff

BFBonn-Bold.woff

1280 ms

bg_verdy_ac.png

bg_verdy_ac.png

2364 ms

icon_verdy_ac_w.gz.svg

icon_verdy_ac_w.gz.svg

2380 ms

BFBonn-Regular.woff

BFBonn-Regular.woff

1257 ms

NotoSansJPS-Regular.woff

NotoSansJPS-Regular.woff

1804 ms

NotoSansJPS-Bold.woff

NotoSansJPS-Bold.woff

1961 ms

TokyoOneSolidOT.woff

TokyoOneSolidOT.woff

1128 ms

icon_youtube.gz.svg

icon_youtube.gz.svg

1110 ms

icon_blank.gz.svg

icon_blank.gz.svg

1263 ms

icon_twitter-white.gz.svg

icon_twitter-white.gz.svg

1166 ms

icon_facebook-white.gz.svg

icon_facebook-white.gz.svg

1256 ms

9963_150x80.jpg

9963_150x80.jpg

1264 ms

js

js

57 ms

segmentation.js

segmentation.js

88 ms

9964_150x80.jpg

9964_150x80.jpg

1331 ms

js

js

62 ms

collect

collect

27 ms

13365_150x80.png

13365_150x80.png

1256 ms

collect

collect

11 ms

12743_470x120.png

12743_470x120.png

1522 ms

cnt

cnt

828 ms

ga-audiences

ga-audiences

65 ms

9927_470x120.png

9927_470x120.png

1272 ms

12736_470x120.png

12736_470x120.png

1334 ms

12739_470x120.png

12739_470x120.png

1336 ms

9894_5b74d1aeeb2a0.gz.svg

9894_5b74d1aeeb2a0.gz.svg

1444 ms

9899_5b74d313e6a4b.gz.svg

9899_5b74d313e6a4b.gz.svg

1481 ms

9896_5b74d2303b2d1.gz.svg

9896_5b74d2303b2d1.gz.svg

1450 ms

reset.css

reset.css

4 ms

jheader.css

jheader.css

11 ms

gpt.js

gpt.js

136 ms

jheader_jlogo.png

jheader_jlogo.png

12 ms

jheader_team_emb_s_bw.png

jheader_team_emb_s_bw.png

13 ms

linkid.js

linkid.js

10 ms

collect

collect

10 ms

9897_5b74d28199812.gz.svg

9897_5b74d28199812.gz.svg

1435 ms

9898_5b74d2c18c3fa.gz.svg

9898_5b74d2c18c3fa.gz.svg

1458 ms

icon_menu-right.gz.svg

icon_menu-right.gz.svg

1460 ms

icon_ticket-white.gz.svg

icon_ticket-white.gz.svg

1516 ms

collect

collect

12 ms

js

js

49 ms

pubads_impl.js

pubads_impl.js

20 ms

ads

ads

62 ms

sodar

sodar

94 ms

container.html

container.html

37 ms

2829157078588573103

2829157078588573103

22 ms

window_focus.js

window_focus.js

22 ms

7847425855730815709

7847425855730815709

18 ms

sodar2.js

sodar2.js

15 ms

runner.html

runner.html

5 ms

aframe

aframe

32 ms

-Q1JhNmMPmyp-FWWBIPhIK8kdKZYRkbH2XUgs1gaV20.js

-Q1JhNmMPmyp-FWWBIPhIK8kdKZYRkbH2XUgs1gaV20.js

4 ms

icon_menu-left-white.gz.svg

icon_menu-left-white.gz.svg

179 ms

beacon.html

beacon.html

16 ms

pixel

pixel

50 ms

tap.php

tap.php

36 ms

Pug

Pug

38 ms

set

set

300 ms

pixel

pixel

47 ms

sd

sd

7 ms

report

report

798 ms

sync

sync

866 ms

bounce

bounce

8 ms

sync

sync

310 ms

Accessibility Review

verdy.co.jp accessibility score

77

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

verdy.co.jp SEO score

73

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

verdy.co.jp

Open Graph data is detected on the main page of Verdy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: