12.8 sec in total
541 ms
11.9 sec
335 ms
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.jpWe analyzed Tobikan.jp page load time and found that the first response time was 541 ms and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tobikan.jp performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value23.7 s
0/100
25%
Value11.0 s
6/100
10%
Value850 ms
34/100
30%
Value0.296
40/100
15%
Value10.9 s
21/100
10%
541 ms
860 ms
507 ms
346 ms
347 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 96% of them (127 requests) were addressed to the original Tobikan.jp, 2% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Tobikan.jp.
Page size can be reduced by 390.3 kB (12%)
3.3 MB
2.9 MB
In fact, the total size of Tobikan.jp main page is 3.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. 30% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 146.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 146.5 kB or 88% of the original size.
Potential reduce by 86.4 kB
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.
Potential reduce by 117.8 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.8 kB or 64% of the original size.
Potential reduce by 39.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 39.6 kB or 85% of the original size.
Number of requests can be reduced by 38 (29%)
130
92
The browser has sent 130 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 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
tobikan.jp
541 ms
www.tobikan.jp
860 ms
main.css
507 ms
small.css
346 ms
index.css
347 ms
jquery-1.9.1.min.js
876 ms
main.js
379 ms
header.js
677 ms
page.js
528 ms
index_v2.js
545 ms
footer.js
417 ms
analytics.js
77 ms
logo.png
180 ms
lang_jp.png
337 ms
lang_en.png
349 ms
lang_cn.png
350 ms
lang_tw.png
352 ms
lang_kr.png
377 ms
access_s.png
526 ms
weather_s.png
727 ms
twitter_s.png
713 ms
facebook_s.png
715 ms
fontsize_s.png
725 ms
fontsize_l.png
727 ms
icon_dropdown.png
858 ms
btn_alert_close.png
1059 ms
pm243.png
1818 ms
pm244.jpg
1626 ms
pm245.jpg
1637 ms
pm246.jpg
1701 ms
pm248.jpg
1616 ms
pm247.jpg
1898 ms
pm33_1.png
2117 ms
pm36_L.png
1991 ms
pm36_R.png
2003 ms
2016_botticelli.jpg
2577 ms
icon_insession.png
2150 ms
2016_jakuchu_b.jpg
2946 ms
icon_notice2.png
2324 ms
2016_pompidou.jpg
2684 ms
2016_newwave_c.jpg
2950 ms
ac_logo_tobira.png
2516 ms
img141016a.jpg
2870 ms
thumb38.jpg
2848 ms
thumb40.jpg
2925 ms
thumb42.jpg
3017 ms
thumb43.jpg
3209 ms
thumb01.jpg
3151 ms
widgets.js
19 ms
linkid.js
13 ms
collect
31 ms
collect
62 ms
information
3145 ms
thumb02.jpg
2962 ms
rss_s.png
2950 ms
top_auditorium2.jpg
3178 ms
top_artlibrary2.jpg
3371 ms
twitter_m.png
3204 ms
facebook_m.png
3106 ms
weather_m.png
2935 ms
access_m.png
2951 ms
footer_logo.png
3135 ms
fontsize_s_on.png
3212 ms
arrow_r.png
3267 ms
icon_external.png
3164 ms
shadow.png
2997 ms
icon_cal_prev.png
2467 ms
icon_cal_next.png
2609 ms
_visual36.png
3002 ms
_visual.jpg
3719 ms
_visual9.jpg
3409 ms
_visual5.jpg
3472 ms
_visual6.jpg
3395 ms
_visual2.jpg
3847 ms
_visual4.jpg
3979 ms
cal_dayhead.png
3408 ms
line3.png
3379 ms
border_dot.png
3240 ms
icon_pdflink.png
3187 ms
border940.png
3221 ms
icon_arrow_bold_white.png
3203 ms
icon_external_white.png
3251 ms
icon_arrow_up.png
3202 ms
icon_info_news.png
3238 ms
icon_info_topics.png
3298 ms
icon_info_press.png
3365 ms
base_e0e0e0.png
3219 ms
exhibition.csv
3304 ms
calendar.csv
336 ms
icon_day_night.png
176 ms
icon_day_nursery.png
338 ms
cal_day_closed.png
517 ms
icon_day_heart.png
350 ms
icon_day_silver.png
350 ms
cal_ex_41.jpg
358 ms
cal_ex_42a.jpg
524 ms
cal_ex_44a.jpg
684 ms
cal_ex_45a.jpg
701 ms
cal_ac_26.jpg
728 ms
cal_ex_43.jpg
724 ms
cal_ex_46a.jpg
848 ms
cal_ac_25.jpg
900 ms
cal_ac_30.jpg
1018 ms
cal_ex_47.jpg
1058 ms
cal_ex_48.jpg
1056 ms
cal_today.png
1266 ms
cal_circle_purple.png
1180 ms
cal_image_special.png
1234 ms
cal_image_closed.png
1351 ms
cal_image_special_end.png
1407 ms
cal_circle_group.png
1411 ms
cal_image_group.png
1554 ms
cal_image_group_end.png
1567 ms
cal_noimage_blue.png
1607 ms
cal_noimage_blue_end.png
1700 ms
cal_noimage_yellow.png
1767 ms
cal_noimage_yellow_end.png
1776 ms
cal_noimage_green.png
1919 ms
cal_noimage_green_end.png
1933 ms
cal_noimage_red.png
1953 ms
cal_noimage_red_end.png
2041 ms
cal_noimage_pink.png
2137 ms
cal_noimage_pink_end.png
2142 ms
cal_circle_ac.png
2268 ms
cal_noimage_closed.png
2276 ms
cal_image_project.png
2150 ms
cal_image_project_end.png
2047 ms
cal_image_ac_end.png
2132 ms
cal_noimage_tws.png
2149 ms
cal_noimage_tws_end.png
2280 ms
icon_free_mini.png
2132 ms
large.css
168 ms
tobikan.jp accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
tobikan.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
tobikan.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
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: