3.2 sec in total
68 ms
2.3 sec
789 ms
Welcome to wealthbar.com homepage info - get ready to check Wealth Bar best content for Canada right away, or after learning these important things about wealthbar.com
CI Direct Investing makes it easy to access financial advice. CI Direct Trading is the best online investment platform for self-directed trading.
Visit wealthbar.comWe analyzed Wealthbar.com page load time and found that the first response time was 68 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
wealthbar.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value7.7 s
3/100
25%
Value5.5 s
54/100
10%
Value640 ms
47/100
30%
Value0.004
100/100
15%
Value8.8 s
35/100
10%
68 ms
611 ms
41 ms
137 ms
300 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Wealthbar.com, 49% (23 requests) were made to D2lneha3bhxnj4.cloudfront.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source D2lneha3bhxnj4.cloudfront.net.
Page size can be reduced by 1.3 MB (63%)
2.1 MB
799.4 kB
In fact, the total size of Wealthbar.com main page is 2.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 853.6 kB which makes up the majority of the site volume.
Potential reduce by 157.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. This page needs HTML code to be minified as it can gain 36.3 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 157.6 kB or 82% of the original size.
Potential reduce by 25.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. Wealth Bar images are well optimized though.
Potential reduce by 523.1 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 523.1 kB or 61% of the original size.
Potential reduce by 641.2 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. Wealthbar.com needs all CSS files to be minified and compressed as it can save up to 641.2 kB or 89% of the original size.
Number of requests can be reduced by 14 (39%)
36
22
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wealth Bar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
www.wealthbar.com
68 ms
analytics.min.js
611 ms
honeybadger.min.js
41 ms
application-9abba65eaf92c98236c4161c1b30e58f92db00f5eed6ca21cd80682dfb2736d5.css
137 ms
vendor-6e9617dd58aec7c71eaa.js
300 ms
wealthbar-f4efb078648ee56d6dd8.js
606 ms
home-a808a8165d5aed549ee3.js
529 ms
app-store.svg
7 ms
google-play-badge.png
33 ms
wealthbar_logo-eea55bb69047ecab3d9e2412a30b962027f1c070627286a83e3f30c34455935e.svg
474 ms
homepage-graphic-01-8955e6f4ad9559ff25b52a08d2b0aca54700d044bec7374d7b5cc04cfd397d32.svg
554 ms
tea_illustration-c2ed21c43854b047a73a5fd9b87a38fc1501b7a469474c2ee19b438c2164bb20.png
475 ms
homepage-graphic-02-25bac57316c85f952a7f6175763e2ecdb5a7243a890925b89cff341197956ad3.svg
484 ms
nationalpost-grey-bfa3e6d1d6eff6e37664aa8d4ff7e452be47155b42e8ed4d361a4a4808d29224.png
534 ms
global-grey-ca0ca83ce258992c43c05b0c5e5ea55b9c830a6954670103e7da175326d7b485.png
535 ms
globeandmail-grey-6bf9ba913326a9fa9465bdf728d3810f06be116f7bf213fbd33b92b81c1f6ae7.png
523 ms
cbc-grey-b97d5579e43554ebaa747fabddcadce2d795c035a09c8ed29d1d19c5554e72cf.png
1078 ms
financialpostmag-grey-e051c4aeeb9cd1cc9d774b9d7c21726cb6c356b4b191946fdf42555a1898485c.png
524 ms
$500M-bkg-2x-69d4cb13e80b8e0885364cbad122bfd58fa35dea9471a6d4669042da634bcb1c.png
404 ms
DINWeb-Bold-0148403b9fffa430bce6b46fc385936fe9b6697b51618ee1066a325cf0d7ae49.woff
608 ms
DINWeb-d2fb59a64d9e550d348d6ca91a5344fac56f67fc6f165dda33df18ca5f61d74d.woff
544 ms
lato-v11-latin-regular-b82e3c01c34620fb5a610244cc773ad46b4b7197be81116ba22ee869a600f6d4.woff
606 ms
lato-v11-latin-700-be2d2f18ba47452f1f31d75dc3abaa2c1e57c366825bebfcac55a554424faa5b.woff
607 ms
lato-v11-latin-900-7e630d107bfe042bab96e91671aadbefc2e838943029f1de767c4f3df1982a44.woff
605 ms
WealthBar-d6703f7048eb07499b6d527df68d0c6464004b84ea56a7a89e8f5e62afea1201.woff
604 ms
lato-v11-latin-700italic-0d5b2e6a115679b3488b1b11193ce2e58b872dc5bb503d4a22db865725352737.woff
603 ms
lato-v11-latin-italic-6acd990ab8fc3f8b16c977a22e12a7c79bf8a3edd9f2164fe283ad5e880ecf88.woff
602 ms
settings.all.jsonp
341 ms
twofactor-02-2153894c4828b1d178108fa446f9e26d.png
66 ms
p
729 ms
adsct
163 ms
conversion_async.js
138 ms
amplitude-2.9.0-min.gz.js
343 ms
fbevents.js
377 ms
analytics.js
178 ms
bw0hbzif
142 ms
mixpanel-2-latest.min.js
300 ms
201 ms
intercom.bcfdf787.js
386 ms
collect
92 ms
languages.jsonp
106 ms
339 ms
330 ms
372 ms
ga-audiences
283 ms
echo.515e8809.js
81 ms
nr-885.min.js
128 ms
wealthbar.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
Links do not have a discernible name
wealthbar.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
Browser errors were logged to the console
wealthbar.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
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 Wealthbar.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 Wealthbar.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.
wealthbar.com
Open Graph data is detected on the main page of Wealth Bar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: