7.5 sec in total
720 ms
6.4 sec
395 ms
Click here to check amazing Yokokan content. Otherwise, check out these important facts you probably never knew about yokokan.co.jp
井県・福井市・福井駅西口より徒歩3分の好立地、福井フェニックスホテル。高級なロイヤルルーム、女性にやさしいレディースルーム、地元の食材を活かしたお料理などハイクオリティーなおもてなしをご提供いたします。
Visit yokokan.co.jpWe analyzed Yokokan.co.jp page load time and found that the first response time was 720 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
yokokan.co.jp performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value8.1 s
2/100
25%
Value12.0 s
4/100
10%
Value440 ms
64/100
30%
Value0
100/100
15%
Value5.9 s
65/100
10%
720 ms
317 ms
357 ms
362 ms
368 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 60% of them (52 requests) were addressed to the original Yokokan.co.jp, 16% (14 requests) were made to Maps.google.com and 10% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Yokokan.co.jp.
Page size can be reduced by 529.1 kB (16%)
3.3 MB
2.8 MB
In fact, the total size of Yokokan.co.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. 50% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 9.0 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 9.0 kB or 70% of the original size.
Potential reduce by 24.5 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. Yokokan images are well optimized though.
Potential reduce by 477.0 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 477.0 kB or 67% of the original size.
Potential reduce by 18.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. Yokokan.co.jp needs all CSS files to be minified and compressed as it can save up to 18.6 kB or 78% of the original size.
Number of requests can be reduced by 50 (61%)
82
32
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yokokan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.yokokan.co.jp
720 ms
Common.css
317 ms
Cookie.js
357 ms
Dom.js
362 ms
Event.js
368 ms
File.js
371 ms
Flash.js
378 ms
Form.js
631 ms
Image.js
688 ms
Numeric.js
706 ms
Opacity.js
705 ms
Platform.js
722 ms
Style.js
725 ms
Text.js
943 ms
Window.js
1019 ms
XmlHttpObject.js
1040 ms
jquery-1.11.3.min.js
1278 ms
jquery.bxslider.js
1107 ms
jquery.bxslider.css
1090 ms
jquery.colorbox.1.6.1.min.js
1285 ms
colorbox.css
1354 ms
common.js
1393 ms
style.css
1454 ms
script.js
1436 ms
js
31 ms
Layout.css
1314 ms
Text.css
1326 ms
Anchor.css
1390 ms
List.css
1421 ms
Calendar.css
1460 ms
Tab.css
1485 ms
Image.css
1645 ms
Form.css
1646 ms
Print.css
1725 ms
analytics.js
73 ms
366 ms
Background.jpg
808 ms
Background.jpg
508 ms
Title.png
362 ms
Yokokan.jpg
535 ms
News.png
909 ms
Policy.png
1125 ms
Menu.png
1206 ms
Shop.png
1327 ms
Telephone.png
963 ms
PointCard.jpg
1294 ms
FukuiPhoenixHotel.jpg
1445 ms
Main.jpg
2386 ms
Policy.jpg
2694 ms
Menu.jpg
2859 ms
Shop.jpg
2661 ms
News.png
1679 ms
overlay.png
1806 ms
bx_loader.gif
2078 ms
collect
3 ms
collect
78 ms
collect
7 ms
common.js
16 ms
map.js
9 ms
util.js
62 ms
marker.js
6 ms
StaticMapService.GetMapImage
158 ms
onion.js
21 ms
openhand_8_8.cur
47 ms
ViewportInfoService.GetViewportInfo
40 ms
stats.js
36 ms
controls.js
33 ms
infowindow.js
53 ms
transparent.png
38 ms
css
36 ms
google4.png
61 ms
mapcnt6.png
24 ms
spotlight-poi.png
25 ms
vt
63 ms
vt
62 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
9 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
13 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
12 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
12 ms
vt
79 ms
vt
64 ms
vt
78 ms
tmapctrl.png
18 ms
cb_scout5.png
18 ms
tmapctrl4.png
19 ms
imgs8.png
16 ms
AuthenticationService.Authenticate
195 ms
yokokan.co.jp 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.
yokokan.co.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
yokokan.co.jp SEO score
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
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yokokan.co.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 Yokokan.co.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.
yokokan.co.jp
Open Graph description is not detected on the main page of Yokokan. 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: