Access nissan-stadium.jp. 日産スタジアム

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value220 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.346

32/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

nissan-stadium.jp

530 ms

www.nissan-stadium.jp

1026 ms

jquery-1.11.2.min.js

347 ms

jquery.belatedPNG.min.js

510 ms

jquery.matchHeight.js

512 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 94% of them (105 requests) were addressed to the original Nissan-stadium.jp, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Nissan-stadium.jp.

Content Size

2.7 MB

After Optimization

2.4 MB

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

HTML Optimization

-77%

Potential reduce by 25.6 kB

Original 33.4 kB
After minification 31.2 kB
After compression 7.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. 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 25.6 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 24.0 kB

Original 2.4 MB
After minification 2.3 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. Nissan Stadium images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 151.7 kB

Original 237.6 kB
After minification 216.9 kB
After compression 85.9 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 151.7 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 32.9 kB

Original 40.6 kB
After minification 26.9 kB
After compression 7.7 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. Nissan-stadium.jp needs all CSS files to be minified and compressed as it can save up to 32.9 kB or 81% of the original size.

Requests Now

108

After Optimization

The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nissan Stadium. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 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-*] attributes do not match their roles

High

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

High

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

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

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

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nissan-stadium.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 Nissan-stadium.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

nissan-stadium.jp

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

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

nissan-stadium.jp

www.nissan-stadium.jp

jquery-1.11.2.min.js

jquery.belatedPNG.min.js

jquery.matchHeight.js

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

nissan-stadium.jp

www.nissan-stadium.jp

jquery-1.11.2.min.js

jquery.belatedPNG.min.js

jquery.matchHeight.js

jquery.backstretch.min.js

rem.min.js

footerFixed.js

jquery.textresizer.js

jquery.cookie.js

jquery.fancybox.pack.js

jquery.fancybox.css

default.js

default.css

slick.css

slick-theme.css

slick.min.js

unit_index.css

css

unit_index.js

js

reset.css

hack.css

basiclayout.css

js

analytics.js

header_inner.html

footer.html

btn_scrollup.png

bg_page_wrapper.png

top_img_m2.jpg

btn_news_anime.gif

btn_news.png

weather_base.png

00.png

imp01.jpg

imp02.jpg

slide37.jpg

slide63.jpg

slide62.jpg

slide32.jpg

slide52.jpg

slide61.jpg