11.7 sec in total
780 ms
10.6 sec
314 ms
Click here to check amazing Pastor content for Japan. Otherwise, check out these important facts you probably never knew about pastor.co.jp
ホテルパストールは、昭和63年9月26日の設立以来、皆様にご愛顧頂いて参りましたが、諸般の事情により平成29年3月31日を持ちましてホテル業務を終了する運びとなりました。
Visit pastor.co.jpWe analyzed Pastor.co.jp page load time and found that the first response time was 780 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pastor.co.jp performance score
780 ms
335 ms
354 ms
354 ms
541 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 82% of them (67 requests) were addressed to the original Pastor.co.jp, 5% (4 requests) were made to Cm.g.doubleclick.net and 2% (2 requests) were made to Img.ak.impact-ad.jp. The less responsive or slowest element that took the longest time to load (7.3 sec) belongs to the original domain Pastor.co.jp.
Page size can be reduced by 72.1 kB (9%)
807.4 kB
735.3 kB
In fact, the total size of Pastor.co.jp main page is 807.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. 20% of websites need less resources to load. Images take 721.7 kB which makes up the majority of the site volume.
Potential reduce by 18.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. This page needs HTML code to be minified as it can gain 2.8 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 18.6 kB or 79% of the original size.
Potential reduce by 8.7 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. Pastor images are well optimized though.
Potential reduce by 32.6 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 32.6 kB or 70% of the original size.
Potential reduce by 12.2 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. Pastor.co.jp needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 80% of the original size.
Number of requests can be reduced by 24 (32%)
75
51
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pastor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pastor.co.jp
780 ms
header.css
335 ms
subnavi.css
354 ms
reservation.css
354 ms
home.css
541 ms
footer.css
540 ms
jquery.min.js
9 ms
jquery.jscrollpane.css
523 ms
jquery.mousewheel.js
683 ms
jquery.jscrollpane.js
1018 ms
jquery.bgswitcher.js
1079 ms
common.js
844 ms
h285_88.jpg
1974 ms
header_roop_1.jpg
657 ms
pastor_logo.jpg
829 ms
btn_english.png
333 ms
btn_kr.png
351 ms
btn_china1.png
384 ms
btn_china2.png
386 ms
btn_facilities.png
668 ms
btn_information.png
699 ms
btn_shop.png
706 ms
btn_access.png
733 ms
btn_contact.png
1000 ms
btn_rooms.jpg
1240 ms
btn_hotspring.jpg
1190 ms
btn_dining.jpg
1254 ms
btn_home.jpg
1435 ms
btn_wedding.jpg
1341 ms
btn_salon.jpg
1502 ms
btn_pool.jpg
1508 ms
gradation.jpg
1592 ms
gradation_w.png
1602 ms
btn_rooms.jpg
2256 ms
btn_hotspring.jpg
2331 ms
btn_dining.jpg
2347 ms
line.jpg
1852 ms
btn_wedding.jpg
2484 ms
btn_salon.jpg
2547 ms
btn_pool.jpg
2770 ms
info.jpg
2987 ms
reservation.jpg
3132 ms
btn_stayplan.jpg
3038 ms
btn_daystayplan.jpg
3222 ms
topics.jpg
3027 ms
topics_prev.jpg
3130 ms
1466024822.jpg
3540 ms
topics_more.jpg
3379 ms
227359345.jpg
3709 ms
mone.285b7b2e3f0_1426.js
450 ms
topics_next.jpg
3142 ms
btn_shop.jpg
3727 ms
btn_access.jpg
3584 ms
banner_FB.png
3575 ms
banner_blog_bardepark.jpg
3344 ms
banner_group.jpg
3613 ms
btn_pagetop.jpg
3421 ms
btn_yoyaku1.jpg
3757 ms
btn_yoyaku2.jpg
3762 ms
combo
169 ms
btn_contact.jpg
3670 ms
pb.html
11 ms
pix
336 ms
pixel
15 ms
306 ms
630 ms
pixel
13 ms
311 ms
logo.jpg
3618 ms
footer.jpg
3846 ms
slider_1.jpg
5115 ms
slider_2.jpg
5488 ms
150 ms
slider_3.jpg
6032 ms
pixel
12 ms
slider_4.jpg
5711 ms
slider_5.jpg
5086 ms
slider_6.jpg
5921 ms
slider_7.jpg
7275 ms
slider_8.jpg
7045 ms
pixel
11 ms
sync
6 ms
pastor.co.jp SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pastor.co.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 Pastor.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.
pastor.co.jp
Open Graph description is not detected on the main page of Pastor. 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: