3.1 sec in total
222 ms
2.7 sec
144 ms
Click here to check amazing Capital 100 content. Otherwise, check out these important facts you probably never knew about capital100.com
Visit capital100.comWe analyzed Capital100.com page load time and found that the first response time was 222 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
capital100.com performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value2.8 s
82/100
25%
Value4.7 s
69/100
10%
Value10 ms
100/100
30%
Value0.724
6/100
15%
Value2.6 s
98/100
10%
222 ms
45 ms
102 ms
64 ms
69 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Capital100.com, 62% (37 requests) were made to Static.parastorage.com and 15% (9 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (818 ms) relates to the external source Frog.wix.com.
Page size can be reduced by 2.4 MB (78%)
3.1 MB
678.2 kB
In fact, the total size of Capital100.com main page is 3.1 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 222.1 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 222.1 kB or 90% of the original size.
Potential reduce by 508 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. Obviously, Capital 100 needs image optimization as it can save up to 508 B or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.1 MB
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 2.1 MB or 77% of the original size.
Potential reduce by 51.7 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. Capital100.com needs all CSS files to be minified and compressed as it can save up to 51.7 kB or 84% of the original size.
Number of requests can be reduced by 40 (83%)
48
8
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capital 100. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
capital100.com
222 ms
capital100
45 ms
bt
102 ms
require.min.js
64 ms
main-r.min.js
69 ms
viewer.css
91 ms
dynamicmodel
47 ms
5d71bb_ca88505975f7a53ce71d5ef1a39a020c_176.json.z
525 ms
5d71bb_102ad15590647167ce3493479eb81277_97.json.z
531 ms
ugc-viewer
47 ms
bt
101 ms
skins.min.js
281 ms
components.min.js
172 ms
utils.min.js
85 ms
core.min.js
169 ms
react-with-addons.min.js
169 ms
lodash.min.js
67 ms
TweenMax.min.js
275 ms
layout.min.js
166 ms
tpa.min.js
280 ms
fonts.min.js
496 ms
animations.min.js
275 ms
swfobject.min.js
274 ms
mousetrap.min.js
276 ms
tweenEngine.min.js
275 ms
DrawSVGPlugin.min.js
276 ms
react-dom.min.js
278 ms
ScrollToPlugin.min.js
277 ms
widgets.min.js
275 ms
experiment.js
278 ms
render.min.js
278 ms
wixappsCore.min.js
281 ms
wixappsClassics.min.js
281 ms
wixappsBuilder.min.js
274 ms
zepto.min.js
271 ms
color.min.js
273 ms
react-dom-server.min.js
21 ms
bt
72 ms
latin.css
105 ms
dc.js
100 ms
bt
818 ms
cyrillic.css
804 ms
5d71bb_9f366875d5c2487ea12baf4c22b199d3.jpg
534 ms
css
297 ms
5d71bb_9f366875d5c2487ea12baf4c22b199d3.jpg
586 ms
bt
103 ms
bt
103 ms
bt
103 ms
wf_label_static.png
100 ms
BG91x1.jpg
99 ms
ironpatern.png
100 ms
__utm.gif
35 ms
ga-audiences
83 ms
opensans-bold-webfont.woff
27 ms
opensans-regular-webfont.woff
28 ms
AKI-lyzyNHXByGHeOcds_w.woff
27 ms
-KTKVm0Mx9ZCRXL9CXVIbT8E0i7KZn-EPnyo3HZu7kw.woff
28 ms
I27Pb-wEGH2ajLYP0QrtSHhCUOGz7vYGh680lGh-uXM.woff
28 ms
cc0b2292-9358-41ee-b3b9-429952586f69.woff
219 ms
ugc-viewer
183 ms
capital100.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
capital100.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
capital100.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
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 Capital100.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 Capital100.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.
capital100.com
Open Graph description is not detected on the main page of Capital 100. 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: