2.2 sec in total
65 ms
1.9 sec
290 ms
Welcome to cape-town-guide.com homepage info - get ready to check Capetown Guide best content for United States right away, or after learning these important things about cape-town-guide.com
Cape Town travel info. Find your answers in this easy to use travel capetown South Africa guide and discover the Western Cape differently!
Visit cape-town-guide.comWe analyzed Cape-town-guide.com page load time and found that the first response time was 65 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
cape-town-guide.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value4.9 s
28/100
25%
Value5.8 s
50/100
10%
Value70 ms
99/100
30%
Value0.098
90/100
15%
Value3.9 s
88/100
10%
65 ms
111 ms
58 ms
79 ms
75 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 22% of them (26 requests) were addressed to the original Cape-town-guide.com, 23% (27 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (284 ms) belongs to the original domain Cape-town-guide.com.
Page size can be reduced by 1.1 MB (54%)
2.0 MB
923.2 kB
In fact, the total size of Cape-town-guide.com main page is 2.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 62.9 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 62.9 kB or 71% of the original size.
Potential reduce by 6.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. Capetown Guide images are well optimized though.
Potential reduce by 646.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 646.0 kB or 64% of the original size.
Potential reduce by 386.4 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. Cape-town-guide.com needs all CSS files to be minified and compressed as it can save up to 386.4 kB or 86% of the original size.
Number of requests can be reduced by 68 (64%)
106
38
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capetown Guide. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
cape-town-guide.com
65 ms
www.cape-town-guide.com
111 ms
style.css
58 ms
mobile.js
79 ms
fix.js
75 ms
jquery-1.6.1.min.js
35 ms
prettyPhoto.css
54 ms
jquery.prettyPhoto.js
53 ms
plusone.js
121 ms
buttons.js
12 ms
loader.js
7 ms
addthis_widget.js
36 ms
socializeit.js
62 ms
jquery-1.6.1.min.js
93 ms
jquery.prettyPhoto.js
46 ms
prettyPhoto.css
38 ms
cs-wh-234x16.gif
166 ms
body.jpg
24 ms
pagewrap.jpg
21 ms
header.jpg
284 ms
spacer.gif
28 ms
cape-town-guide-dinner.jpg
124 ms
xrss.jpg.pagespeed.ic.tg98uIqgYi.jpg
41 ms
xfeedly.gif.pagespeed.ic.t3Vu8JhVKA.png
42 ms
add-mymsn2.gif
121 ms
xbloglines.gif.pagespeed.ic.vnK-NB9PiG.png
120 ms
vip-concierge-service-column-ad.jpg
121 ms
cb=gapi.loaded_0
51 ms
ga.js
50 ms
cse.js
76 ms
font-awesome.min.css
44 ms
footer.jpg
44 ms
__utm.gif
32 ms
cse.js
183 ms
Hy9W_mrY_Vk
185 ms
font-awesome.min.css
28 ms
collect
154 ms
fontawesome-webfont.woff
138 ms
sdk.js
106 ms
300lo.json
88 ms
getAllAppDefault.esi
226 ms
sh.7c7179124ea24ac6ba46caac.html
32 ms
www-embed-player-vflQrT_sR.css
86 ms
www-embed-player.js
115 ms
base.js
198 ms
160 ms
jsapi
154 ms
xd_arbiter.php
46 ms
xd_arbiter.php
93 ms
getSegment.php
16 ms
checkOAuth.esi
97 ms
default+en.css
87 ms
default.css
99 ms
default+en.I.js
166 ms
t.dhj
132 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
114 ms
ad_status.js
51 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
63 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
105 ms
abtest.d0be1bac1a23ac98ce053e1dd08cc781.html
29 ms
default.css
33 ms
hoverbuttons_reskin.1581f73092bf0aeddc0bb88d0aaa31d0.css
4 ms
hoverbuttons_reskin.3bc05701d07578cfb4db9517abf2dbc2.js
6 ms
t.dhj
65 ms
cm
55 ms
async-ads.js
78 ms
google_custom_search_watermark.gif
70 ms
small-logo.png
59 ms
clear.gif
57 ms
s-3271.xgi
32 ms
23 ms
hbpix
39 ms
19 ms
pixel
18 ms
xrefid.xgi
14 ms
pixel
15 ms
2981
30 ms
buttons.ab966a004186897711de4a5ed256c924.css
27 ms
hbclose.png
22 ms
__utm.gif
17 ms
hbRightArrow.png
12 ms
comments.php
189 ms
facebook_32.png
8 ms
twitter_32.png
7 ms
pinterest_32.png
8 ms
googleplus_32.png
8 ms
xd_arbiter.php
18 ms
like.php
113 ms
vpc6VNjRPXV.js
81 ms
LVx-xkvaJ0b.png
57 ms
roNeOY-tz5Y.css
53 ms
UHhaxo8Cs3k.css
56 ms
46rofGuRiZn.css
64 ms
O8DK6hTywHD.css
71 ms
_rx8naC75Dy.js
80 ms
x5F9OMjKyLw.js
92 ms
ICDbTSzjQEg.js
67 ms
rFmE1g6Dkoz.js
105 ms
7cm7D75Y0Sf.js
101 ms
DKRU1bYTkTw.js
101 ms
LU4a_W5X-JG.js
101 ms
sj-JwAJi4AH.js
102 ms
AunibtBOmSk.js
102 ms
Nvkj5df-gdk.js
102 ms
336JejShbZp.js
102 ms
Q4A0UyjU8W2.js
138 ms
TTCre3391I0.js
139 ms
DnwTulctFaE.js
138 ms
46176_10153900190635625_1469836903364028157_n.jpg
133 ms
like.png
78 ms
fav.png
60 ms
10403036_468414546656175_700585308897973787_n.jpg
130 ms
545255_548021958544082_400038993_n.jpg
63 ms
odA9sNLrE86.jpg
46 ms
wL6VQj7Ab77.png
46 ms
a-ZN6WoEOje.png
47 ms
W0OV23mIOyO.js
13 ms
36TdwhIHusi.js
9 ms
I6-MnjEovm5.js
12 ms
vlXaquuXMrr.js
24 ms
cape-town-guide.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.
cape-town-guide.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
cape-town-guide.com SEO score
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
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cape-town-guide.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 Cape-town-guide.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.
cape-town-guide.com
Open Graph data is detected on the main page of Capetown Guide. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: