8.1 sec in total
36 ms
1.5 sec
6.6 sec
Visit wtfhappenedin1971.com now to see the best up-to-date WTF Happened In 1971 content for United States and also check out these interesting facts you probably never knew about wtfhappenedin1971.com
"I don't believe we shall ever have a good money again before we take the thing out of the hands of government, that is, we can't take it violently out of the hands of government, all we can...
Visit wtfhappenedin1971.comWe analyzed Wtfhappenedin1971.com page load time and found that the first response time was 36 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wtfhappenedin1971.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value5.0 s
26/100
25%
Value2.5 s
98/100
10%
Value170 ms
93/100
30%
Value0
100/100
15%
Value3.8 s
90/100
10%
36 ms
33 ms
169 ms
167 ms
191 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Wtfhappenedin1971.com, 76% (78 requests) were made to Wtfhappenedin1971home.files.wordpress.com and 6% (6 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (960 ms) relates to the external source Wtfhappenedin1971home.files.wordpress.com.
Page size can be reduced by 319.0 kB (5%)
7.0 MB
6.7 MB
In fact, the total size of Wtfhappenedin1971.com main page is 7.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.8 MB which makes up the majority of the site volume.
Potential reduce by 169.9 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 169.9 kB or 86% of the original size.
Potential reduce by 148.0 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. WTF Happened In 1971 images are well optimized though.
Potential reduce by 934 B
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 165 B
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Wtfhappenedin1971.com has all CSS files already compressed.
Number of requests can be reduced by 16 (16%)
100
84
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WTF Happened In 1971. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
wtfhappenedin1971.com
36 ms
wtfhappenedin1971.com
33 ms
169 ms
167 ms
191 ms
161 ms
176 ms
177 ms
global.css
171 ms
176 ms
hovercards.min.js
245 ms
wpgroho.js
173 ms
245 ms
246 ms
index.min.js
246 ms
244 ms
w.js
246 ms
img_0540-1_arrow.jpg
170 ms
unknown.jpeg
175 ms
wages.jpg
173 ms
wages2_arrow.jpg
151 ms
img_0658-1.jpg
144 ms
ei7oxspxgamaayl.png
158 ms
img_0727_arrow.png
198 ms
img_0601_arrow.jpg
187 ms
racial-inequality.png
179 ms
men-vs-women.jpg
185 ms
dual-income-1.jpg
184 ms
national-income.png
196 ms
ray-dalio-wealth-inequality.png
187 ms
cambells-soup.jpg
196 ms
cummulative-inflation.jpg
193 ms
img_0681_arrow-1.jpg
194 ms
cpi-basket-1.png
191 ms
efkgav8wwaenvoc.png
197 ms
ey_zm2fwsamocf9-1.png
203 ms
home-prices-amsterdam.png
385 ms
e8j1qysxsai4g5d.jpg
203 ms
unknown.jpg
202 ms
us_gold_reserves.png
200 ms
do5g42luuae65cp_1.jpg
203 ms
books.jpg
205 ms
peerreview.jpg
207 ms
currency-crashes.png
208 ms
img_1376.png
205 ms
grasp_brettonwoodstitled_arrow-1.jpg
207 ms
federdebtheldbypublic2021.jpg
314 ms
federaldebtpublic.jpg
210 ms
eifme9yu0ae8xnz.jpg
317 ms
roundcube.png
569 ms
fed-deficit-vs-gdp.png
212 ms
federal-deficit.jpg
212 ms
outlays.jpg
214 ms
bank-assets.jpg
215 ms
print.css
95 ms
g.gif
95 ms
remote-login.php
137 ms
g.gif
76 ms
g.gif
75 ms
sp-500-pe-ratio.jpg
79 ms
pe-shiller.jpg
77 ms
sp-1.jpg
73 ms
speculationproduction-1.jpg
67 ms
e90vtjfwqacj6g3.jpg
57 ms
savingsrate.jpg
47 ms
savings_gdp.jpg
46 ms
7dc2e053-b6dc-471e-a41b-1aac52be41f5.jpg
47 ms
tradebalance1.jpg
45 ms
ewuc3gru0auouse.jpeg-1.jpg
45 ms
edzn042uwaab9ss.jpg
129 ms
10-year-bond-yield.jpg
41 ms
ehq1sryxkag5iif.jpg
41 ms
energy-per-capita.png
317 ms
untitled-1.jpg
121 ms
ideological-positions.jpg
250 ms
simpler-1.jpg
232 ms
political-problems.jpg
180 ms
eyjmmocvaaic3yd.jpg
180 ms
cloture.png
181 ms
dk8rnmg-.png
488 ms
ejquitsuyaauxis.png
486 ms
unknown-4.png
451 ms
fisl9jwxiamxbvh.jpg
241 ms
incarcerationrate.jpg
243 ms
fv3zumgwyaajjil.jpg
244 ms
eqmf1inxeaaocmj.jpg
245 ms
gfwaunaw4aapfvw.jpg
245 ms
eztlkdtxsaayeda-1.png
640 ms
img_0977.jpg
373 ms
families.png
656 ms
eaqhgk4x0aad-6h.jpeg.jpg
471 ms
children-per-woman-1.jpg
440 ms
ey0djovuwaal2ri-1.jpg
503 ms
health-care-and-population.png
471 ms
eyyiyheucaug4wt.png
471 ms
image.png
473 ms
meat-consumption-copy.jpg
469 ms
image.png
467 ms
diet.jpg
545 ms
image-2.png
960 ms
cropped-nixonsquareicon.jpg
467 ms
actionbar.css
6 ms
actionbar.js
35 ms
wtfhappenedin1971.com accessibility score
wtfhappenedin1971.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
wtfhappenedin1971.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wtfhappenedin1971.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wtfhappenedin1971.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
wtfhappenedin1971.com
Open Graph description is not detected on the main page of WTF Happened In 1971. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: