freakonomics.com

freakonomics.com is SSL secured

Free website and domain report on freakonomics.com

Last Updated: 8th February, 2021 Update Now
Overview

Snoop Summary for freakonomics.com

This is a free and comprehensive report about freakonomics.com. The domain freakonomics.com is currently hosted on a server located in United States with the IP address 52.116.199.28, where USD is the local currency and the local language is English. Freakonomics.com is expected to earn an estimated $18 USD per day from advertising revenue. The sale of freakonomics.com would possibly be worth $13,005 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Freakonomics.com receives an estimated 6,246 unique visitors every day - a huge amount of traffic! This report was last updated 8th February, 2021.

About freakonomics.com

Site Preview: freakonomics.com freakonomics.com
Title: Freakonomics - The hidden side of everything Freakonomics | The hidden side of everything
Description: The hidden side of everything
Keywords and Tags: education, news, reference
Related Terms: canal digital min side, creepy things hidden in pictures, digipost min side, everything about entrepreneurship, hidden risks, metoprolol side effects, phenocal side effects, side transfer, the side, tu lanh hitachi side by side
Fav Icon:
Age: Over 20 years old
Domain Created: 23rd October, 2003
Domain Updated: 12th December, 2018
Domain Expires: 23rd October, 2021
Review

Snoop Score

3/5 (Great!)

Valuation

$13,005 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 79,721
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 6,246
Monthly Visitors: 190,109
Yearly Visitors: 2,279,790
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $18 USD
Monthly Revenue: $542 USD
Yearly Revenue: $6,497 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: freakonomics.com 16
Domain Name: freakonomics 12
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.35 seconds
Load Time Comparison: Faster than 66% of sites

PageSpeed Insights

Avg. (All Categories) 70
Performance 94
Accessibility 61
Best Practices 64
SEO 92
Progressive Web App 37
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
94

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for freakonomics.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.2 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 0.7 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive freakonomics.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://freakonomics.com/
0
97.92899992317
11861
42422
200
text/html
Document
https://fonts.googleapis.com/css?family=Droid+Sans
114.24599960446
129.14100009948
1157
380
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Oswald:300
114.89100009203
126.72900035977
1614
1654
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Crete+Round:400,400italic
115.14300014824
132.334000431
1432
1440
200
text/css
Stylesheet
https://freakonomics.com/wp-content/themes/freako_2.0/css/normalize.css
115.38599990308
272.56599999964
990
1411
200
text/css
Stylesheet
https://freakonomics.com/wp-content/themes/freako_2.0/css/main.css?v=1.76
115.59300031513
286.62300016731
6648
37402
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js
115.98000023514
122.50200007111
30419
84320
200
text/javascript
Script
https://freakonomics.com/wp-content/themes/freako_2.0/lib/vendor/masonry.pkgd.min.js
116.12700019032
289.73499964923
8895
28953
200
application/javascript
Script
https://freakonomics.com/wp-content/themes/freako_2.0/lib/main.js?v=1.71
116.325000301
299.99999981374
6575
23057
200
application/javascript
Script
https://freakonomics.com/wp-includes/css/dist/block-library/style.min.css?ver=5.6.1
116.58400017768
267.15799979866
8212
51433
200
text/css
Stylesheet
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/css/frontend.min.css?ver=7.15.1
116.75699986517
295.80600000918
3271
36639
200
text/css
Stylesheet
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/js/frontend.min.js?ver=7.15.1
116.87699984759
280.58299981058
3137
9298
200
application/javascript
Script
https://freakonomics.com/wp-content/themes/freako_2.0/images/logo.png
313.34600038826
454.7709999606
12063
11756
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_itunes.png
319.39399987459
473.63600041717
4368
4063
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_twitter.png
387.60400004685
544.80499960482
2875
2570
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_fb.png
387.80899997801
437.77600023896
2251
1946
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_contact.png
388.12700007111
539.41900003701
991
687
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_close.png
388.39800003916
433.72299987823
1447
1142
200
image/png
Image
https://freakonomics.com/wp-content/uploads/2020/02/Sub-Leaderboard-01.png
388.58500029892
615.1520004496
52847
52540
200
image/png
Image
https://freakonomics.com/wp-content/uploads/2020/02/Freakonomics_WebButtons_SubscribeNow_300wd.png
388.80600035191
432.82900005579
9430
9124
200
image/png
Image
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
389.08500038087
533.94000045955
53558
53294
200
image/png
Image
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
389.27299994975
538.96600008011
53359
53094
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/button_surprise_me.png
389.50200006366
537.2639996931
3701
3396
200
image/png
Image
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
389.66500014067
540.76400026679
60185
59920
200
image/png
Image
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
389.85100015998
507.13500007987
46007
45742
200
image/jpeg
Image
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
390.03400038928
536.62499971688
55715
55450
200
image/jpeg
Image
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
390.18500037491
534.9080003798
43370
43105
200
image/jpeg
Image
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
390.31799975783
547.69099969417
48898
48633
200
image/jpeg
Image
http://freakonomics.disqus.com/count.js
390.45500010252
503.4929998219
449
0
301
text/html
https://freakonomics.com/wp-json/wp-statistics/v2/hit?_=1612692173&_wpnonce=275c3e4cc1&wp_statistics_hit_rest=yes&browser=Unknown&platform=Unknown&version=Unknown&referred=https://freakonomics.com&ip=127.0.0.1&exclusion_match=yes&exclusion_reason=CrawlerDetect&ua=BLP_bbot/0.1&track_all=1&timestamp=1612674173&current_page_type=home&current_page_id=0&search_query&page_uri=/&user_id=0
387.26800028235
459.45900026709
715
0
403
application/json
Other
https://snap.licdn.com/li.lms-analytics/insight.min.js
390.6020000577
473.17500039935
2169
4322
200
application/x-javascript
Script
http://www.google-analytics.com/analytics.js
390.77000040561
397.00900018215
19274
47051
200
text/javascript
Script
https://freakonomics.com/wp-includes/js/wp-emoji-release.min.js?ver=5.6.1
391.80599991232
546.48400004953
5033
14229
200
application/javascript
Script
https://freakonomics.com/wp-json/wp-statistics/v2/hit?_=1612692173&_wpnonce=275c3e4cc1&wp_statistics_hit_rest=yes&browser=Unknown&platform=Unknown&version=Unknown&referred=https://freakonomics.com&ip=127.0.0.1&exclusion_match=yes&exclusion_reason=CrawlerDetect&ua=BLP_bbot/0.1&track_all=1&timestamp=1612674173&current_page_type=home&current_page_id=0&search_query&page_uri=/&user_id=0
385.46600006521
518.31500045955
0
0
-1
XHR
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_search.png
394.00499965996
541.32699966431
1698
1392
200
image/png
Image
https://fonts.gstatic.com/s/oswald/v36/TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYySUhiCXAA.woff
394.81199998409
399.26700014621
13404
12836
200
font/woff
Font
https://freakonomics.com/wp-content/themes/freako_2.0/images/newsletter_icon.png
464.40500020981
501.81599985808
2359
2054
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/button_slot_arm.png
469.53400038183
623.3769999817
5291
4985
200
image/png
Image
https://fonts.gstatic.com/s/creteround/v9/55xoey1sJNPjPiv1ZZZrxK170b3iKWxM.woff2
472.35400043428
475.53899977356
12081
11512
200
font/woff2
Font
https://freakonomics.disqus.com/count.js
503.72599996626
619.71999984235
1570
1517
200
application/javascript
Script
https://freakonomics.com/wp-content/themes/freako_2.0/images/footer_subscribe.png
525.90799983591
565.96199981868
14145
13838
200
image/png
Image
http://tracking.aegpresents.com/universalpixel/universalpixel.js?t=1612828800000
549.80699997395
633.45499988645
880
353
200
application/javascript
Script
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_play.png?v=1.1
607.71999973804
646.92199975252
1332
1027
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_volume.png?v=1.4
608.21999981999
647.35700003803
1436
1131
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_download.png?v=1.1
608.87499991804
647.85899966955
1555
1250
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j87&a=1947925707&t=pageview&_s=1&dl=http%3A%2F%2Ffreakonomics.com%2F&ul=en-us&de=UTF-8&dt=Freakonomics%20-%20The%20hidden%20side%20of%20everything%20Freakonomics%20%7C%20The%20hidden%20side%20of%20everything&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=290349724&gjid=1541963645&cid=979196540.1612745796&tid=UA-21781166-1&_gid=732953421.1612745796&_r=1&_slc=1&did=dZGIzZG&z=1148995841
654.5099997893
658.03200006485
624
2
200
text/plain
XHR
https://px.ads.linkedin.com/collect?v=2&fmt=js&pid=192945&time=1612745796239&url=http%3A%2F%2Ffreakonomics.com%2F
688.22799995542
717.48599968851
876
0
302
http://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
714.38200026751
761.76500041038
544
0
301
text/html
http://freakonomics.disqus.com/count-data.js?1=125851
715.18300008029
758.62199999392
463
0
301
text/html
https://www.googletagmanager.com/gtm.js?id=GTM-M9NK8HW
715.41300043464
756.5559996292
92406
443823
200
application/javascript
Script
https://px.ads.linkedin.com/collect?v=2&fmt=js&pid=192945&time=1612745796239&url=http%3A%2F%2Ffreakonomics.com%2F&cookiesTest=true
717.81999990344
751.30099989474
778
0
302
https://www.linkedin.com/px/li_sync?redirect=https%3A%2F%2Fpx.ads.linkedin.com%2Fcollect%3Fv%3D2%26fmt%3Djs%26pid%3D192945%26time%3D1612745796239%26url%3Dhttp%253A%252F%252Ffreakonomics.com%252F%26cookiesTest%3Dtrue%26liSync%3Dtrue
751.65699981153
802.9829999432
2404
0
302
https://freakonomics.disqus.com/count-data.js?1=125851
761.13099977374
819.18799970299
779
239
200
application/javascript
Script
https://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
762.0609998703
818.33900045604
1041
501
200
application/javascript
Script
https://px.ads.linkedin.com/collect?v=2&fmt=js&pid=192945&time=1612745796239&url=http%3A%2F%2Ffreakonomics.com%2F&cookiesTest=true&liSync=true
803.21899987757
846.26999963075
545
0
302
https://connect.facebook.net/en_US/fbevents.js
815.30600041151
831.5110001713
25311
93376
200
application/x-javascript
Script
http://tracking.aegpresents.com/sp_2_16_3.js
844.05300021172
998.80599975586
79449
78920
200
application/javascript
Script
https://p.adsymptotic.com/d/px/?_pid=16218&_psign=0aa5badf92527f7732e22463d6fa4dbc&coopa=0&gdpr=0&gdpr_consent=&_puuid=212f7fc3-a2e2-429f-91fd-7d6db9eaf5b3
849.35600031167
937.34499998391
834
0
302
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
870.56499999017
892.5839997828
72402
247023
200
application/x-javascript
Script
https://www.facebook.com/tr/?id=217011611820041&ev=PageView&dl=http%3A%2F%2Ffreakonomics.com%2F&rl=&if=false&ts=1612745796487&sw=800&sh=600&v=2.9.33&r=stable&a=tmgoogletagmanager&ec=0&o=30&fbp=fb.1.1612745796484.674221216&it=1612745796420&coo=false&rqm=GET
937.52199970186
951.56299974769
507
44
200
image/gif
Image
https://p.adsymptotic.com/d/px/?_pid=16218&_psign=0aa5badf92527f7732e22463d6fa4dbc&coopa=0&gdpr=0&gdpr_consent=&_puuid=212f7fc3-a2e2-429f-91fd-7d6db9eaf5b3&_expected_cookie=f17fa833eadd5982ec4c92247a009b39
937.7469997853
998.49299993366
737
43
200
image/gif
Image
http://b.aegpresents.com/com.snowplowanalytics.snowplow/tp2
1033.637999557
1245.5820003524
305
0
200
Other
http://b.aegpresents.com/com.snowplowanalytics.snowplow/tp2
1246.0789997131
1412.9579998553
473
2
200
text/plain
XHR
https://www.facebook.com/tr/
1440.318999812
1441.6460003704
0
0
-1
Other
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
132.781
8.536
144.989
5.686
321.715
21.367
345.166
5.787
351.307
70.45
421.77
22.458
444.999
40.869
489.564
43.579
537.341
11.648
555.636
22.42
580.407
76.176
656.655
30.189
686.876
6.366
699.953
7.102
720.162
10.178
731.247
6.835
807.517
27.472
835.494
13.198
851.113
25.216
882.27
5.128
887.61
13.354
939.796
29.655
1037.18
28.443
1067.671
8.647
1468.183
5.045
1480.626
8.117
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Freakonomics.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Freakonomics.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Freakonomics.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Freakonomics.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 89 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
72402
53647
http://tracking.aegpresents.com/sp_2_16_3.js
79449
37998
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression — Potential savings of 51 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://tracking.aegpresents.com/sp_2_16_3.js
78920
52127
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 100 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://freakonomics.com/
98.927
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Freakonomics.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Freakonomics.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
11994
https://connect.facebook.net/en_US/fbevents.js
45

Diagnostics

Avoids enormous network payloads — Total size was 878 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtm.js?id=GTM-M9NK8HW
92406
http://tracking.aegpresents.com/sp_2_16_3.js
79449
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
72402
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
60185
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
55715
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
53558
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
53359
https://freakonomics.com/wp-content/uploads/2020/02/Sub-Leaderboard-01.png
52847
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
48898
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
46007
Avoids an excessive DOM size — 502 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
502
Maximum DOM Depth
11
Maximum Child Elements
13
Avoid chaining critical requests — 11 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Freakonomics.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://freakonomics.com/
270.177
68.021
3.471
https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js
99.67
83.349
1.519
https://www.googletagmanager.com/gtm.js?id=GTM-M9NK8HW
68.174
51.006
10.848
Unattributable
55.987
1.009
0.129
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
322.544
Style & Layout
103.594
Other
95.73
Parse HTML & CSS
61.179
Rendering
39.094
Script Parsing & Compilation
37.864
Keep request counts low and transfer sizes small — 64 requests • 878 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
64
899145
Image
25
480125
Script
15
349340
Font
2
25485
Stylesheet
7
23324
Document
1
11861
Other
14
9010
Media
0
0
Third-party
30
364927
Minimize third-party usage — Third-party code blocked the main thread for 10 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
30419
9.898
98220
0
92406
0
29688
0
19898
0
4846
0
4573
0
1571
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://freakonomics.com/wp-content/themes/freako_2.0/lib/main.js?v=1.71
490
70
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Opportunities

Eliminate render-blocking resources — Potential savings of 440 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Freakonomics.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Droid+Sans
1157
230
https://fonts.googleapis.com/css?family=Oswald:300
1614
230
https://fonts.googleapis.com/css?family=Crete+Round:400,400italic
1432
230
https://freakonomics.com/wp-content/themes/freako_2.0/css/normalize.css
990
150
https://freakonomics.com/wp-content/themes/freako_2.0/css/main.css?v=1.76
6648
190
https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js
30419
350
https://freakonomics.com/wp-content/themes/freako_2.0/lib/vendor/masonry.pkgd.min.js
8895
230
https://freakonomics.com/wp-content/themes/freako_2.0/lib/main.js?v=1.71
6575
190
https://freakonomics.com/wp-includes/css/dist/block-library/style.min.css?ver=5.6.1
8212
190
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/css/frontend.min.css?ver=7.15.1
3271
150
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/js/frontend.min.js?ver=7.15.1
3137
150
Properly size images — Potential savings of 110 KiB
Images can slow down the page's load time. Freakonomics.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
55450
24306
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
48633
20538
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
45742
19724
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
43105
18741
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
59920
10635
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
53294
9475
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
53094
9424
Serve images in next-gen formats — Potential savings of 278 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
59920
50426
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
53094
45918
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
53294
45798
https://freakonomics.com/wp-content/uploads/2020/02/Sub-Leaderboard-01.png
52540
41950
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
55450
25804
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
48633
23827
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
43105
21017
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
45742
21006
https://freakonomics.com/wp-content/themes/freako_2.0/images/footer_subscribe.png
13838
9278

Metrics

Cumulative Layout Shift — 0.317
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Diagnostics

Serve static assets with an efficient cache policy — 41 resources found
Freakonomics.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://tracking.aegpresents.com/sp_2_16_3.js
0
79449
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
0
60185
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
0
55715
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
0
53558
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
0
53359
https://freakonomics.com/wp-content/uploads/2020/02/Sub-Leaderboard-01.png
0
52847
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
0
48898
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
0
46007
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
0
43370
https://freakonomics.com/wp-content/themes/freako_2.0/images/footer_subscribe.png
0
14145
https://freakonomics.com/wp-content/themes/freako_2.0/images/logo.png
0
12063
https://freakonomics.com/wp-content/uploads/2020/02/Freakonomics_WebButtons_SubscribeNow_300wd.png
0
9430
https://freakonomics.com/wp-content/themes/freako_2.0/lib/vendor/masonry.pkgd.min.js
0
8895
https://freakonomics.com/wp-includes/css/dist/block-library/style.min.css?ver=5.6.1
0
8212
https://freakonomics.com/wp-content/themes/freako_2.0/css/main.css?v=1.76
0
6648
https://freakonomics.com/wp-content/themes/freako_2.0/lib/main.js?v=1.71
0
6575
https://freakonomics.com/wp-content/themes/freako_2.0/images/button_slot_arm.png
0
5291
https://freakonomics.com/wp-includes/js/wp-emoji-release.min.js?ver=5.6.1
0
5033
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_itunes.png
0
4368
https://freakonomics.com/wp-content/themes/freako_2.0/images/button_surprise_me.png
0
3701
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/css/frontend.min.css?ver=7.15.1
0
3271
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/js/frontend.min.js?ver=7.15.1
0
3137
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_twitter.png
0
2875
https://freakonomics.com/wp-content/themes/freako_2.0/images/newsletter_icon.png
0
2359
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_fb.png
0
2251
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_search.png
0
1698
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_download.png?v=1.1
0
1555
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_close.png
0
1447
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_volume.png?v=1.4
0
1436
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_play.png?v=1.1
0
1332
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_contact.png
0
991
https://freakonomics.com/wp-content/themes/freako_2.0/css/normalize.css
0
990
http://tracking.aegpresents.com/universalpixel/universalpixel.js?t=1612828800000
0
880
https://p.adsymptotic.com/d/px/?_pid=16218&_psign=0aa5badf92527f7732e22463d6fa4dbc&coopa=0&gdpr=0&gdpr_consent=&_puuid=212f7fc3-a2e2-429f-91fd-7d6db9eaf5b3&_expected_cookie=f17fa833eadd5982ec4c92247a009b39
0
737
https://freakonomics.disqus.com/count.js
300000
1570
https://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
600000
1041
https://freakonomics.disqus.com/count-data.js?1=125851
600000
779
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
1200000
72402
https://connect.facebook.net/en_US/fbevents.js
1200000
25311
http://www.google-analytics.com/analytics.js
7200000
19274
https://snap.licdn.com/li.lms-analytics/insight.min.js
25915000
2169
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/oswald/v36/TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYySUhiCXAA.woff
4.4550001621246
https://fonts.gstatic.com/s/creteround/v9/55xoey1sJNPjPiv1ZZZrxK170b3iKWxM.woff2
3.1849993392825
61

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of freakonomics.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Freakonomics.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Freakonomics.com may provide relevant information that dialogue cannot, by using audio descriptions.

Contrast

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
64

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that freakonomics.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
2.1.3
WordPress
5.6.1
core-js
3.0.0: pure
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 15 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://freakonomics.com/
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
http://freakonomics.disqus.com/count.js
http://www.google-analytics.com/analytics.js
http://tracking.aegpresents.com/universalpixel/universalpixel.js?t=1612828800000
http://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
http://freakonomics.disqus.com/count-data.js?1=125851
http://tracking.aegpresents.com/sp_2_16_3.js
http://b.aegpresents.com/com.snowplowanalytics.snowplow/tp2
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
URL
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
http://freakonomics.com/
Access to XMLHttpRequest at 'https://freakonomics.com/wp-json/wp-statistics/v2/hit?_=1612692173&_wpnonce=275c3e4cc1&wp_statistics_hit_rest=yes&browser=Unknown&platform=Unknown&version=Unknown&referred=https://freakonomics.com&ip=127.0.0.1&exclusion_match=yes&exclusion_reason=CrawlerDetect&ua=BLP_bbot/0.1&track_all=1&timestamp=1612674173&current_page_type=home&current_page_id=0&search_query&page_uri=/&user_id=0' from origin 'http://freakonomics.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.
https://www.facebook.com/tr/
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector
https://freakonomics.com/wp-json/wp-statistics/v2/hit?_=1612692173&_wpnonce=275c3e4cc1&wp_statistics_hit_rest=yes&browser=Unknown&platform=Unknown&version=Unknown&referred=https://freakonomics.com&ip=127.0.0.1&exclusion_match=yes&exclusion_reason=CrawlerDetect&ua=BLP_bbot/0.1&track_all=1&timestamp=1612674173&current_page_type=home&current_page_id=0&search_query&page_uri=/&user_id=0
Failed to load resource: net::ERR_FAILED
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for freakonomics.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freakonomics.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
37

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of freakonomics.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freakonomics.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 15 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://freakonomics.com/
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
http://freakonomics.disqus.com/count.js
http://www.google-analytics.com/analytics.js
http://tracking.aegpresents.com/universalpixel/universalpixel.js?t=1612828800000
http://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
http://freakonomics.disqus.com/count-data.js?1=125851
http://tracking.aegpresents.com/sp_2_16_3.js
http://b.aegpresents.com/com.snowplowanalytics.snowplow/tp2
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 66
Performance 85
Accessibility 58
Best Practices 57
SEO 93
Progressive Web App 39
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
85

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for freakonomics.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 2.1 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 2.1 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.1 s
The timing of the largest text or image that is painted.

Other

Estimated Input Latency — 50 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive freakonomics.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://freakonomics.com/
0
78.800000017509
11861
42422
200
text/html
Document
https://fonts.googleapis.com/css?family=Droid+Sans
98.023000173271
113.3690001443
1201
380
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Oswald:300
98.176000174135
114.35800022446
1569
1653
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Crete+Round:400,400italic
98.713000072166
113.90900006518
1446
1440
200
text/css
Stylesheet
https://freakonomics.com/wp-content/themes/freako_2.0/css/normalize.css
99.087000126019
137.57200003602
991
1411
200
text/css
Stylesheet
https://freakonomics.com/wp-content/themes/freako_2.0/css/main.css?v=1.76
99.867000011727
140.68900002167
6649
37402
200
text/css
Stylesheet
https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js
100.07200017571
106.49900021963
30419
84320
200
text/javascript
Script
https://freakonomics.com/wp-content/themes/freako_2.0/lib/vendor/masonry.pkgd.min.js
100.33700009808
140.05700009875
8895
28953
200
application/javascript
Script
https://freakonomics.com/wp-content/themes/freako_2.0/lib/main.js?v=1.71
100.65400018357
141.86300011352
6575
23057
200
application/javascript
Script
https://freakonomics.com/wp-includes/css/dist/block-library/style.min.css?ver=5.6.1
100.80300015397
143.43799999915
8212
51433
200
text/css
Stylesheet
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/css/frontend.min.css?ver=7.15.1
100.96800001338
141.37000008486
3272
36639
200
text/css
Stylesheet
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/js/frontend.min.js?ver=7.15.1
101.09300003387
142.85699999891
3137
9298
200
application/javascript
Script
https://freakonomics.com/wp-content/themes/freako_2.0/images/logo.png
172.66500019468
211.59600000829
12063
11756
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_itunes.png
225.52200010978
269.94800008833
4369
4063
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_twitter.png
228.21100009605
267.88300019689
2876
2570
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_fb.png
228.36000006646
266.53900020756
2252
1946
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_contact.png
228.63500006497
268.29500007443
992
687
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_close.png
228.89800020494
267.21600000747
1448
1142
200
image/png
Image
https://freakonomics.com/wp-content/uploads/2020/02/Sub-Leaderboard-01.png
229.16200011969
304.39100018702
52847
52540
200
image/png
Image
https://freakonomics.com/wp-content/uploads/2020/02/Freakonomics_WebButtons_SubscribeNow_300wd.png
229.37600011937
271.04000002146
9432
9124
200
image/png
Image
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
229.76100002415
305.39100011811
53558
53294
200
image/png
Image
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
230.2080001682
385.31600008719
53358
53094
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/button_surprise_me.png
230.37300002761
379.76000015624
3701
3396
200
image/png
Image
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
230.53000005893
379.17300011031
60184
59920
200
image/png
Image
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
230.76599999331
372.89500003681
46007
45742
200
image/jpeg
Image
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
231.03700019419
381.16200012155
55715
55450
200
image/jpeg
Image
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
231.21100012213
371.75000016578
43370
43105
200
image/jpeg
Image
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
231.36900016107
373.51100007072
48898
48633
200
image/jpeg
Image
http://freakonomics.disqus.com/count.js
231.51800013147
393.16199999303
449
0
301
text/html
https://snap.licdn.com/li.lms-analytics/insight.min.js
231.74700001255
313.53300018236
2169
4322
200
application/x-javascript
Script
http://www.google-analytics.com/analytics.js
232.10000013933
240.32700015232
19274
47051
200
text/javascript
Script
https://freakonomics.com/wp-includes/js/wp-emoji-release.min.js?ver=5.6.1
232.45900007896
270.61100001447
5034
14229
200
application/javascript
Script
https://freakonomics.com/wp-json/wp-statistics/v2/hit?_=1612692173&_wpnonce=275c3e4cc1&wp_statistics_hit_rest=yes&browser=Unknown&platform=Unknown&version=Unknown&referred=https://freakonomics.com&ip=127.0.0.1&exclusion_match=yes&exclusion_reason=CrawlerDetect&ua=BLP_bbot/0.1&track_all=1&timestamp=1612674173&current_page_type=home&current_page_id=0&search_query&page_uri=/&user_id=0
228.01600000821
300.68900017068
715
0
403
application/json
Other
https://freakonomics.com/wp-json/wp-statistics/v2/hit?_=1612692173&_wpnonce=275c3e4cc1&wp_statistics_hit_rest=yes&browser=Unknown&platform=Unknown&version=Unknown&referred=https://freakonomics.com&ip=127.0.0.1&exclusion_match=yes&exclusion_reason=CrawlerDetect&ua=BLP_bbot/0.1&track_all=1&timestamp=1612674173&current_page_type=home&current_page_id=0&search_query&page_uri=/&user_id=0
227.07100003026
394.0930000972
0
0
-1
XHR
https://freakonomics.com/wp-content/themes/freako_2.0/images/sprite_burger.png
235.36900011823
383.83400021121
1325
1020
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/newsletter_icon.png
343.21400010958
382.19800009392
2359
2054
200
image/png
Image
https://fonts.gstatic.com/s/oswald/v36/TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiZSSShiA.woff2
345.71100003086
349.68400001526
10613
10044
200
font/woff2
Font
https://fonts.gstatic.com/s/creteround/v9/55xoey1sJNPjPiv1ZZZrxK170b3iKWxM.woff2
348.58200000599
354.03900011443
12081
11512
200
font/woff2
Font
https://freakonomics.disqus.com/count.js
393.60500010662
459.73300002515
1572
1517
200
application/javascript
Script
http://tracking.aegpresents.com/universalpixel/universalpixel.js?t=1612828800000
444.71599999815
472.61000005528
880
353
200
application/javascript
Script
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_play.png?v=1.1
502.59600020945
540.91800004244
1333
1027
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_volume.png?v=1.4
503.39800002985
554.78600016795
1436
1131
200
image/png
Image
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_download.png?v=1.1
504.13200003095
541.52200021781
1555
1250
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j87&a=990672120&t=pageview&_s=1&dl=http%3A%2F%2Ffreakonomics.com%2F&ul=en-us&de=UTF-8&dt=Freakonomics%20-%20The%20hidden%20side%20of%20everything%20Freakonomics%20%7C%20The%20hidden%20side%20of%20everything&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAAC~&jid=173464620&gjid=1719560365&cid=1838117272.1612745809&tid=UA-21781166-1&_gid=716303853.1612745809&_r=1&_slc=1&did=dZGIzZG&z=212006604
551.60600016825
555.32800010405
624
2
200
text/plain
XHR
https://px.ads.linkedin.com/collect?v=2&fmt=js&pid=192945&time=1612745809317&url=http%3A%2F%2Ffreakonomics.com%2F
570.19000011496
599.82700017281
861
0
302
http://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
598.02200016566
628.12200002372
544
0
301
text/html
http://freakonomics.disqus.com/count-data.js?1=125851
598.94600021653
626.50700006634
448
0
301
text/html
https://www.googletagmanager.com/gtm.js?id=GTM-M9NK8HW
599.18900020421
675.45199999586
92406
443823
200
application/javascript
Script
https://px.ads.linkedin.com/collect?v=2&fmt=js&pid=192945&time=1612745809317&url=http%3A%2F%2Ffreakonomics.com%2F&cookiesTest=true
600.10200017132
635.67600003444
793
0
302
https://freakonomics.disqus.com/count-data.js?1=125851
626.79200014099
686.41800014302
778
239
200
application/javascript
Script
https://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
628.60500020906
686.97300017811
1040
501
200
application/javascript
Script
https://www.linkedin.com/px/li_sync?redirect=https%3A%2F%2Fpx.ads.linkedin.com%2Fcollect%3Fv%3D2%26fmt%3Djs%26pid%3D192945%26time%3D1612745809317%26url%3Dhttp%253A%252F%252Ffreakonomics.com%252F%26cookiesTest%3Dtrue%26liSync%3Dtrue
636.10100001097
668.70600008406
2389
0
302
https://px.ads.linkedin.com/collect?v=2&fmt=js&pid=192945&time=1612745809317&url=http%3A%2F%2Ffreakonomics.com%2F&cookiesTest=true&liSync=true
669.14200014435
740.96200009808
560
0
302
https://p.adsymptotic.com/d/px/?_pid=16218&_psign=0aa5badf92527f7732e22463d6fa4dbc&coopa=0&gdpr=0&gdpr_consent=&_puuid=bb1a40e0-e8b2-4ad1-8b52-52120875e7ea
741.48000008427
814.31400007568
834
0
302
https://connect.facebook.net/en_US/fbevents.js
759.26700001583
775.54400009103
25003
93376
200
application/x-javascript
Script
http://tracking.aegpresents.com/sp_2_16_3.js
785.77600000426
832.33300014399
79449
78920
200
application/javascript
Script
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
814.3680000212
835.46500001103
72402
247023
200
application/x-javascript
Script
https://p.adsymptotic.com/d/px/?_pid=16218&_psign=0aa5badf92527f7732e22463d6fa4dbc&coopa=0&gdpr=0&gdpr_consent=&_puuid=bb1a40e0-e8b2-4ad1-8b52-52120875e7ea&_expected_cookie=9db7226bf171532e714b9184e7e401f9
814.89700009115
880.6240002159
737
43
200
image/gif
Image
http://b.aegpresents.com/com.snowplowanalytics.snowplow/tp2
873.59700002708
994.93500008248
305
0
200
Other
http://b.aegpresents.com/com.snowplowanalytics.snowplow/tp2
995.58300012723
1092.1660000458
473
2
200
text/plain
XHR
https://www.facebook.com/tr/?id=217011611820041&ev=PageView&dl=http%3A%2F%2Ffreakonomics.com%2F&rl=&if=false&ts=1612745809659&sw=360&sh=640&v=2.9.33&r=stable&a=tmgoogletagmanager&ec=0&o=30&fbp=fb.1.1612745809655.1825631351&it=1612745809561&coo=false&rqm=GET
913.59600005671
927.83100018278
507
44
200
image/gif
Image
https://www.facebook.com/tr/
1417.4880001228
1419.1070001107
0
0
-1
Other
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
119.952
10.583
134.487
6.638
183.31
24.79
210.001
52.161
262.561
7.127
269.704
9.324
281.798
86.142
368.995
54.085
434.559
14.104
460.921
19.749
480.708
78.779
559.539
29.742
589.295
5.715
595.566
7.943
607.907
8.339
739.108
34.85
778.941
19.289
798.253
25.174
833.628
18.063
876.756
34.05
914.1
36.712
1009.476
9.325
1449.479
6.447
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Freakonomics.com should consider serving more appropriate-sized images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Freakonomics.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Freakonomics.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Freakonomics.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 80 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://freakonomics.com/
79.798
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Freakonomics.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Freakonomics.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
11994
https://connect.facebook.net/en_US/fbevents.js
45

Diagnostics

Avoids enormous network payloads — Total size was 856 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtm.js?id=GTM-M9NK8HW
92406
http://tracking.aegpresents.com/sp_2_16_3.js
79449
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
72402
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
60184
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
55715
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
53558
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
53358
https://freakonomics.com/wp-content/uploads/2020/02/Sub-Leaderboard-01.png
52847
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
48898
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
46007
Avoids an excessive DOM size — 502 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
502
Maximum DOM Depth
11
Maximum Child Elements
13
Avoid chaining critical requests — 11 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Freakonomics.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 62 requests • 856 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
62
876245
Image
23
460322
Script
15
349033
Stylesheet
7
23340
Font
2
22694
Document
1
11861
Other
14
8995
Media
0
0
Third-party
30
361826
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
img
0.068580361024879
0.046436440332934
0.036204682293474
0.028664971464869
a
0.0066152470865353
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 12 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
http://freakonomics.com/
718
345
https://freakonomics.com/wp-content/themes/freako_2.0/lib/main.js?v=1.71
1560
209
https://freakonomics.com/wp-content/themes/freako_2.0/lib/vendor/masonry.pkgd.min.js
3159
158
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
7980
147
https://www.googletagmanager.com/gtm.js?id=GTM-M9NK8HW
5670
139
http://tracking.aegpresents.com/sp_2_16_3.js
7200
136
http://freakonomics.com/
1063
108
https://www.googletagmanager.com/gtm.js?id=GTM-M9NK8HW
5886
101
https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js
3060
99
https://www.googletagmanager.com/gtm.js?id=GTM-M9NK8HW
5809
77
https://connect.facebook.net/en_US/fbevents.js
6750
72
http://www.google-analytics.com/analytics.js
3780
59
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Time to Interactive — 6.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 360 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.192
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 5.7 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 160 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.4 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 4359 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Defer offscreen images — Potential savings of 215 KiB
Time to Interactive can be slowed down by resources on the page. Freakonomics.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
59920
59920
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
55450
55450
https://freakonomics.com/wp-content/uploads/2020/02/Sub-Leaderboard-01.png
52540
52540
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
45742
45742
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_itunes.png
4063
4063
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_twitter.png
2570
2570
Remove unused JavaScript — Potential savings of 89 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
72402
53647
http://tracking.aegpresents.com/sp_2_16_3.js
79449
37998
Enable text compression — Potential savings of 51 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://tracking.aegpresents.com/sp_2_16_3.js
78920
52127

Diagnostics

Reduce JavaScript execution time — 1.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://freakonomics.com/
1155.82
228.736
15.336
https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js
381.416
319.084
6.768
https://www.googletagmanager.com/gtm.js?id=GTM-M9NK8HW
327.32
240.852
51.624
Unattributable
243.832
5.34
0.768
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
172.636
142.66
20.744
http://www.google-analytics.com/analytics.js
157.824
120.12
28.744
http://tracking.aegpresents.com/sp_2_16_3.js
144.276
124.064
6.908
https://connect.facebook.net/en_US/fbevents.js
72.252
60.24
8.68
https://freakonomics.com/wp-content/themes/freako_2.0/lib/vendor/masonry.pkgd.min.js
64.284
24.516
10.592
Minimize main-thread work — 2.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1349.976
Parse HTML & CSS
436.272
Other
402.068
Style & Layout
392.628
Script Parsing & Compilation
177.164
Rendering
109.728

Opportunities

Eliminate render-blocking resources — Potential savings of 1,430 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Freakonomics.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Droid+Sans
1201
780
https://fonts.googleapis.com/css?family=Oswald:300
1569
930
https://fonts.googleapis.com/css?family=Crete+Round:400,400italic
1446
780
https://freakonomics.com/wp-content/themes/freako_2.0/css/normalize.css
991
480
https://freakonomics.com/wp-content/themes/freako_2.0/css/main.css?v=1.76
6649
780
https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js
30419
1380
https://freakonomics.com/wp-content/themes/freako_2.0/lib/vendor/masonry.pkgd.min.js
8895
930
https://freakonomics.com/wp-content/themes/freako_2.0/lib/main.js?v=1.71
6575
780
https://freakonomics.com/wp-includes/css/dist/block-library/style.min.css?ver=5.6.1
8212
930
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/css/frontend.min.css?ver=7.15.1
3272
630
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/js/frontend.min.js?ver=7.15.1
3137
630
Serve images in next-gen formats — Potential savings of 269 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
59920
50426
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
53094
45918
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
53294
45798
https://freakonomics.com/wp-content/uploads/2020/02/Sub-Leaderboard-01.png
52540
41950
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
55450
25804
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
48633
23827
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
43105
21017
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
45742
21006

Diagnostics

Serve static assets with an efficient cache policy — 39 resources found
Freakonomics.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://tracking.aegpresents.com/sp_2_16_3.js
0
79449
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
0
60184
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
0
55715
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
0
53558
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
0
53358
https://freakonomics.com/wp-content/uploads/2020/02/Sub-Leaderboard-01.png
0
52847
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
0
48898
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
0
46007
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
0
43370
https://freakonomics.com/wp-content/themes/freako_2.0/images/logo.png
0
12063
https://freakonomics.com/wp-content/uploads/2020/02/Freakonomics_WebButtons_SubscribeNow_300wd.png
0
9432
https://freakonomics.com/wp-content/themes/freako_2.0/lib/vendor/masonry.pkgd.min.js
0
8895
https://freakonomics.com/wp-includes/css/dist/block-library/style.min.css?ver=5.6.1
0
8212
https://freakonomics.com/wp-content/themes/freako_2.0/css/main.css?v=1.76
0
6649
https://freakonomics.com/wp-content/themes/freako_2.0/lib/main.js?v=1.71
0
6575
https://freakonomics.com/wp-includes/js/wp-emoji-release.min.js?ver=5.6.1
0
5034
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_itunes.png
0
4369
https://freakonomics.com/wp-content/themes/freako_2.0/images/button_surprise_me.png
0
3701
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/css/frontend.min.css?ver=7.15.1
0
3272
https://freakonomics.com/wp-content/plugins/google-analytics-premium/assets/js/frontend.min.js?ver=7.15.1
0
3137
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_twitter.png
0
2876
https://freakonomics.com/wp-content/themes/freako_2.0/images/newsletter_icon.png
0
2359
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_fb.png
0
2252
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_download.png?v=1.1
0
1555
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_close.png
0
1448
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_volume.png?v=1.4
0
1436
https://freakonomics.com/wp-content/themes/freako_2.0/images/player_play.png?v=1.1
0
1333
https://freakonomics.com/wp-content/themes/freako_2.0/images/sprite_burger.png
0
1325
https://freakonomics.com/wp-content/themes/freako_2.0/images/icon_contact.png
0
992
https://freakonomics.com/wp-content/themes/freako_2.0/css/normalize.css
0
991
http://tracking.aegpresents.com/universalpixel/universalpixel.js?t=1612828800000
0
880
https://p.adsymptotic.com/d/px/?_pid=16218&_psign=0aa5badf92527f7732e22463d6fa4dbc&coopa=0&gdpr=0&gdpr_consent=&_puuid=bb1a40e0-e8b2-4ad1-8b52-52120875e7ea&_expected_cookie=9db7226bf171532e714b9184e7e401f9
0
737
https://freakonomics.disqus.com/count.js
300000
1572
https://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
600000
1040
https://freakonomics.disqus.com/count-data.js?1=125851
600000
778
https://connect.facebook.net/signals/config/217011611820041?v=2.9.33&r=stable
1200000
72402
https://connect.facebook.net/en_US/fbevents.js
1200000
25003
http://www.google-analytics.com/analytics.js
7200000
19274
https://snap.licdn.com/li.lms-analytics/insight.min.js
25901000
2169
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/oswald/v36/TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiZSSShiA.woff2
3.9729999843985
https://fonts.gstatic.com/s/creteround/v9/55xoey1sJNPjPiv1ZZZrxK170b3iKWxM.woff2
5.4570001084358
Reduce the impact of third-party code — Third-party code blocked the main thread for 410 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
30419
207.004
97912
74.788
92406
69.28
19898
55.252
26910
0
4831
0
4558
0
1571
0
58

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of freakonomics.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Freakonomics.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Freakonomics.com may provide relevant information that dialogue cannot, by using audio descriptions.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
09
30

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
57

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that freakonomics.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
2.1.3
WordPress
5.6.1
core-js
3.0.0: pure
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 15 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://freakonomics.com/
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
http://freakonomics.disqus.com/count.js
http://www.google-analytics.com/analytics.js
http://tracking.aegpresents.com/universalpixel/universalpixel.js?t=1612828800000
http://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
http://freakonomics.disqus.com/count-data.js?1=125851
http://tracking.aegpresents.com/sp_2_16_3.js
http://b.aegpresents.com/com.snowplowanalytics.snowplow/tp2
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://freakonomics.com/wp-content/uploads/2020/02/Freakonomics_WebButtons_SubscribeNow_300wd.png
353 x 166
300 x 141
927 x 436
https://freakonomics.com/wp-content/themes/freako_2.0/images/logo.png
228 x 52
228 x 52
599 x 137

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
URL
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
http://freakonomics.com/
Access to XMLHttpRequest at 'https://freakonomics.com/wp-json/wp-statistics/v2/hit?_=1612692173&_wpnonce=275c3e4cc1&wp_statistics_hit_rest=yes&browser=Unknown&platform=Unknown&version=Unknown&referred=https://freakonomics.com&ip=127.0.0.1&exclusion_match=yes&exclusion_reason=CrawlerDetect&ua=BLP_bbot/0.1&track_all=1&timestamp=1612674173&current_page_type=home&current_page_id=0&search_query&page_uri=/&user_id=0' from origin 'http://freakonomics.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.
https://www.facebook.com/tr/
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector
https://freakonomics.com/wp-json/wp-statistics/v2/hit?_=1612692173&_wpnonce=275c3e4cc1&wp_statistics_hit_rest=yes&browser=Unknown&platform=Unknown&version=Unknown&referred=https://freakonomics.com&ip=127.0.0.1&exclusion_match=yes&exclusion_reason=CrawlerDetect&ua=BLP_bbot/0.1&track_all=1&timestamp=1612674173&current_page_type=home&current_page_id=0&search_query&page_uri=/&user_id=0
Failed to load resource: net::ERR_FAILED
93

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for freakonomics.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freakonomics.com on mobile screens.
Document uses legible font sizes — 96.2% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.article_list article footer, .feature_content_inner footer
2.11%
11.25px
#footer_copyright p
1.69%
11.25px
96.20%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
39

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of freakonomics.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freakonomics.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 15 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://freakonomics.com/
http://freakonomics.com/wp-content/uploads/2020/08/nsq.fbthumbnail-550x288.png
http://freakonomics.com/wp-content/uploads/2020/08/pima.fbthumbnail.630px-550x289.png
http://freakonomics.com/wp-content/uploads/2020/08/fr.fbthumbnail-550x289.png
http://freakonomics.com/wp-content/uploads/2016/01/Freakonomics-Paperback-298x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/SuperFreak-Paperback-300x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/Think-like-a-Freak-Paperback-299x450.jpg
http://freakonomics.com/wp-content/uploads/2016/01/When-To-Rob-A-Bank-Hard-Cover-296x450.jpg
http://freakonomics.disqus.com/count.js
http://www.google-analytics.com/analytics.js
http://tracking.aegpresents.com/universalpixel/universalpixel.js?t=1612828800000
http://freakonomics.disqus.com/count-data.js?1=125699&1=125727&1=125745&1=125766&1=125768&1=125786&1=125809&1=125814&1=125823&1=125828
http://freakonomics.disqus.com/count-data.js?1=125851
http://tracking.aegpresents.com/sp_2_16_3.js
http://b.aegpresents.com/com.snowplowanalytics.snowplow/tp2
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 52.116.199.28
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
SoftLayer Technologies Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 184.25.36.36
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 4.5/5
WOT Trustworthiness: 91/100
WOT Child Safety: 91/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: freakonomics.com
Issued By: R3
Valid From: 6th February, 2021
Valid To: 7th May, 2021
Subject: CN = freakonomics.com
Hash: c3fdc6f9
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04EF43B16571F109BB9895E64354DD10EE4C
Serial Number (Hex): 04EF43B16571F109BB9895E64354DD10EE4C
Valid From: 6th February, 2024
Valid To: 7th May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
Timestamp : Feb 6 11:35:47.452 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:C5:A0:5F:94:60:D7:D2:2D:FA:45:23:
E5:13:48:1A:02:8C:DB:A0:FC:B8:32:75:9A:F3:B5:59:
31:7B:F6:D9:11:02:20:75:52:30:EB:C6:DD:45:AD:7D:
69:E3:F5:03:2D:E3:EB:36:7C:82:0C:E2:52:ED:C4:0E:
85:C1:62:06:65:A2:B7
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Feb 6 11:35:47.474 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E4:FC:93:F2:2B:4B:64:18:D9:4B:F2:
A9:1E:3A:28:35:53:AE:7D:A9:5A:C7:A3:8A:B6:93:BC:
A7:88:9D:6A:0D:02:21:00:86:3A:9B:F1:E3:A9:0C:D9:
75:20:65:73:5E:59:D1:14:D3:B0:76:9F:EF:26:E6:9F:
4B:68:D1:6F:31:82:F3:39
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.freakonomics.com
DNS:freakonomics.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
freakonomics.com. 52.116.199.28 IN 599

NS Records

Host Nameserver Class TTL
freakonomics.com. ns77.domaincontrol.com. IN 3599
freakonomics.com. ns78.domaincontrol.com. IN 3599

MX Records

Priority Host Server Class TTL
20 freakonomics.com. ALT1.ASPMX.L.GOOGLE.com. IN 3599
30 freakonomics.com. ALT2.ASPMX.L.GOOGLE.com. IN 3599
10 freakonomics.com. ASPMX.L.GOOGLE.com. IN 3599
40 freakonomics.com. ASPMX2.GOOGLEMAIL.com. IN 3599
50 freakonomics.com. ASPMX3.GOOGLEMAIL.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
freakonomics.com. ns77.domaincontrol.com. dns.jomax.net. 21599

TXT Records

Host Value Class TTL
freakonomics.com. google-site-verification=Oux8H2o4IW-F6Bu3EHuBKxe3HOjy5SDQfFHvtheGWQY IN 3599
freakonomics.com. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 8th February, 2021
Content-Type: text/html; charset=UTF-8
Vary: User-Agent,Accept-Encoding
Last-Modified: 7th February, 2021
Content-Length: 11519
Age: 0
ETag: W/"a5b6-5babc2829cf80-gzip"
X-Cache: HIT
X-Cache-Hits: 2
Accept-Ranges: bytes
Connection: keep-alive

Whois Lookup

Created: 23rd October, 2003
Changed: 12th December, 2018
Expires: 23rd October, 2021
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns77.domaincontrol.com
ns78.domaincontrol.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
Owner Post Code: 85260
Owner City: Scottsdale
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: FREAKONOMICS.COM@domainsbyproxy.com
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Post Code: 85260
Admin City: Scottsdale
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: FREAKONOMICS.COM@domainsbyproxy.com
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Post Code: 85260
Tech City: Scottsdale
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: FREAKONOMICS.COM@domainsbyproxy.com
Full Whois: Domain Name: FREAKONOMICS.COM
Registry Domain ID: 105468998_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2018-12-12T08:52:40Z
Creation Date: 2003-10-23T02:38:31Z
Registrar Registration Expiration Date: 2021-10-23T02:38:31Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant City: Scottsdale
Registrant State/Province: Arizona
Registrant Postal Code: 85260
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: FREAKONOMICS.COM@domainsbyproxy.com
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin City: Scottsdale
Admin State/Province: Arizona
Admin Postal Code: 85260
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: FREAKONOMICS.COM@domainsbyproxy.com
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech City: Scottsdale
Tech State/Province: Arizona
Tech Postal Code: 85260
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: FREAKONOMICS.COM@domainsbyproxy.com
Name Server: NS77.DOMAINCONTROL.COM
Name Server: NS78.DOMAINCONTROL.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-02-08T00:56:33Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
ns77.domaincontrol.com 97.74.108.49
ns78.domaincontrol.com 173.201.76.49
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$73,537,675 USD 5/5
0/5
0/5
$4,794,933,151 USD 5/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address