14.3 sec in total
3.2 sec
10.5 sec
630 ms
Visit capeinfo.com now to see the best up-to-date Capeinfo content for South Africa and also check out these interesting facts you probably never knew about capeinfo.com
Find accommodation during Coronovirus/Covid-19 lockdown: Accommodation, Destinations, Food & Wine and Reviews for southern Africa.
Visit capeinfo.comWe analyzed Capeinfo.com page load time and found that the first response time was 3.2 sec and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
capeinfo.com performance score
name
value
score
weighting
Value10.6 s
0/100
10%
Value14.4 s
0/100
25%
Value16.6 s
0/100
10%
Value890 ms
32/100
30%
Value0.157
74/100
15%
Value21.2 s
1/100
10%
3177 ms
1113 ms
1119 ms
1122 ms
1491 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 76% of them (56 requests) were addressed to the original Capeinfo.com, 4% (3 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Stories.capeinfo.com.
Page size can be reduced by 416.4 kB (26%)
1.6 MB
1.2 MB
In fact, the total size of Capeinfo.com 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 786.9 kB which makes up the majority of the site volume.
Potential reduce by 82.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. 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 82.6 kB or 48% of the original size.
Potential reduce by 4.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. Capeinfo images are well optimized though.
Potential reduce by 318.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 318.6 kB or 40% of the original size.
Potential reduce by 10.5 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. Capeinfo.com has all CSS files already compressed.
Number of requests can be reduced by 45 (67%)
67
22
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capeinfo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
capeinfo.com
3177 ms
content.min.css
1113 ms
style.min.css
1119 ms
style.css
1122 ms
sc_bootstrap.css
1491 ms
font-awesome.min.css
1122 ms
common.css
1127 ms
default.css
1490 ms
bootstrap-tooltip-extended.css
1498 ms
nucleus.css
1499 ms
helium_17.css
1501 ms
bootstrap-gantry.css
1886 ms
joomla.css
1872 ms
icomoon.css
1876 ms
helium-joomla_17.css
1872 ms
custom_17.css
1875 ms
imageeffectck.css
1878 ms
theme.css
2261 ms
custom_styles.css
2251 ms
jquery.min.js
2625 ms
jquery-noconflict.js
2254 ms
jquery-migrate.min.js
2254 ms
caption.js
2278 ms
core.js
2645 ms
bootstrap.min.js
2647 ms
script.min.js
2654 ms
bootstrap-tooltip-extended.min.js
2655 ms
floatingmoduleck.js
2655 ms
js
66 ms
imageeffectck.js
2999 ms
head.load.min.js
2998 ms
adsbygoogle.js
191 ms
main.js
2381 ms
css
33 ms
css
49 ms
css
19 ms
js
125 ms
analytics.js
118 ms
locale-en_GB.js
474 ms
jquery-ui.min.js
1143 ms
jquery.ui.datepicker-en-GB.js
473 ms
jreviews.js
472 ms
jreviews.media.js
474 ms
jreviews.filters.js
473 ms
jreviews.fields.js
863 ms
jreviews.compare.js
862 ms
300x600-success.jpg
3823 ms
capetown.webp
1932 ms
karoo275.jpg
822 ms
CT275.jpg
820 ms
winelands275.jpg
1195 ms
garden-route275.jpg
1197 ms
Agulhas275.jpg
1202 ms
Saldanha_Bay275.jpg
1203 ms
gauteng275.jpg
1493 ms
limpopo275.jpg
1572 ms
kzn275.jpg
1574 ms
Namibia275.jpg
1577 ms
Botswana275.jpg
1580 ms
Mozambique275.jpg
1875 ms
capeinfo-320px-trans.png
1950 ms
show_ads_impl.js
420 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf
356 ms
fa-solid-900.woff
2242 ms
fa-regular-400.woff
1873 ms
BngRUXNadjH0qYEzV7ab-oWlsbCGwRg.ttf
455 ms
collect
297 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
245 ms
jrIcons.woff
1758 ms
collect
132 ms
zrt_lookup.html
58 ms
ads
86 ms
ga-audiences
82 ms
ca-pub-7178841012957880
60 ms
capeinfo.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
capeinfo.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
capeinfo.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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capeinfo.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 Capeinfo.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.
capeinfo.com
Open Graph description is not detected on the main page of Capeinfo. 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: