Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

npb.jp

NPB.jp 日本野球機構

Page Load Speed

7 sec in total

First Response

1.1 sec

Resources Loaded

5.2 sec

Page Rendered

726 ms

npb.jp screenshot

About Website

Click here to check amazing NPB content for Japan. Otherwise, check out these important facts you probably never knew about npb.jp

日本野球機構(NPB)オフィシャルサイト。プロ野球12球団の試合日程・結果や予告先発、ドラフト会議をはじめ、事業・振興に関する情報を掲載。また、オールスター・ゲームや日本シリーズなど主催試合のチケット情報もご覧いただけます。

Visit npb.jp

Key Findings

We analyzed Npb.jp page load time and found that the first response time was 1.1 sec and then it took 5.9 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

npb.jp performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value34.9 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,340 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.337

33/100

15%

TTI (Time to Interactive)

Value24.1 s

0/100

10%

Network Requests Diagram

npb.jp

1064 ms

jquery-1.11.3.min.js

1030 ms

jquery.easing.js

514 ms

jquery.flicksimple.js

512 ms

common.js

355 ms

Our browser made a total of 152 requests to load all elements on the main page. We found that 46% of them (70 requests) were addressed to the original Npb.jp, 47% (72 requests) were made to P.npb.jp and 3% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source P.npb.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 436.6 kB (25%)

Content Size

1.7 MB

After Optimization

1.3 MB

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

HTML Optimization

-83%

Potential reduce by 54.0 kB

  • Original 65.3 kB
  • After minification 57.3 kB
  • After compression 11.3 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 7.9 kB, which is 12% 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 54.0 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 70.6 kB

  • Original 1.3 MB
  • After minification 1.2 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. NPB images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 155.1 kB

  • Original 227.7 kB
  • After minification 215.4 kB
  • After compression 72.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 155.1 kB or 68% of the original size.

CSS Optimization

-92%

Potential reduce by 156.9 kB

  • Original 171.5 kB
  • After minification 152.1 kB
  • After compression 14.5 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. Npb.jp needs all CSS files to be minified and compressed as it can save up to 156.9 kB or 92% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (10%)

Requests Now

146

After Optimization

131

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

Accessibility Review

npb.jp accessibility score

80

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 input fields do not have accessible names

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

npb.jp best practices score

50

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

npb.jp SEO score

89

Search Engine Optimization Advices

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

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 Npb.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 Npb.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 description is not detected on the main page of NPB. 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: