3.9 sec in total
876 ms
2.7 sec
343 ms
Click here to check amazing Freakonomix content. Otherwise, check out these important facts you probably never knew about freakonomix.com
Free DJ Mix Podcasts brought to you by www.FREAKONOMIX.com!
Visit freakonomix.comWe analyzed Freakonomix.com page load time and found that the first response time was 876 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
freakonomix.com performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
876 ms
151 ms
169 ms
166 ms
37 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 34% of them (40 requests) were addressed to the original Freakonomix.com, 10% (12 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (876 ms) belongs to the original domain Freakonomix.com.
Page size can be reduced by 370.7 kB (43%)
864.0 kB
493.3 kB
In fact, the total size of Freakonomix.com main page is 864.0 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. 65% of websites need less resources to load. Images take 312.1 kB which makes up the majority of the site volume.
Potential reduce by 75.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 75.0 kB or 80% of the original size.
Potential reduce by 8.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. Freakonomix images are well optimized though.
Potential reduce by 68.0 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 68.0 kB or 44% of the original size.
Potential reduce by 219.6 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. Freakonomix.com needs all CSS files to be minified and compressed as it can save up to 219.6 kB or 72% of the original size.
Number of requests can be reduced by 61 (55%)
111
50
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freakonomix. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
freakonomix.com
876 ms
style.css
151 ms
reset.css
169 ms
screen.css
166 ms
google_service.js
37 ms
plusone.js
95 ms
style.css
181 ms
jquery.min.js
40 ms
swfobject.js
208 ms
audio-player-noswfobject.js
206 ms
stylesheet.css
237 ms
disqus.css
20 ms
tdomf-style-form.css
256 ms
wp-page-numbers.css
263 ms
show_ads.js
4 ms
Loader_308365.js
142 ms
v1.js
18 ms
google_ads.js
16 ms
cb=gapi.loaded_0
21 ms
all.js
164 ms
BluePAIDApp_125x125.jpg
501 ms
show
20 ms
header-bg.jpg
154 ms
FREAKONOMIX-WEB-LOGO-360x68.jpg
152 ms
social-bg.jpg
107 ms
social-edge.jpg
151 ms
social-connect-title.jpg
107 ms
social-icons.jpg
106 ms
nav-current.jpg
251 ms
search-input.jpg
202 ms
search-button.jpg
201 ms
1125.jpg
365 ms
708.jpg
385 ms
148.jpg
382 ms
djserafin160x98.jpg
299 ms
freakonomix-itunes-mix-show-120x98.jpg
308 ms
ie40.gif
337 ms
firefox40.gif
386 ms
safari40.gif
390 ms
chrome40.gif
420 ms
1655.jpg
546 ms
38.jpg
490 ms
20.jpg
489 ms
186.jpg
510 ms
V-MODAlogoBBG-125x125.jpg
490 ms
stanton-125x125.jpg
508 ms
official_bumsquad_dj.jpg
563 ms
showcase-bg.jpg
547 ms
showcase-effects.png
561 ms
mid-bg.jpg
575 ms
ca-pub-6741831200295902.js
202 ms
zrt_lookup.html
59 ms
show_ads_impl.js
65 ms
author-bg.jpg
531 ms
ads
268 ms
ads
298 ms
osd.js
28 ms
23 ms
xd_arbiter.php
134 ms
xd_arbiter.php
236 ms
footer-bg.jpg
242 ms
ga.js
29 ms
get_num_replies_from_wpid.js
209 ms
__utm.gif
11 ms
17017281189048022997
16 ms
abg.js
22 ms
m_js_controller.js
30 ms
googlelogo_color_112x36dp.png
65 ms
s
23 ms
x_button_blue2.png
23 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
4 ms
font-awesome.min.css
61 ms
widgets.js
37 ms
platform.js
107 ms
page.js
57 ms
1TF2XTZ
64 ms
cb=gapi.loaded_1
100 ms
fastbutton
156 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
83 ms
xd_arbiter.php
111 ms
1px.png
39 ms
fan.php
277 ms
sm13.html
46 ms
icons.15.svg.css
44 ms
like.php
138 ms
postmessageRelay
63 ms
ga.js
82 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
18 ms
cb=gapi.loaded_0
17 ms
cb=gapi.loaded_1
17 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
80 ms
3193398744-postmessagerelay.js
51 ms
rpc:shindig_random.js
33 ms
fy8tT2klpgR.js
288 ms
LVx-xkvaJ0b.png
212 ms
cb=gapi.loaded_0
12 ms
jot
90 ms
hDvwL1_H7g-.css
119 ms
udqjbTyb5Ue.css
114 ms
FAHeNGXgPup.js
150 ms
FJmpeSpHpjS.js
187 ms
0wM5s1Khldu.js
148 ms
1bNoFZUdlYZ.js
166 ms
540282_10150672774269403_124631244_n.jpg
181 ms
549087_10150672766544403_1877155848_n.jpg
187 ms
12801326_237895363210407_6548336196309917771_n.jpg
230 ms
941192_10151537920059463_263145015_n.jpg
256 ms
12316206_119505465087416_1885121648880756022_n.jpg
257 ms
1426396_1384659018448566_198489651_n.jpg
256 ms
1014117_1008729585835343_1941734233514384832_n.jpg
258 ms
74517_10200221259873506_181132956_n.jpg
265 ms
10734046_562304613913888_894779669353193675_n.jpg
270 ms
wL6VQj7Ab77.png
44 ms
s7jcwEQH7Sx.png
38 ms
I6-MnjEovm5.js
40 ms
pQrUxxo5oQp.js
74 ms
ui
35 ms
freakonomix.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
Document doesn't have a <title> element
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
freakonomix.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
freakonomix.com 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freakonomix.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Freakonomix.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.
freakonomix.com
Open Graph description is not detected on the main page of Freakonomix. 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: