4.6 sec in total
1 sec
3.4 sec
175 ms
Visit thinksold.ca now to see the best up-to-date Thinksold content and also check out these interesting facts you probably never knew about thinksold.ca
Need assistance with your investment timing? Don’t we all! Tap into to the Market Metrics signal feed for when to buy, sell, short or sit it out.
Visit thinksold.caWe analyzed Thinksold.ca page load time and found that the first response time was 1 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
thinksold.ca performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.6 s
60/100
25%
Value3.2 s
92/100
10%
Value160 ms
93/100
30%
Value0.007
100/100
15%
Value3.8 s
89/100
10%
1012 ms
153 ms
229 ms
157 ms
171 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Thinksold.ca, 9% (4 requests) were made to Google-analytics.com and 4% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Marketmetrics.info.
Page size can be reduced by 444.6 kB (66%)
672.6 kB
228.0 kB
In fact, the total size of Thinksold.ca main page is 672.6 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. 35% of websites need less resources to load. Javascripts take 287.0 kB which makes up the majority of the site volume.
Potential reduce by 32.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 32.1 kB or 80% of the original size.
Potential reduce by 1.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. Thinksold images are well optimized though.
Potential reduce by 171.5 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 171.5 kB or 60% of the original size.
Potential reduce by 239.4 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. Thinksold.ca needs all CSS files to be minified and compressed as it can save up to 239.4 kB or 84% of the original size.
Number of requests can be reduced by 34 (79%)
43
9
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thinksold. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
marketmetrics.info
1012 ms
reset.css
153 ms
style.css
229 ms
54405a750206f.css
157 ms
structure.css
171 ms
bbpress.css
263 ms
structure.css
176 ms
prettyPhoto.css
230 ms
exchange.css
309 ms
membership-dashboard.css
262 ms
tablepress-combined.min.css
265 ms
mm-style.css
304 ms
jquery.js
454 ms
jquery-migrate.min.js
340 ms
jquery.prettyPhoto.js
424 ms
front.js
354 ms
font-awesome.css
6 ms
formreset.min.css
315 ms
formsmain.min.css
444 ms
readyclass.min.css
362 ms
browsers.min.css
378 ms
comment-reply.min.js
430 ms
jquery.fitvids-max-width-modification.js
453 ms
init-fitvids.js
453 ms
editor.js
468 ms
jquery.zoom.min.js
464 ms
membership-dashboard.js
469 ms
wp-embed.min.js
518 ms
conversion.js
16 ms
css
24 ms
wp-emoji-release.min.js
356 ms
script.js
139 ms
analytics.js
22 ms
content-bg.png
198 ms
Header-Images-2.jpg
263 ms
MM-Logo-new.jpg
198 ms
Market-Metrics-Performance.jpg
699 ms
fontawesome-webfont.woff
17 ms
collect
13 ms
87 ms
ga.js
66 ms
39 ms
__utm.gif
12 ms
style-responsive.css
82 ms
style-mobile.css
83 ms
print.css
83 ms
thinksold.ca 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
thinksold.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
thinksold.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thinksold.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Thinksold.ca 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.
thinksold.ca
Open Graph description is not detected on the main page of Thinksold. 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: