6.3 sec in total
499 ms
4.5 sec
1.3 sec
Click here to check amazing Capital content for Germany. Otherwise, check out these important facts you probably never knew about capital.com
Enjoy online trading like never before. With Capital.com’s app, you can discover investment opportunities on leading financial markets. Access the latest trading insights at the touch of a button, as ...
Visit capital.comWe analyzed Capital.com page load time and found that the first response time was 499 ms 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.
capital.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value7.6 s
4/100
25%
Value7.3 s
28/100
10%
Value1,050 ms
25/100
30%
Value0.018
100/100
15%
Value12.5 s
14/100
10%
499 ms
31 ms
26 ms
33 ms
36 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 54% of them (41 requests) were addressed to the original Capital.com, 7% (5 requests) were made to Googleads.g.doubleclick.net and 7% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Capital.com.
Page size can be reduced by 146.2 kB (59%)
245.8 kB
99.6 kB
In fact, the total size of Capital.com main page is 245.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 188.7 kB which makes up the majority of the site volume.
Potential reduce by 34.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 34.6 kB or 75% of the original size.
Potential reduce by 401 B
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. Capital images are well optimized though.
Potential reduce by 110.7 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 110.7 kB or 59% of the original size.
Potential reduce by 538 B
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. Capital.com needs all CSS files to be minified and compressed as it can save up to 538 B or 61% of the original size.
Number of requests can be reduced by 33 (57%)
58
25
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capital. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
www.capital.com
499 ms
style.css
31 ms
modernizr-2.0.6.min.js
26 ms
styles.css
33 ms
l10n.js
36 ms
jquery.js
43 ms
track.aspx
85 ms
show_ads.js
28 ms
infeed.min.js
21 ms
464 ms
jquery.form.js
164 ms
scripts.js
164 ms
jquery.min.js
55 ms
easySlider1.7.js
164 ms
plugins.js
282 ms
script.js
282 ms
trackalyze.js
359 ms
re_.js
281 ms
modernizr-2.0.6.min.js
151 ms
style.css
166 ms
error.htm
205 ms
easySlider1.7.js
346 ms
script.js
269 ms
plugins.js
267 ms
1729
83 ms
body-bg.gif
345 ms
CapitalLogo.gif
386 ms
card-citi-airline.gif
710 ms
card-amex-gold.gif
709 ms
btnApply.gif
717 ms
footer-logo.gif
1597 ms
ca-pub-6864227551161423.js
212 ms
zrt_lookup.html
1522 ms
show_ads_impl.js
309 ms
menu-bg.png
640 ms
sidebar2-bg.gif
1250 ms
helveticaneue-condensed-webfont.woff
569 ms
InFeed
507 ms
566 ms
card-citi-mastercard.gif
1300 ms
card-discover.jpg
1250 ms
card-chase-freedom.gif
1244 ms
ads
1209 ms
osd.js
920 ms
card-citi-airline.gif
914 ms
btnApply.gif
908 ms
main-bg.gif
905 ms
whatshot-bg.gif
322 ms
rating-3point5stars.gif
323 ms
credit-indicator.gif
323 ms
ads
421 ms
footer-logo.gif
279 ms
footer-bg.gif
233 ms
footer-logo.gif
235 ms
ads
371 ms
m_js_controller.js
330 ms
abg.js
679 ms
main-bg.gif
557 ms
ga.js
527 ms
trackalyze.asp
517 ms
favicon
626 ms
favicon
812 ms
favicon
750 ms
googlelogo_color_112x36dp.png
625 ms
nessie_icon_tiamat_white.png
302 ms
x_button_blue2.png
286 ms
dot.gif
460 ms
main-bg.gif
204 ms
s
219 ms
ajax-loader.gif
550 ms
500 ms
ga.js
94 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
45 ms
__utm.gif
85 ms
main-bg.gif
23 ms
main-bg.gif
11 ms
capital.com accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
capital.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
capital.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 Capital.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 Capital.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.
capital.com
Open Graph description is not detected on the main page of Capital. 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: