2.8 sec in total
520 ms
2.1 sec
199 ms
Visit 20thcenturyblog.com now to see the best up-to-date 20th Century Blog content and also check out these interesting facts you probably never knew about 20thcenturyblog.com
By Carrie O'Mahoney & Katie McGarr
Visit 20thcenturyblog.comWe analyzed 20thcenturyblog.com page load time and found that the first response time was 520 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
20thcenturyblog.com performance score
520 ms
91 ms
118 ms
99 ms
105 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 20thcenturyblog.com, 18% (16 requests) were made to Static.xx.fbcdn.net and 14% (12 requests) were made to S2.wp.com. The less responsive or slowest element that took the longest time to load (520 ms) belongs to the original domain 20thcenturyblog.com.
Page size can be reduced by 596.6 kB (46%)
1.3 MB
687.6 kB
In fact, the total size of 20thcenturyblog.com main page is 1.3 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. 70% of websites need less resources to load. Javascripts take 776.9 kB which makes up the majority of the site volume.
Potential reduce by 30.4 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 30.4 kB or 73% of the original size.
Potential reduce by 1.4 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. 20th Century Blog images are well optimized though.
Potential reduce by 550.9 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 550.9 kB or 71% of the original size.
Potential reduce by 13.9 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. 20thcenturyblog.com needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 62% of the original size.
Number of requests can be reduced by 49 (64%)
76
27
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 20th Century Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
20thcenturyblog.com
520 ms
91 ms
css
118 ms
99 ms
global.css
105 ms
98 ms
style.css
88 ms
gprofiles.js
110 ms
wpgroho.js
94 ms
95 ms
104 ms
tiled-gallery.css
100 ms
108 ms
widgets.js
73 ms
101 ms
725X1342.skimlinks.js
90 ms
w.js
68 ms
merriweather.css
23 ms
global-print.css
2 ms
default-header.jpg
84 ms
sdk.js
164 ms
platform.js
80 ms
grace-of-monaco.jpg
80 ms
widgets.js
78 ms
25 ms
hovercard.css
38 ms
services.css
69 ms
Genericons.svg
10 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
9 ms
Aleo-Bold.woff
15 ms
Aleo-Regular-webfont.woff
14 ms
Aleo-Light-webfont.woff
15 ms
Noticons.svg
15 ms
BaABdRAi2AAAA
7 ms
merriweather-bold-webfont.ttf
14 ms
merriweather-regular-webfont.ttf
12 ms
merriweather-light-webfont.ttf
24 ms
g.gif
15 ms
g.gif
14 ms
g.gif
13 ms
grace-of-monaco.jpg
144 ms
index.html
13 ms
jquery.js
4 ms
postmessage.js
2 ms
jed.js
5 ms
underscore.min.js
4 ms
43 ms
xd_arbiter.php
141 ms
xd_arbiter.php
292 ms
jquery.wpcom-proxy-request.js
3 ms
34 ms
4 ms
follow-rest.js
18 ms
batch
62 ms
http%3A%2F%2F20thcenturyblog.com
36 ms
page.php
211 ms
style.css
11 ms
k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff
28 ms
link
10 ms
track.php
6 ms
Xr6T9jq_7DM.css
168 ms
lnL0YI3IxWI.css
206 ms
fG0y3ka9ETY.css
246 ms
q68gy-v_YMF.js
352 ms
YvxwM8R7ol8.js
352 ms
ihptErjAmMX.js
318 ms
3So47A9WcrL.js
283 ms
cUsKAwzqrQw.js
378 ms
1501734_436755433118941_241779025_n.jpg
182 ms
safe_image.php
295 ms
1453260_416663621794789_747035409_n.jpg
214 ms
12814171_10207287414156488_3829480867651240544_n.jpg
263 ms
12705464_181876368842640_1775764652364442511_n.jpg
290 ms
12249759_1063724403658018_683777120711471340_n.jpg
358 ms
1914632_959156240787040_710450243020300361_n.jpg
300 ms
10357173_510134325781051_7047910141636910370_n.jpg
303 ms
10441123_507723586022125_6358713487918977042_n.jpg
301 ms
10341638_507714902689660_2039392291011422524_n.jpg
305 ms
10390387_501447089983108_8388137752241538313_n.jpg
329 ms
wL6VQj7Ab77.png
50 ms
s7jcwEQH7Sx.png
49 ms
GtIpNnEyqq_.png
48 ms
lRyN50VcaFW.js
52 ms
R9a_DtVRZgv.js
43 ms
cUDgRFxaoIk.js
45 ms
0JBr1QHp8Gi.js
41 ms
kDOzhTr2W91.js
43 ms
20thcenturyblog.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 20thcenturyblog.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 20thcenturyblog.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.
20thcenturyblog.com
Open Graph data is detected on the main page of 20th Century Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: