8.3 sec in total
2.6 sec
5.5 sec
311 ms
Welcome to capetocape.net homepage info - get ready to check Cape To best content right away, or after learning these important things about capetocape.net
Follow Johan Wiklund, SAS pilot on an adventure where past and present meet – and where you can help children discover the excitement of learning.
Visit capetocape.netWe analyzed Capetocape.net page load time and found that the first response time was 2.6 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
capetocape.net performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value13.3 s
0/100
25%
Value16.1 s
0/100
10%
Value1,500 ms
14/100
30%
Value0.184
66/100
15%
Value16.8 s
5/100
10%
2566 ms
217 ms
221 ms
223 ms
40 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 54% of them (45 requests) were addressed to the original Capetocape.net, 17% (14 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Capetocape.net.
Page size can be reduced by 1.4 MB (48%)
3.0 MB
1.5 MB
In fact, the total size of Capetocape.net main page is 3.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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 38.5 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 38.5 kB or 77% of the original size.
Potential reduce by 10.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 To images are well optimized though.
Potential reduce by 514.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 514.0 kB or 71% of the original size.
Potential reduce by 873.6 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. Capetocape.net needs all CSS files to be minified and compressed as it can save up to 873.6 kB or 87% of the original size.
Number of requests can be reduced by 44 (66%)
67
23
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cape To. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
capetocape.net
2566 ms
wp-emoji-release.min.js
217 ms
styles.css
221 ms
cff-style.css
223 ms
font-awesome.min.css
40 ms
sb-instagram.css
234 ms
font-awesome.min.css
33 ms
css
38 ms
style.css
225 ms
style.css
234 ms
css
49 ms
style.css
433 ms
shortcodes.css
453 ms
shortcodes_responsive.css
451 ms
magnific_popup.css
437 ms
jetpack.css
446 ms
jquery.js
560 ms
jquery-migrate.min.js
643 ms
frontend-builder-global-functions.js
643 ms
jquery.form.min.js
668 ms
scripts.js
669 ms
cff-scripts.js
732 ms
sb-instagram.js
776 ms
idle-timer.min.js
852 ms
custom.js
858 ms
jquery.uniform.min.js
887 ms
custom.js
890 ms
idle-timer.min.js
956 ms
devicepx-jetpack.js
21 ms
gprofiles.js
72 ms
wpgroho.js
990 ms
custom.js
1071 ms
jquery.fitvids.js
1063 ms
waypoints.min.js
1094 ms
jquery.magnific-popup.js
1109 ms
frontend-builder-scripts.js
1278 ms
wp-embed.min.js
1209 ms
jquery.hashchange.js
1274 ms
e-201611.js
19 ms
style.css
1043 ms
capetcape-200x83.png
226 ms
ctc-banner-frontpage-02.jpg
852 ms
ctc-banner-map1.jpg
492 ms
gallery-011.jpg
642 ms
gallery-021.jpg
777 ms
gallery-031.jpg
634 ms
gallery-04.jpg
849 ms
gallery-05.jpg
1320 ms
gallery-06.jpg
1178 ms
loader.png
851 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
22 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
153 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
155 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
154 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
153 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
153 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
154 ms
ETmodules_v2_4.ttf
1303 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
152 ms
PRmiXeptR36kaC0GEAetxvqEJM-AK1nFUafhVdytxUY.ttf
155 ms
PRmiXeptR36kaC0GEAetxmYImPRL1w80NlYTQ8LOqf4.ttf
154 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
153 ms
PRmiXeptR36kaC0GEAetxk7Gbs5Oj9RrfpUUQRHsz5w.ttf
153 ms
fontawesome-webfont.woff
17 ms
fontawesome-webfont.woff
17 ms
ETmonarch_2.ttf
1026 ms
analytics.js
16 ms
243165347
171 ms
recent
306 ms
hovercard.css
67 ms
services.css
94 ms
collect
15 ms
g.gif
5 ms
gejZBB5xcDU
88 ms
10491169_701405879943093_6517226076568797208_n.jpg
25 ms
www-embed-player-vflfNyN_r.css
39 ms
www-embed-player.js
63 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
33 ms
ad_status.js
26 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
26 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
32 ms
12825955_582117511947026_1215791353_n.jpg
41 ms
12751269_1519986821629765_1199424195_n.jpg
38 ms
12716638_1149592095060258_1807428184_n.jpg
40 ms
capetocape.net 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.
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
<frame> or <iframe> elements do not have a title
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.
capetocape.net 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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
capetocape.net SEO score
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 Capetocape.net 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 Capetocape.net 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.
capetocape.net
Open Graph data is detected on the main page of Cape To. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: