8.5 sec in total
550 ms
7.5 sec
468 ms
Visit scapes.jp now to see the best up-to-date SCAPES content for Japan and also check out these interesting facts you probably never knew about scapes.jp
都心から1時間。穏やかな海と深い森を湛える葉山に、静寂と大人の遊び心を併せ持つコンパクトデザインホテル「スケープス ザ スィート」。わずか4部屋の客室は全てオーシャンビュースイート。ミシュランガイドをはじめ、多くの賞を受賞した実績のある、大人の感受性が刺激される宿泊施設。慌ただしい日常から一呼吸。「旅行」とはまた違う「エスケープ」するという体験をご提供します。
Visit scapes.jpWe analyzed Scapes.jp page load time and found that the first response time was 550 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
scapes.jp performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value11.1 s
0/100
25%
Value17.3 s
0/100
10%
Value3,280 ms
2/100
30%
Value0.559
13/100
15%
Value24.9 s
0/100
10%
550 ms
1880 ms
630 ms
800 ms
354 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 42% of them (57 requests) were addressed to the original Scapes.jp, 20% (27 requests) were made to Maps.google.com and 7% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Scapes.jp.
Page size can be reduced by 630.9 kB (40%)
1.6 MB
960.6 kB
In fact, the total size of Scapes.jp main page is 1.6 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. Javascripts take 863.5 kB which makes up the majority of the site volume.
Potential reduce by 79.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 79.1 kB or 82% of the original size.
Potential reduce by 22.2 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. SCAPES images are well optimized though.
Potential reduce by 526.8 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 526.8 kB or 61% of the original size.
Potential reduce by 2.8 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. Scapes.jp needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 76% of the original size.
Number of requests can be reduced by 72 (56%)
129
57
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SCAPES. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and as a result speed up the page load time.
scapes.jp
550 ms
www.scapes.jp
1880 ms
view_css.php
630 ms
jquery-1.7.min.js
800 ms
jquery_prototype.js
354 ms
public.js
357 ms
footer.css
377 ms
reserved.js
674 ms
current.js
679 ms
wideslider.js
693 ms
jquery.flexslider.js
986 ms
jquery.exresize.js
1000 ms
customSelect.jquery.min.js
982 ms
responsive-tables.js
998 ms
slider.js
1029 ms
height.js
1119 ms
switch.js
1302 ms
about.js
1340 ms
bd-KUMFBR-1.js
338 ms
line-button.js
372 ms
js
20 ms
bdash.js
465 ms
tag.js
16 ms
widgets.js
91 ms
hd_lg.png
246 ms
hd_lg_pdp.gif
245 ms
gnav01_off.gif
312 ms
gnav03_off.gif
313 ms
gnav02_off.gif
435 ms
gnav04_off.gif
404 ms
gnav05_off.gif
584 ms
gnav06_off.gif
604 ms
main_Visual01.jpg
1994 ms
main_Visual02.jpg
1905 ms
main_Visual03.jpg
1901 ms
main_Visual04.jpg
1726 ms
mv_logo_scs.png
901 ms
ttl_h2_topics.gif
981 ms
bt_list.gif
1261 ms
ic_media.gif
1357 ms
ic_restaurant.gif
1598 ms
ic_hotel.gif
1685 ms
ic_wedding.gif
1937 ms
ic_banquet.gif
2058 ms
bn_customersVoice.jpg
2231 ms
bn_staffBlog.jpg
2206 ms
bn_media.jpg
2261 ms
bn_thanksparty.jpg
2441 ms
bt_pagetop.gif
2348 ms
ft_lg.png
2413 ms
ft_lgB.png
2526 ms
ft_bt_bland.gif
2569 ms
ft_lgS.gif
2637 ms
all.js
36 ms
bg_head.gif
2697 ms
analytics.js
15 ms
tag
47 ms
collect
29 ms
ft_bg_sns.gif
2657 ms
209 ms
collect
157 ms
xd_arbiter.php
114 ms
xd_arbiter.php
135 ms
ic_arw_blackL.gif
2659 ms
ic_line_black.gif
2712 ms
ya.js
463 ms
conversion_async.js
87 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
149 ms
ic_arw_blackM.gif
2723 ms
ic_arw_blackS.gif
2771 ms
ic_window.gif
2802 ms
30 ms
conversion.js
843 ms
like.php
56 ms
55 ms
share_button.php
62 ms
ZJkxn0orVLU.js
54 ms
FEppCFCt76d.png
40 ms
like.php
78 ms
tweet_button.64a917b4a230f163048902c783e1530f.ja.html
55 ms
ZJkxn0orVLU.js
15 ms
LVx-xkvaJ0b.png
38 ms
ZJkxn0orVLU.js
10 ms
create
150 ms
jot
89 ms
pb.js
529 ms
336 ms
conversion.js
572 ms
921 ms
82x20.png
186 ms
common.js
10 ms
util.js
16 ms
geocoder.js
16 ms
prev.png
187 ms
next.png
187 ms
ic_pager.png
400 ms
AuthenticationService.Authenticate
195 ms
GeocodeService.Search
255 ms
map.js
7 ms
marker.js
7 ms
infowindow.js
79 ms
onion.js
35 ms
openhand_8_8.cur
21 ms
ViewportInfoService.GetViewportInfo
37 ms
stats.js
33 ms
controls.js
27 ms
css
84 ms
transparent.png
18 ms
mapcnt6.png
53 ms
spotlight-poi.png
93 ms
google4.png
39 ms
sv5.png
39 ms
vt
92 ms
vt
89 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
13 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
vt
80 ms
vt
82 ms
vt
82 ms
vt
77 ms
vt
78 ms
vt
90 ms
vt
100 ms
vt
87 ms
vt
88 ms
vt
89 ms
vt
99 ms
vt
88 ms
vt
97 ms
vt
98 ms
vt
105 ms
tmapctrl.png
68 ms
cb_scout5.png
69 ms
tmapctrl4.png
67 ms
imgs8.png
70 ms
scapes.jp accessibility score
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
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.
scapes.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
scapes.jp SEO score
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
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 Scapes.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 Scapes.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.
scapes.jp
Open Graph data is detected on the main page of SCAPES. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: