6.8 sec in total
1.2 sec
5.4 sec
253 ms
Visit shiinoki-geihinkan.jp now to see the best up-to-date Shiinoki Geihinkan content for Japan and also check out these interesting facts you probably never knew about shiinoki-geihinkan.jp
ようこそ、おもてなしの空間へ。石川県政記念 しいのき迎賓館
Visit shiinoki-geihinkan.jpWe analyzed Shiinoki-geihinkan.jp page load time and found that the first response time was 1.2 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
shiinoki-geihinkan.jp performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value11.7 s
0/100
25%
Value8.7 s
17/100
10%
Value250 ms
84/100
30%
Value0.046
99/100
15%
Value8.5 s
38/100
10%
1212 ms
373 ms
566 ms
401 ms
361 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 61% of them (62 requests) were addressed to the original Shiinoki-geihinkan.jp, 30% (31 requests) were made to Pbs.twimg.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Shiinoki-geihinkan.jp.
Page size can be reduced by 107.2 kB (4%)
2.5 MB
2.4 MB
In fact, the total size of Shiinoki-geihinkan.jp main page is 2.5 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 2.4 MB which makes up the majority of the site volume.
Potential reduce by 15.1 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 15.1 kB or 73% of the original size.
Potential reduce by 44.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. Shiinoki Geihinkan images are well optimized though.
Potential reduce by 7.2 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 7.2 kB or 26% of the original size.
Potential reduce by 40.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. Shiinoki-geihinkan.jp needs all CSS files to be minified and compressed as it can save up to 40.6 kB or 85% of the original size.
Number of requests can be reduced by 27 (27%)
100
73
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shiinoki Geihinkan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
shiinoki-geihinkan.jp
1212 ms
action.js
373 ms
swfobject.js
566 ms
import.css
401 ms
flash.js
361 ms
jsRSS.cgi
825 ms
index.cgi
308 ms
index.cgi
302 ms
common.css
190 ms
layout.css
370 ms
base.css
1264 ms
event.css
338 ms
english.css
348 ms
ga.js
19 ms
bg_header.gif
410 ms
space.gif
193 ms
icon_arrow1.gif
201 ms
bg_ixnavi.gif
192 ms
01_n.gif
196 ms
02_n.gif
165 ms
03_n.gif
327 ms
04_n.gif
379 ms
05_n.gif
376 ms
06_n.gif
392 ms
flash.jpg
1801 ms
shiinoki-facebook.gif
510 ms
bt_kenrokumori02.gif
566 ms
hot-ishikawa.gif
795 ms
world-heritage.gif
678 ms
syouhi-henkou.gif
678 ms
eventbtn_n.gif
745 ms
accessbtn.gif
746 ms
floorbtn.gif
795 ms
pdfbtn_j.gif
819 ms
pdfbtn_e.gif
842 ms
getacrobat.gif
927 ms
selectshop.jpg
1504 ms
cb_paul_bocuse.gif
976 ms
j_paul_bocuse.gif
1022 ms
ucl.gif
1004 ms
unu.gif
1112 ms
freespot.gif
1170 ms
bg_infor.gif
1156 ms
__utm.gif
20 ms
ixrblogsub.gif
1196 ms
widgets.js
82 ms
ixarndsub.gif
1258 ms
ix_evtsub.gif
1291 ms
bg_eventbox.gif
1326 ms
000001.jpg
2657 ms
icon_list.gif
1438 ms
5.gif
1450 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
125 ms
000211.jpg
1791 ms
000212.jpg
1664 ms
ix_glysub.gif
1467 ms
000249.jpg
2442 ms
1.gif
1623 ms
syndication
94 ms
346873305271263232
199 ms
000250.jpg
1677 ms
000251.jpg
2099 ms
000252.jpg
2032 ms
000254.jpg
1760 ms
000253.jpg
1795 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
29 ms
2.gif
1837 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
55 ms
______normal.JPG
201 ms
Cd4Rh1cUMAEaHlU.jpg:small
246 ms
Cdu5WBOUkAAo2dc.jpg:small
358 ms
CdpWh-DW0AAeCTA.jpg:small
339 ms
Cde5ZuWUAAAlXK-.jpg:small
328 ms
CdQA5K9UkAQDdtQ.jpg:small
419 ms
CcrXLyaUAAAne1t.jpg:small
431 ms
CcRJCGwUMAAg0x9.jpg:small
357 ms
CcMYwnJUUAEfM0M.jpg:small
447 ms
CcH5TImVIAEaMFp.jpg:small
608 ms
CcCV7U2UsAE4Xy7.jpg:small
452 ms
CbpAsrEUcAA2Z4P.jpg:small
535 ms
CdUJxA2UsAAq0il.jpg:small
508 ms
CdUJxN9UYAAP6uu.jpg:small
500 ms
CdABhcoVIAA18BK.jpg:small
472 ms
CdABhl-UkAAe16U.jpg:small
651 ms
Cc1pTBmUkAAZbZb.jpg:small
543 ms
Cc1pTFdUEAE-yYb.jpg:small
683 ms
CcmJAQOUMAAlHlR.jpg:small
658 ms
CcmJAXeUsAEBfyc.jpg:small
642 ms
CcmI_3OVAAAdDVi.jpg:small
636 ms
CcmI_bfUcAAjo3W.jpg:small
703 ms
Ccci-czVAAAdlXe.jpg:small
806 ms
Ccci9VaUcAAMpDu.jpg:small
715 ms
Ccci6HQVIAA7qwd.jpg:small
723 ms
CcHMxzVUEAAZDLi.jpg:small
1062 ms
CcHMxixUAAIVT2J.jpg:small
790 ms
Cb8-uN9UYAED3dd.jpg:small
1002 ms
Cb8-vKaUUAAHKgt.jpg:small
817 ms
Cbt9wewUcAE9R2N.jpg:small
888 ms
Cbt9wyiUAAAbX0t.jpg:small
926 ms
ixopensub.gif
1837 ms
ixshopsub.gif
1863 ms
jot
24 ms
shiinoki-geihinkan.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 input fields do not have accessible names
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>).
shiinoki-geihinkan.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
shiinoki-geihinkan.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shiinoki-geihinkan.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 Shiinoki-geihinkan.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
shiinoki-geihinkan.jp
Open Graph description is not detected on the main page of Shiinoki Geihinkan. 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: