Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

marathon.tokyo

トップページ | 東京マラソン2025

Page Load Speed

36.1 sec in total

First Response

294 ms

Resources Loaded

9 sec

Page Rendered

26.8 sec

marathon.tokyo screenshot

About Website

Welcome to marathon.tokyo homepage info - get ready to check Marathon best content for Bangladesh right away, or after learning these important things about marathon.tokyo

「東京がひとつになる日。」東京マラソン2025の大会公式ウェブサイトです。コースマップ、エントリー情報などご確認いただけます。

Visit marathon.tokyo

Key Findings

We analyzed Marathon.tokyo page load time and found that the first response time was 294 ms and then it took 35.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

marathon.tokyo performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value2,700 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.58

11/100

15%

TTI (Time to Interactive)

Value21.9 s

1/100

10%

Network Requests Diagram

marathon.tokyo

294 ms

www.marathon.tokyo

45 ms

gtm.js

126 ms

reset.css

11 ms

common.css

19 ms

Our browser made a total of 265 requests to load all elements on the main page. We found that 57% of them (151 requests) were addressed to the original Marathon.tokyo, 37% (99 requests) were made to Scontent-nrt1-2.cdninstagram.com and 3% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (5.5 sec) relates to the external source Scontent-nrt1-2.cdninstagram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.0 MB (7%)

Content Size

112.2 MB

After Optimization

104.2 MB

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

HTML Optimization

-81%

Potential reduce by 277.3 kB

  • Original 341.1 kB
  • After minification 269.0 kB
  • After compression 63.8 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 72.1 kB, which is 21% 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 277.3 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 7.7 MB

  • Original 111.7 MB
  • After minification 104.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. Marathon images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 50.7 kB

  • Original 131.2 kB
  • After minification 131.2 kB
  • After compression 80.5 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 50.7 kB or 39% of the original size.

CSS Optimization

-10%

Potential reduce by 3.0 kB

  • Original 29.5 kB
  • After minification 29.5 kB
  • After compression 26.4 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. Marathon.tokyo has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 119 (46%)

Requests Now

257

After Optimization

138

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

Accessibility Review

marathon.tokyo accessibility score

86

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

Best Practices

marathon.tokyo best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

marathon.tokyo SEO score

83

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 uses 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 Marathon.tokyo 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 Marathon.tokyo 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

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