Access yurikamome.tokyo. 新交通ゆりかもめ

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value34.4 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value13,130 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value26.8 s

0/100

10%

yurikamome.tokyo

10 ms

www.yurikamome.co.jp

639 ms

js

67 ms

js

100 ms

style.css

346 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yurikamome.tokyo, 70% (90 requests) were made to Yurikamome.co.jp and 16% (20 requests) were made to Tokyo-odaiba.net. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Yurikamome.co.jp.

Content Size

12.7 MB

After Optimization

11.2 MB

In fact, the total size of Yurikamome.tokyo main page is 12.7 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 11.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 112.8 kB

Original 130.6 kB
After minification 115.8 kB
After compression 17.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 14.8 kB, which is 11% 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 112.8 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 854.8 kB

Original 11.8 MB
After minification 11.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. Yurikamome images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 345.5 kB

Original 496.3 kB
After minification 490.0 kB
After compression 150.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 345.5 kB or 70% of the original size.

CSS Optimization

-80%

Potential reduce by 184.3 kB

Original 229.6 kB
After minification 158.6 kB
After compression 45.3 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. Yurikamome.tokyo needs all CSS files to be minified and compressed as it can save up to 184.3 kB or 80% of the original size.

Requests Now

125

After Optimization

100

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

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

yurikamome.tokyo

Open Graph description is not detected on the main page of Yurikamome. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

新交通ゆりかもめ

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

yurikamome.tokyo

www.yurikamome.co.jp

js

js

style.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

yurikamome.tokyo

www.yurikamome.co.jp

js

js

style.css

normalize.min.css

jquery.fancybox.min.css

base.css

common.css

all.css

suggest.css

slick.css

home.css

jquery-3.7.1.min.js

jsrender.min.js

jquery-ui.min.js

jquery.fancybox.min.js

common.js

main.js

slick.min.js

home.js

inc.js

widgets.js

wejs

Tripadvisor_lockup_horizontal_secondary_registered-11900-2.svg

logo@2x.png

icn-sta01@2x.png

icn-sta02@2x.png

icn-sta03@2x.png

icn-sta04@2x.png

pt-nav01-01@2x.jpg

pt-nav01-02@2x.jpg

pt-nav01-03@2x.jpg

pt-nav01-04@2x.jpg

pt-nav02-01@2x.jpg

pt-nav02-02@2x.jpg

pt-nav03-01@2x.jpg

pt-nav03-02@2x.jpg

pt-nav03-03@2x.jpg

pt-nav03-04@2x.jpg

pt-nav04-01@2x.jpg

pt-nav04-02@2x.jpg

pt-nav04-03@2x.jpg