9.1 sec in total
2.6 sec
6.4 sec
106 ms
Visit kanzan.net now to see the best up-to-date Kanzan content for Japan and also check out these interesting facts you probably never knew about kanzan.net
福岡市、北九州市で飲食店を展開する観山グループのホームページです。観山荘別館、桜坂観山荘、IMURI、西洋菓子工房IMURIとこだわりの素材と技術でサービスを展開しております。
Visit kanzan.netWe analyzed Kanzan.net page load time and found that the first response time was 2.6 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
kanzan.net performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value11.6 s
0/100
25%
Value11.0 s
6/100
10%
Value920 ms
31/100
30%
Value0.383
27/100
15%
Value11.0 s
21/100
10%
2622 ms
1125 ms
92 ms
204 ms
406 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 82% of them (31 requests) were addressed to the original Kanzan.net, 3% (1 request) were made to Googletagmanager.com and 3% (1 request) were made to Webfont.fontplus.jp. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Kanzan.net.
Page size can be reduced by 172.6 kB (22%)
781.4 kB
608.8 kB
In fact, the total size of Kanzan.net main page is 781.4 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. 25% of websites need less resources to load. Images take 441.7 kB which makes up the majority of the site volume.
Potential reduce by 7.8 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 7.8 kB or 69% of the original size.
Potential reduce by 2.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. Kanzan images are well optimized though.
Potential reduce by 157.3 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 157.3 kB or 50% of the original size.
Potential reduce by 5.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. Kanzan.net needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 32% of the original size.
Number of requests can be reduced by 17 (49%)
35
18
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kanzan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
kanzan.net
2622 ms
kanzan.net
1125 ms
gtm.js
92 ms
style.css
204 ms
lightbox.css
406 ms
calendar.css
576 ms
styles.css
584 ms
jquery.js
790 ms
jquery-migrate.min.js
596 ms
fontplus.js
1125 ms
element.js
75 ms
jquery.min.js
50 ms
js
99 ms
xfade3.js
595 ms
lightbox.js
604 ms
ajaxzip3.js
47 ms
kanzan.js
766 ms
scripts.js
775 ms
jquery.optimum-lazy-load.min.js
801 ms
wp-embed.min.js
800 ms
close.png
202 ms
loading.gif
196 ms
prev.png
198 ms
next.png
194 ms
back-img01.png
199 ms
main-img01.jpg
592 ms
main-img02.jpg
961 ms
main-img03.jpg
778 ms
main-img04.jpg
592 ms
homenav0_off.jpg
394 ms
homenav1_off.jpg
399 ms
homenav2_off.jpg
592 ms
homenav4_off.jpg
600 ms
img06.jpg
788 ms
img04.jpg
788 ms
img05.jpg
789 ms
pta.js
27 ms
xfade2.css
531 ms
kanzan.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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.
kanzan.net 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
kanzan.net SEO score
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 Kanzan.net 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 Kanzan.net 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.
kanzan.net
Open Graph data is detected on the main page of Kanzan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: