19.2 sec in total
3.7 sec
15.3 sec
191 ms
Click here to check amazing Cape House content for Netherlands. Otherwise, check out these important facts you probably never knew about capehouse.com
Cape House Hotel offers the finest in luxury accommodation for both short and long stay guests in the Luangsan area of Bangkok.
Visit capehouse.comWe analyzed Capehouse.com page load time and found that the first response time was 3.7 sec and then it took 15.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
capehouse.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value11.3 s
0/100
25%
Value11.0 s
6/100
10%
Value1,350 ms
17/100
30%
Value0.289
41/100
15%
Value12.9 s
13/100
10%
3656 ms
521 ms
522 ms
1044 ms
1127 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 92% of them (56 requests) were addressed to the original Capehouse.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Capehouse.com.
Page size can be reduced by 450.5 kB (32%)
1.4 MB
952.4 kB
In fact, the total size of Capehouse.com main page is 1.4 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. 20% of websites need less resources to load. Images take 881.9 kB which makes up the majority of the site volume.
Potential reduce by 39.7 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 11.9 kB, which is 25% 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 39.7 kB or 83% of the original size.
Potential reduce by 44.9 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. Cape House images are well optimized though.
Potential reduce by 186.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 186.8 kB or 70% of the original size.
Potential reduce by 179.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. Capehouse.com needs all CSS files to be minified and compressed as it can save up to 179.1 kB or 87% of the original size.
Number of requests can be reduced by 21 (39%)
54
33
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cape House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
capehouse.com
3656 ms
html5shiv.js
521 ms
respond.min.js
522 ms
html5shiv.js
1044 ms
respond.min.js
1127 ms
bootstrap.css
5092 ms
ei-slider.css
1053 ms
crsl-item.css
795 ms
slick.css
1079 ms
camera.css
3382 ms
cape.css
1694 ms
style.css
2496 ms
css
24 ms
SpryMenuBar.js
2638 ms
SpryMenuBarHorizontal.css
1900 ms
jquery-1.11.1.min.js
6171 ms
bootstrap.min.js
5391 ms
jquery.easing.1.3.js
3660 ms
jquery.eislideshow.js
3742 ms
slick.min.js
4212 ms
logo_cape.jpg
273 ms
SpryMenuBarDown.gif
262 ms
capehouse_logo.png
294 ms
youtube_32_s_06.png
336 ms
Flickr%202-32.png
534 ms
facebook_32_s_06.png
539 ms
logoig.png
565 ms
welcome6.jpg
3506 ms
welcome2.jpg
3860 ms
welcome3.jpg
3223 ms
welcome4.jpg
3325 ms
welcome5.jpg
4760 ms
welcome1.jpg
6833 ms
welcome7.jpg
5108 ms
BannerCapeHouse.jpg
4168 ms
2.jpg
4829 ms
3.jpg
4719 ms
4.jpg
4985 ms
head_awards.png
5000 ms
line.png
5026 ms
award.png
5134 ms
award3.png
5270 ms
award2.png
5357 ms
head_cutomer_review.png
5305 ms
w1.png
5388 ms
w2.png
5416 ms
head_connect.png
5545 ms
facebook.png
5576 ms
twitter.png
5627 ms
instragram.png
5656 ms
footer.jpg
5680 ms
analytics.js
8 ms
SpryMenuBarDownHover.gif
5790 ms
SpryMenuBarRightHover.gif
5829 ms
SpryMenuBarRight.gif
5867 ms
collect
13 ms
gk5FxslNkTTHtojXrkp-xF1YPouZEKgzpqZW9wN-3Ek.woff
8 ms
9MkijrV-dEJ0-_NWV7E6N3aqFElqJjV-H5EUExnZgmU.woff
17 ms
ajax-loader.gif
4510 ms
slick.woff
4524 ms
slick.ttf
287 ms
capehouse.com 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-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
Links do not have a discernible name
capehouse.com 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
capehouse.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capehouse.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Capehouse.com 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.
capehouse.com
Open Graph description is not detected on the main page of Cape House. 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: