11.3 sec in total
1.9 sec
9 sec
456 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 1.9 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ytmoca.jp performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value12.3 s
0/100
25%
Value29.8 s
0/100
10%
Value11,210 ms
0/100
30%
Value1.019
2/100
15%
Value45.2 s
0/100
10%
1856 ms
503 ms
29 ms
601 ms
603 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 64% of them (48 requests) were addressed to the original Ytmoca.jp, 24% (18 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Ytmoca.jp.
Page size can be reduced by 543.0 kB (17%)
3.2 MB
2.7 MB
In fact, the total size of Ytmoca.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. 70% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 72.2 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 72.2 kB or 71% of the original size.
Potential reduce by 45.3 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 234.5 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 234.5 kB or 41% of the original size.
Potential reduce by 191.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. Ytmoca.jp needs all CSS files to be minified and compressed as it can save up to 191.1 kB or 88% of the original size.
Number of requests can be reduced by 53 (77%)
69
16
The browser has sent 69 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 39 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
ytmoca.jp
1856 ms
base.css
503 ms
jquery.min.js
29 ms
slick-theme.css
601 ms
slick.css
603 ms
smooth.pack.js
702 ms
common.js
701 ms
slick.min.js
972 ms
js
87 ms
style.min.css
1321 ms
style.css
901 ms
styles.css
900 ms
styles.css
997 ms
style.css
1067 ms
blocks.css
1072 ms
jquery.min.js
1314 ms
jquery-migrate.min.js
1151 ms
widgets.js
44 ms
sdk.js
36 ms
index.js
1070 ms
index.js
1081 ms
jquery.form.min.js
1256 ms
scripts.js
1256 ms
skip-link-focus-fix.js
1256 ms
global.js
1320 ms
jquery.scrollTo.js
1327 ms
api.js
58 ms
wp-polyfill-inert.min.js
1327 ms
regenerator-runtime.min.js
1411 ms
wp-polyfill.min.js
1770 ms
index.js
1491 ms
h1.svg
317 ms
btn_twitter.png
486 ms
btn_fb.png
386 ms
btn_instagram.png
480 ms
btn_youtube.png
490 ms
HP%E3%83%88%E3%83%83%E3%83%97%E7%94%BB%E9%9D%A2%E7%94%A8.jpg
1612 ms
IMG_1970.jpg
889 ms
1C-82.jpg
994 ms
top_30.jpg
2700 ms
top09.jpg
1189 ms
arrow01.png
758 ms
B1%EF%BC%88%E6%9C%80%E7%B5%82%EF%BC%89_mini.jpg
1108 ms
returntop.png
1055 ms
h1_2.svg
1165 ms
NotoSansCJKjp-Regular.otf
3024 ms
NotoSansCJKjp-Bold.otf
3320 ms
sdk.js
13 ms
40 ms
recaptcha__en.js
25 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
31 ms
settings
72 ms
btn_prev.png
610 ms
btn_next.png
634 ms
ajax-loader.gif
2547 ms
slick.woff
2333 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
3 ms
YTmocaStaff
859 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
10 ms
runtime-b1c52fd0a13ead5fcf6b.js
24 ms
modules-96ebc7ac3ad66d681a3d.js
48 ms
main-babd9234dc048fb47339.js
14 ms
_app-a9c9f1a99e4414675fb1.js
13 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
47 ms
_buildManifest.js
23 ms
_ssgManifest.js
111 ms
8526.0c32a8f0cfc5749221a3.js
16 ms
1755.07a49c40b12af4f75780.js
15 ms
8283.f3e5048cca7cef5eed7f.js
3 ms
3077.44bfeb00af01bc4020f6.js
12 ms
1362.42d432e02f7980bca032.js
25 ms
4956.c4e51ef593974b9db0bb.js
25 ms
5893.d500bd2a89ded806aa73.js
24 ms
slick.ttf
1464 ms
slick.svg
169 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
JA
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 it matches the claimed language. 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: