Tools & Wizards About Us
tokyo100k.jp screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

tokyo100k.jp

柴又100K～東京⇔埼玉⇔茨城の道～【公式】

Page Load Speed

6.2 sec in total

First Response

536 ms

Resources Loaded

5.3 sec

Page Rendered

315 ms

tokyo100k.jp screenshot

About Website

Visit tokyo100k.jp now to see the best up-to-date Tokyo 100 K content for Japan and also check out these interesting facts you probably never knew about tokyo100k.jp

2023年5月21日（日）に開催される「柴又100Ｋ～東京⇔埼玉⇔茨城の道～」公式サイトです。当サイトではコースマップ、エントリー情報などご覧いただけます。

Visit tokyo100k.jp

Key Findings

We analyzed Tokyo100k.jp page load time and found that the first response time was 536 ms and then it took 5.6 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

tokyo100k.jp performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value30.9 s

0/100

25%

SI (Speed Index)

Value19.6 s

0/100

10%

TBT (Total Blocking Time)

Value5,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.264

46/100

15%

TTI (Time to Interactive)

Value33.6 s

0/100

10%

Network Requests Diagram

tokyo100k.jp

536 ms

tokyo100k.jp

1005 ms

js

87 ms

style.min.css

184 ms

classic-themes.min.css

366 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 54% of them (45 requests) were addressed to the original Tokyo100k.jp, 10% (8 requests) were made to Youtube.com and 10% (8 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Tokyo100k.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 282.6 kB (6%)

Content Size

4.5 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyo100k.jp main page is 4.5 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. Only a small number of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 74.2 kB

  • Original 95.6 kB
  • After minification 94.2 kB
  • After compression 21.4 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 74.2 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 32.7 kB

  • Original 3.6 MB
  • After minification 3.6 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. Tokyo 100 K images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 154.5 kB

  • Original 617.2 kB
  • After minification 617.1 kB
  • After compression 462.6 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 154.5 kB or 25% of the original size.

CSS Optimization

-15%

Potential reduce by 21.3 kB

  • Original 146.2 kB
  • After minification 145.2 kB
  • After compression 125.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. Tokyo100k.jp needs all CSS files to be minified and compressed as it can save up to 21.3 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (38%)

Requests Now

73

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokyo100k.jp

tokyo100k.jp

536 ms

tokyo100k.jp

tokyo100k.jp

1005 ms

js

js

87 ms

style.min.css

style.min.css

184 ms

classic-themes.min.css

classic-themes.min.css

366 ms

foobox.free.min.css

foobox.free.min.css

522 ms

jquery.min.js

jquery.min.js

28 ms

foobox.free.min.js

foobox.free.min.js

704 ms

style_bizvektor_sns.css

style_bizvektor_sns.css

539 ms

css

css

35 ms

bizvektor_common.css

bizvektor_common.css

541 ms

rbs_std.css

rbs_std.css

722 ms

style.css

style.css

544 ms

fa-all.min.css

fa-all.min.css

866 ms

css2

css2

48 ms

biz-vektor-min.js

biz-vektor-min.js

715 ms

flexslider.css

flexslider.css

183 ms

sdk.js

sdk.js

121 ms

ZYFVmm9jWCo

ZYFVmm9jWCo

255 ms

8dgZlkqlRKs

8dgZlkqlRKs

188 ms

gWvA3fFAvxQ

gWvA3fFAvxQ

188 ms

3104

3104

725 ms

0TYuqq0ORvs

0TYuqq0ORvs

256 ms

header_banner.jpg

header_banner.jpg

1687 ms

slide0509record.jpg

slide0509record.jpg

1481 ms

tshirts_slide2023_sono2.jpg

tshirts_slide2023_sono2.jpg

2712 ms

slide_01.jpg

slide_01.jpg

1599 ms

slide_03.jpg

slide_03.jpg

2789 ms

slide_05.jpg

slide_05.jpg

1377 ms

result.jpg

result.jpg

1685 ms

runphotoplus.png

runphotoplus.png

1685 ms

ouennavi.png

ouennavi.png

1769 ms

update.png

update.png

1794 ms

bnr_sankainfo.png

bnr_sankainfo.png

1819 ms

h2_bg.png

h2_bg.png

1821 ms

tatta_run_tokyo100k.png

tatta_run_tokyo100k.png

1883 ms

gallery.png

gallery.png

1967 ms

volunteer.png

volunteer.png

2000 ms

shibamata2021.jpg

shibamata2021.jpg

2002 ms

bnr_hoka.jpg

bnr_hoka.jpg

2060 ms

bnr_zamst.png

bnr_zamst.png

2155 ms

bnr_amino-vital.jpg

bnr_amino-vital.jpg

2181 ms

bnr_asc.jpg

bnr_asc.jpg

2183 ms

rbs_zaidan1.jpg

rbs_zaidan1.jpg

2237 ms

katsushika.jpg

katsushika.jpg

2312 ms

tokyo_rikkyo.jpg

tokyo_rikkyo.jpg

2361 ms

saitama.jpg

saitama.jpg

2364 ms

runnet.jpg

runnet.jpg

2413 ms

teamr2.jpg

teamr2.jpg

2484 ms

footer_pagetop.png

footer_pagetop.png

2543 ms

vektor_kado_icons.woff

vektor_kado_icons.woff

2460 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

53 ms

general_foundicons.woff

general_foundicons.woff

2504 ms

fa-solid-900.ttf

fa-solid-900.ttf

2745 ms

fa-regular-400.ttf

fa-regular-400.ttf

2640 ms

R70djykGkuuDep-hRg6gbCm0Vw.ttf

R70djykGkuuDep-hRg6gbCm0Vw.ttf

838 ms

bg_control_nav.png

bg_control_nav.png

2634 ms

sdk.js

sdk.js

14 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

29 ms

base.js

base.js

80 ms

ad_status.js

ad_status.js

373 ms

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

330 ms

embed.js

embed.js

126 ms

gtm.js

gtm.js

248 ms

js

js

665 ms

runtime.5be623de732c3486.js

runtime.5be623de732c3486.js

56 ms

polyfills.f83859eaec44992d.js

polyfills.f83859eaec44992d.js

213 ms

main.6f8218f67525dcb4.js

main.6f8218f67525dcb4.js

244 ms

id

id

159 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

185 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

397 ms

Create

Create

444 ms

Create

Create

451 ms

Create

Create

452 ms

Create

Create

549 ms

id

id

415 ms

styles.abdae06893681e05.css

styles.abdae06893681e05.css

95 ms

styles.abdae06893681e05.css

styles.abdae06893681e05.css

92 ms

GenerateIT

GenerateIT

181 ms

GenerateIT

GenerateIT

187 ms

GenerateIT

GenerateIT

99 ms

GenerateIT

GenerateIT

15 ms

Accessibility Review

tokyo100k.jp accessibility score

53

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

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

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

High

Page has valid source maps

SEO Factors

tokyo100k.jp SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 doesn't use legible font sizes

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

tokyo100k.jp

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