Tools & Wizards About Us

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

nissan-stadium.jp

日産スタジアム｜横浜国際総合競技場

Page Load Speed

7.3 sec in total

First Response

530 ms

Resources Loaded

6.1 sec

Page Rendered

648 ms

About Website

Click here to check amazing Nissan Stadium content for Japan. Otherwise, check out these important facts you probably never knew about nissan-stadium.jp

日本最大規模の72,327席の観客収容能力を誇る屋外多目的競技場。2002FIFAワールドカップ決勝開催。イベントカレンダー、交通・駐車場案内、周辺案内図、座席案内、ワールドカップスタジアムツアー、スタジアムウエディング等

Visit nissan-stadium.jp

Key Findings

We analyzed Nissan-stadium.jp page load time and found that the first response time was 530 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

nissan-stadium.jp performance score

52

Measured Metrics

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%

Network Requests Diagram

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 266.1 kB (10%)

Content Size

2.7 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

-68%

Potential reduce by 183.6 kB

  • Original 269.5 kB
  • After minification 248.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 183.6 kB or 68% 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 Breakdown

Number of requests can be reduced by 22 (20%)

Requests Now

108

After Optimization

86

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

nissan-stadium.jp accessibility score

67

Accessibility Issues

ARIA

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.

Impact

Issue

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.

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

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

Internationalization and localization

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

Impact

Issue

High

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

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

Form elements do not have associated labels

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

nissan-stadium.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nissan-stadium.jp SEO score

90

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

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

    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

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: