5.6 sec in total
714 ms
2.2 sec
2.7 sec
Click here to check amazing Traderspodcast content for United States. Otherwise, check out these important facts you probably never knew about traderspodcast.com
A podcast about living better and trading more profitably.
Visit traderspodcast.comWe analyzed Traderspodcast.com page load time and found that the first response time was 714 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
traderspodcast.com performance score
714 ms
108 ms
135 ms
131 ms
132 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 25% of them (26 requests) were addressed to the original Traderspodcast.com, 21% (21 requests) were made to Pixel.wp.com and 10% (10 requests) were made to Graph.facebook.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Content.screencast.com.
Page size can be reduced by 1.1 MB (44%)
2.4 MB
1.3 MB
In fact, the total size of Traderspodcast.com main page is 2.4 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 179.0 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 179.0 kB or 82% of the original size.
Potential reduce by 638.0 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. Obviously, Traderspodcast needs image optimization as it can save up to 638.0 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 141.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 141.7 kB or 63% of the original size.
Potential reduce by 95.1 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. Traderspodcast.com needs all CSS files to be minified and compressed as it can save up to 95.1 kB or 74% of the original size.
Number of requests can be reduced by 68 (69%)
99
31
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Traderspodcast. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
traderspodcast.com
714 ms
style.css
108 ms
layout.css
135 ms
custom.css
131 ms
wpp.css
132 ms
style.css
155 ms
genericons.css
159 ms
jetpack.css
170 ms
jquery.js
268 ms
jquery-migrate.min.js
200 ms
getsocial.css
199 ms
getsocial.js
227 ms
widgets.js
8 ms
pinit.js
49 ms
plusone.js
40 ms
devicepx-jetpack.js
12 ms
gprofiles.js
58 ms
wpgroho.js
183 ms
player.min.js
180 ms
sharing.js
385 ms
e-201611.js
5 ms
wp-emoji-release.min.js
288 ms
Screen%20Shot%202015-12-08%20at%208.37.30%20PM.png
1187 ms
PinExt.png
72 ms
downarrow2.png
603 ms
12.01.2014-08.19.png
606 ms
thetraderspodcast-header-blog1.gif
160 ms
dot-ddd.gif
86 ms
play_audio.png
87 ms
best-podcast.png
159 ms
itunes.png
88 ms
rss.png
84 ms
twitter.png
159 ms
facebook.png
159 ms
loading.gif
196 ms
all.js
79 ms
Genericons.svg
418 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
8 ms
cb=gapi.loaded_0
291 ms
pinit_main.js
289 ms
667 ms
xd_arbiter.php
369 ms
xd_arbiter.php
518 ms
hovercard.css
252 ms
services.css
303 ms
count.json
245 ms
g.gif
253 ms
graph.facebook.com
395 ms
count.json
243 ms
graph.facebook.com
520 ms
count.json
242 ms
graph.facebook.com
518 ms
count.json
239 ms
graph.facebook.com
515 ms
count.json
236 ms
graph.facebook.com
514 ms
count.json
236 ms
graph.facebook.com
514 ms
count.json
305 ms
graph.facebook.com
571 ms
count.json
305 ms
graph.facebook.com
633 ms
count.json
302 ms
graph.facebook.com
638 ms
count.json
389 ms
graph.facebook.com
672 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
366 ms
cb=gapi.loaded_1
147 ms
fastbutton
287 ms
g.gif
125 ms
g.gif
122 ms
g.gif
122 ms
g.gif
122 ms
g.gif
122 ms
g.gif
148 ms
g.gif
148 ms
g.gif
147 ms
g.gif
148 ms
g.gif
147 ms
g.gif
147 ms
g.gif
268 ms
g.gif
268 ms
g.gif
262 ms
g.gif
268 ms
g.gif
268 ms
g.gif
262 ms
g.gif
270 ms
g.gif
279 ms
g.gif
264 ms
count.json
287 ms
postmessageRelay
193 ms
cb=gapi.loaded_0
51 ms
cb=gapi.loaded_1
52 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
72 ms
like.php
249 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
27 ms
3193398744-postmessagerelay.js
30 ms
rpc:shindig_random.js
53 ms
cb=gapi.loaded_0
8 ms
jot
92 ms
qeKvIRsJabD.js
24 ms
LVx-xkvaJ0b.png
16 ms
traderspodcast.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Traderspodcast.com 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 Traderspodcast.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.
traderspodcast.com
Open Graph data is detected on the main page of Traderspodcast. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: