4.3 sec in total
684 ms
3.4 sec
166 ms
Click here to check amazing Ytmoca content for Japan. Otherwise, check out these important facts you probably never knew about ytmoca.jp
横尾忠則現代美術館は、兵庫県西脇市出身の美術家、横尾忠則からの寄贈・寄託作品を適切な環境で保管し、多くの人に鑑賞していただくため、兵庫県立美術館王子分館(旧兵庫県立近代美術館、村野藤吾設計)の西館をリニューアルし、2012年11月に開館いたしました。
Visit ytmoca.jpWe analyzed Ytmoca.jp page load time and found that the first response time was 684 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ytmoca.jp performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value15.9 s
0/100
25%
Value22.6 s
0/100
10%
Value1,210 ms
20/100
30%
Value0.135
80/100
15%
Value21.4 s
1/100
10%
684 ms
348 ms
519 ms
2209 ms
370 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 44% of them (34 requests) were addressed to the original Ytmoca.jp, 24% (19 requests) were made to Static.xx.fbcdn.net and 13% (10 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Ytmoca.jp.
Page size can be reduced by 43.9 kB (9%)
464.7 kB
420.8 kB
In fact, the total size of Ytmoca.jp main page is 464.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 418.1 kB which makes up the majority of the site volume.
Potential reduce by 5.6 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 5.6 kB or 63% of the original size.
Potential reduce by 5.9 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. Ytmoca images are well optimized though.
Potential reduce by 32.4 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. Ytmoca.jp needs all CSS files to be minified and compressed as it can save up to 32.4 kB or 86% of the original size.
Number of requests can be reduced by 38 (49%)
77
39
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ytmoca. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
ytmoca.jp
684 ms
import.css
348 ms
logo.gif
519 ms
top_img.jpg
2209 ms
topics.gif
370 ms
exb.gif
334 ms
events.gif
356 ms
common.css
840 ms
margin.css
374 ms
page.css
813 ms
widgets.js
80 ms
menu01_off.gif
178 ms
menu02_off.gif
177 ms
menu03_off.gif
466 ms
menu04_off.gif
465 ms
menu05_off.gif
465 ms
menu06_off.gif
639 ms
menu07_off.gif
638 ms
menu08_off.gif
807 ms
menu09_off.gif
806 ms
title01.gif
814 ms
title02.gif
973 ms
link01_off.gif
974 ms
link02_off.gif
1146 ms
link03_off.gif
1147 ms
link04_off.gif
1148 ms
link05_off.gif
1297 ms
f_menu01_off.gif
1328 ms
f_menu02_off.gif
1332 ms
f_menu03_off.gif
1480 ms
f_menu04_off.gif
1488 ms
f_menu05_off.gif
1509 ms
f_menu06_off.gif
1617 ms
copyright.gif
1683 ms
f_menu07_off.gif
1695 ms
likebox.php
176 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
130 ms
410ucuAGgaJ.css
53 ms
tSbl8xBI27R.css
75 ms
Czh0gDTFcBt.css
55 ms
Ek6lpayKeeB.css
66 ms
Pa4LYC3smxF.js
73 ms
FJmpeSpHpjS.js
99 ms
0wM5s1Khldu.js
99 ms
1bNoFZUdlYZ.js
65 ms
njO1TPvGzoR.js
116 ms
1QuX41zDRrx.js
116 ms
Oagsvfb4VWi.js
115 ms
LTv6ZK-5zxz.js
131 ms
1FCa-btixu2.js
115 ms
syndication
246 ms
313887354857324545
376 ms
12294613_1016538185034613_7073427699262412557_n.jpg
139 ms
525625_535505273137909_1451341093_n.jpg
77 ms
10371520_1074782605876837_5351040118330289038_n.jpg
141 ms
1914648_1072885866066511_3082062236489639704_n.jpg
70 ms
1916676_1070308549657576_626591740568834608_n.jpg
69 ms
12717908_1069271439761287_8112633604452917921_n.jpg
69 ms
12670923_1067074259981005_2164025415092077102_n.jpg
69 ms
wL6VQj7Ab77.png
25 ms
s7jcwEQH7Sx.png
27 ms
QDwYpIaRyfG.png
25 ms
K00K-UgnsKu.png
26 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
12 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
27 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
108 ms
1cf1302efeefcf1ab95d209d1391ab5c_normal.jpeg
230 ms
CdynoP4UIAEwv6F.jpg:small
503 ms
CdkPCqTVIAAG0Uj.jpg:small
417 ms
CdOweVeVAAAa1XL.jpg:small
474 ms
CdEYXEzUEAANjcE.jpg:small
429 ms
CcvyTwbUYAAYqWs.jpg:small
503 ms
CcmOSj9UkAALkd5.jpg:small
439 ms
Ccbmx6LVAAEAbc0.jpg:small
464 ms
CcNgXBSUkAA85ru.jpg:small
482 ms
CcL6Ye_VAAAGeIJ.jpg:small
489 ms
jot
25 ms
ytmoca.jp accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ytmoca.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
Browser errors were logged to the console
ytmoca.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ytmoca.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 Ytmoca.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.
ytmoca.jp
Open Graph description is not detected on the main page of Ytmoca. 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: