Tools & Wizards About Us
tobikan.jp screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

tobikan.jp

東京都美術館

Page Load Speed

10.6 sec in total

First Response

527 ms

Resources Loaded

9.8 sec

Page Rendered

237 ms

tobikan.jp screenshot

About Website

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

東京都美術館の公式サイトです。「スコットランド国立美術館　THE GREATS　美の巨匠たち」、「ボストン美術館展　芸術×力」、「フィン・ユールとデンマークの椅子」、「展覧会 岡本太郎」など、多彩なラインナップで古今東西の美をお届けします。

Visit tobikan.jp

Key Findings

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

Performance Metrics

tobikan.jp performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.504

16/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

tobikan.jp

527 ms

www.tobikan.jp

1113 ms

v3.css

1191 ms

jquery-3.5.1.min.js

1026 ms

jquery.transit.min.js

515 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 90% of them (70 requests) were addressed to the original Tobikan.jp, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Tobikan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.5 kB (14%)

Content Size

2.3 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 37.3 kB

  • Original 48.7 kB
  • After minification 46.1 kB
  • After compression 11.4 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 37.3 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 54.2 kB

  • Original 1.9 MB
  • After minification 1.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. Tobikan images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 111.7 kB

  • Original 186.8 kB
  • After minification 185.9 kB
  • After compression 75.0 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 111.7 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 108.2 kB

  • Original 128.8 kB
  • After minification 111.9 kB
  • After compression 20.6 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. Tobikan.jp needs all CSS files to be minified and compressed as it can save up to 108.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (46%)

Requests Now

76

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tobikan.jp

tobikan.jp

527 ms

www.tobikan.jp

www.tobikan.jp

1113 ms

v3.css

v3.css

1191 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

1026 ms

jquery.transit.min.js

jquery.transit.min.js

515 ms

v3.js

v3.js

857 ms

js

js

57 ms

v3.header.js

v3.header.js

530 ms

v3.index.js

v3.index.js

686 ms

sdk.js

sdk.js

13 ms

v3.footer.js

v3.footer.js

868 ms

btn_alert_close.png

btn_alert_close.png

375 ms

dummy.png

dummy.png

517 ms

2024_daichinimimi.jpg

2024_daichinimimi.jpg

1715 ms

2024_issontanaka.jpg

2024_issontanaka.jpg

1406 ms

2024_groupshow.jpg

2024_groupshow.jpg

1056 ms

ac_logo_tobira.png

ac_logo_tobira.png

885 ms

img141016a.jpg

img141016a.jpg

1081 ms

thumb106.jpg

thumb106.jpg

1222 ms

thumb105.jpg

thumb105.jpg

1421 ms

thumb107.jpg

thumb107.jpg

1587 ms

thumb84.jpg

thumb84.jpg

1612 ms

thumb01.jpg

thumb01.jpg

1767 ms

thumb02.jpg

thumb02.jpg

1933 ms

rss_s.png

rss_s.png

1934 ms

x_s.png

x_s.png

2118 ms

facebook_s.png

facebook_s.png

2141 ms

instagram_s.png

instagram_s.png

2224 ms

banner_x.jpg

banner_x.jpg

2497 ms

banner_in.jpg

banner_in.jpg

2618 ms

top_auditorium3.jpg

top_auditorium3.jpg

2846 ms

top_artlibrary3.jpg

top_artlibrary3.jpg

2970 ms

logo.png

logo.png

2761 ms

lang_jp.png

lang_jp.png

2676 ms

lang_en.png

lang_en.png

2984 ms

lang_cn.png

lang_cn.png

3070 ms

lang_tw.png

lang_tw.png

3226 ms

lang_kr.png

lang_kr.png

3275 ms

access_s.png

access_s.png

3316 ms

weather_s.png

weather_s.png

3455 ms

fontsize_s_on.png

fontsize_s_on.png

3529 ms

fontsize_l.png

fontsize_l.png

3583 ms

icon_dropdown.png

icon_dropdown.png

3757 ms

base.png

base.png

5158 ms

_visual.jpg

_visual.jpg

4953 ms

_visual2.jpg

_visual2.jpg

4863 ms

_visual4.jpg

_visual4.jpg

4731 ms

js

js

39 ms

sdk.js

sdk.js

8 ms

analytics.js

analytics.js

28 ms

34 ms

collect

collect

11 ms

collect

collect

11 ms

exhibition.csv

exhibition.csv

3786 ms

base_e0e0e0.png

base_e0e0e0.png

3816 ms

icon_cal_prev.png

icon_cal_prev.png

3786 ms

icon_cal_next.png

icon_cal_next.png

3790 ms

cal_dayhead.png

cal_dayhead.png

4140 ms

arrow_r.png

arrow_r.png

4102 ms

bg_info_news.png

bg_info_news.png

3953 ms

icon_external_wine.png

icon_external_wine.png

4017 ms

information

information

3982 ms

bg_info_topics.png

bg_info_topics.png

4138 ms

bg_info_recruit.png

bg_info_recruit.png

4052 ms

icon_arrow_up.png

icon_arrow_up.png

4070 ms

icon_arrow_bold_white.png

icon_arrow_bold_white.png

3941 ms

icon_external_white.png

icon_external_white.png

4015 ms

footer_logox2.png

footer_logox2.png

3967 ms

access_l.png

access_l.png

4138 ms

weather_l.png

weather_l.png

4056 ms

x_l.png

x_l.png

3850 ms

facebook_l.png

facebook_l.png

3786 ms

instagram_l.png

instagram_l.png

3724 ms

logo_translator.png

logo_translator.png

3944 ms

logo_culturefromhome.png

logo_culturefromhome.png

4284 ms

logo_museumcollection.png

logo_museumcollection.png

3992 ms

logo_tomuco.png

logo_tomuco.png

4007 ms

logo_donation.png

logo_donation.png

3981 ms

Accessibility Review

tobikan.jp accessibility score

85

Accessibility Issues

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

Best Practices

tobikan.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Browser errors were logged to the console

SEO Factors

tobikan.jp SEO score

90

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

tobikan.jp

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