5.6 sec in total
272 ms
5 sec
302 ms
Visit capetravel.com now to see the best up-to-date Cape Travel content and also check out these interesting facts you probably never knew about capetravel.com
Travel to South Africa
Visit capetravel.comWe analyzed Capetravel.com page load time and found that the first response time was 272 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
capetravel.com performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value4.6 s
34/100
25%
Value1.6 s
100/100
10%
Value250 ms
84/100
30%
Value0.179
68/100
15%
Value2.7 s
97/100
10%
272 ms
904 ms
349 ms
203 ms
57 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Capetravel.com, 39% (62 requests) were made to I.ytimg.com and 6% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Login.wn.com.
Page size can be reduced by 2.2 MB (48%)
4.7 MB
2.4 MB
In fact, the total size of Capetravel.com main page is 4.7 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. Only a small number of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 1.1 MB
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 1.1 MB or 85% of the original size.
Potential reduce by 32.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. Cape Travel images are well optimized though.
Potential reduce by 803.1 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 803.1 kB or 65% of the original size.
Potential reduce by 339.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. Capetravel.com needs all CSS files to be minified and compressed as it can save up to 339.2 kB or 80% of the original size.
Number of requests can be reduced by 49 (32%)
151
102
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cape Travel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
capetravel.com
272 ms
Cape_travel
904 ms
0d83a92648f1b7825c11da343d4df6.js
349 ms
2f3af3dd54f3b52809a24014de2ab9.css
203 ms
wnmoviecredits.combined.min.20131104.js
57 ms
videoplayer-20151109-5.min.js
102 ms
anything-events.js
248 ms
platform.js
66 ms
jquery.touchtoclick.js
203 ms
ga.js
42 ms
search-button.png
107 ms
0.jpg
42 ms
wnblack.png
47 ms
loading.gif
107 ms
spreddit7.gif
38 ms
9b64e9f3159f2083ac6a52319a24-medium.jpg
47 ms
a6fab7a50e5ddb5fc5ec9846bfab-medium.jpg
147 ms
f00c7a5c033a4d8a30a5414ebec2-medium.jpg
104 ms
0.jpg
149 ms
0.jpg
39 ms
0.jpg
39 ms
0.jpg
43 ms
0.jpg
40 ms
0.jpg
146 ms
0.jpg
150 ms
0.jpg
98 ms
0.jpg
97 ms
0.jpg
100 ms
0.jpg
143 ms
0.jpg
142 ms
0.jpg
278 ms
0.jpg
155 ms
0.jpg
288 ms
0.jpg
151 ms
0.jpg
275 ms
0.jpg
152 ms
0.jpg
285 ms
0.jpg
282 ms
0.jpg
272 ms
0.jpg
277 ms
0.jpg
278 ms
0.jpg
279 ms
0.jpg
282 ms
0.jpg
284 ms
0.jpg
365 ms
0.jpg
286 ms
0.jpg
340 ms
0.jpg
364 ms
0.jpg
338 ms
0.jpg
363 ms
0.jpg
364 ms
0.jpg
363 ms
0.jpg
364 ms
logo.png
134 ms
712.GIF
281 ms
f794e254899eebb5bddfbf81b95d-medium.jpg
132 ms
43fc9cb3de06c5ba8cbdd9c98e35-medium.jpg
132 ms
sdk.js
68 ms
113px-Inverness_cape_07Tac_401.jpg
115 ms
120px-El_viaxeru_d%27Urculo.JPG
116 ms
0.jpg
740 ms
0.jpg
712 ms
0.jpg
739 ms
0.jpg
736 ms
0.jpg
735 ms
__utm.gif
64 ms
__utm.gif
52 ms
iconSprite.png
61 ms
0.jpg
680 ms
0.jpg
677 ms
0.jpg
1621 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
48 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
48 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
50 ms
4cKlrioa77J2iqTqBgkRWg.ttf
48 ms
fontawesome-webfont.woff
184 ms
0.jpg
1578 ms
0.jpg
639 ms
0.jpg
638 ms
0.jpg
1450 ms
0.jpg
633 ms
0.jpg
1565 ms
0.jpg
1564 ms
0.jpg
1562 ms
widgets.js
24 ms
share-button.js
508 ms
0.jpg
1445 ms
0.jpg
1603 ms
0.jpg
1609 ms
0.jpg
1620 ms
0.jpg
1605 ms
0.jpg
1598 ms
0.jpg
1596 ms
0.jpg
1678 ms
0.jpg
1677 ms
0.jpg
1674 ms
1608 ms
xd_arbiter.php
394 ms
xd_arbiter.php
427 ms
iframe_api
1110 ms
modal-gloss.png
1135 ms
wn_logo.png
1133 ms
p.js
1177 ms
quant.js
1178 ms
__utm.gif
701 ms
iconSprite01.png
848 ms
playPrev-button.png
928 ms
playNext-button.png
688 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
504 ms
cb=gapi.loaded_0
312 ms
cb=gapi.loaded_1
385 ms
fastbutton
379 ms
1691 ms
1626 ms
www-widgetapi.js
222 ms
button
486 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
110 ms
postmessageRelay
364 ms
pixel;r=517915622;a=p-69LMgINxZpq8g;labels=wn.anything.main;fpan=1;fpa=P0-957402439-1458471787029;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458471787029;tzo=-180;ref=;url=http%3A%2F%2Fwn.com%2Fcape_travel;ogl=title.Cape%20Travel%2Curl.http%3A%2F%2Fwn%252Ecom%2FCape_Travel%2Cimage.http%3A%2F%2Fi%252Eytimg%252Ecom%2Fvi%2Fk3aw7gbGNt8%2F0%252Ejpg%2Csite_name.World%20News%2Cvideo.http%3A%2F%2Fwww%252Eyoutube-nocookie%252Ecom%2Fv%2Fk3aw7gbGNt8%2Cvideo%3Aheight.240%2Cvideo%3Awidth.320%2Cvideo%3Atype.application%2Fx-shockwave-flash
117 ms
cb=gapi.loaded_0
96 ms
cb=gapi.loaded_1
94 ms
like.php
155 ms
wn.com
119 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
371 ms
like.php
310 ms
k3aw7gbGNt8
571 ms
IqAlRWHWbfk
785 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
130 ms
6RJXxUEi5lM
938 ms
styles.css
221 ms
rapid-3.36.js
313 ms
rapidworker-1.2.js
316 ms
index.js
553 ms
qeKvIRsJabD.js
723 ms
LVx-xkvaJ0b.png
751 ms
like.php
315 ms
like.php
334 ms
ptrack-v0.4.10-engaged-time.js
161 ms
3193398744-postmessagerelay.js
587 ms
rpc:shindig_random.js
118 ms
ga.js
549 ms
analytics.js
516 ms
beacon.js
548 ms
impixu
550 ms
271 ms
yql
1043 ms
www-embed-player-vflfNyN_r.css
329 ms
www-embed-player.js
482 ms
base.js
516 ms
3d-t-button-white.svg
117 ms
cb=gapi.loaded_0
214 ms
__utm.gif
280 ms
__utm.gif
359 ms
__utm.gif
418 ms
__utm.gif
417 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
284 ms
ad_status.js
292 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
93 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
127 ms
jot.html
65 ms
cedexis.radar.js
42 ms
capetravel.com 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.
capetravel.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
capetravel.com SEO score
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capetravel.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Capetravel.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.
capetravel.com
Open Graph description is not detected on the main page of Cape Travel. 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: