Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 98% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 88

    SEO

    Google-friendlier than
    71% of websites

bigsight.jp

東京ビッグサイト(東京国際展示場)

Page Load Speed

5.8 sec in total

First Response

375 ms

Resources Loaded

5.3 sec

Page Rendered

130 ms

bigsight.jp screenshot

About Website

Visit bigsight.jp now to see the best up-to-date Bigsight content for Japan and also check out these interesting facts you probably never knew about bigsight.jp

Visit bigsight.jp

Key Findings

We analyzed Bigsight.jp page load time and found that the first response time was 375 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

bigsight.jp performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

bigsight.jp

375 ms

360 ms

css

26 ms

default.css

347 ms

common.css

536 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 98% of them (84 requests) were addressed to the original Bigsight.jp, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Bigsight.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 277.8 kB (9%)

Content Size

3.2 MB

After Optimization

3.0 MB

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

HTML Optimization

-81%

Potential reduce by 27.1 kB

  • Original 33.6 kB
  • After minification 32.1 kB
  • After compression 6.5 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 27.1 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 106.1 kB

  • Original 3.0 MB
  • After minification 2.9 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. Bigsight images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 117.0 kB

  • Original 175.3 kB
  • After minification 169.2 kB
  • After compression 58.4 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 117.0 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 27.7 kB

  • Original 33.8 kB
  • After minification 25.8 kB
  • After compression 6.1 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. Bigsight.jp needs all CSS files to be minified and compressed as it can save up to 27.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (40%)

Requests Now

83

After Optimization

50

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

Accessibility Review

bigsight.jp accessibility score

100

Accessibility Issues

Best Practices

bigsight.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

bigsight.jp SEO score

88

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bigsight.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Bigsight.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 Bigsight. 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: