15.6 sec in total
4 sec
6.3 sec
5.3 sec
Click here to check amazing E Chen content for United States. Otherwise, check out these important facts you probably never knew about echen.me
Visit echen.meWe analyzed Echen.me page load time and found that the first response time was 4 sec and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
echen.me performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value3.2 s
72/100
25%
Value9.1 s
14/100
10%
Value7,170 ms
0/100
30%
Value0
100/100
15%
Value26.2 s
0/100
10%
4002 ms
49 ms
25 ms
33 ms
6 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Echen.me, 40% (47 requests) were made to Dl.dropboxusercontent.com and 25% (30 requests) were made to Dl.dropbox.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Echen.me.
Page size can be reduced by 1.7 MB (25%)
7.0 MB
5.3 MB
In fact, the total size of Echen.me 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 5.9 MB which makes up the majority of the site volume.
Potential reduce by 152.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 152.4 kB or 77% of the original size.
Potential reduce by 904.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, E Chen needs image optimization as it can save up to 904.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 581.8 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 581.8 kB or 70% of the original size.
Potential reduce by 90.0 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. Echen.me needs all CSS files to be minified and compressed as it can save up to 90.0 kB or 82% of the original size.
Number of requests can be reduced by 24 (29%)
82
58
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Chen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
echen.me
4002 ms
blog.echen.me
49 ms
main.css
25 ms
jquery.min.js
33 ms
widgets.js
6 ms
reset.css
20 ms
pygment.css
26 ms
typogrify.css
26 ms
css
28 ms
body-bg.jpg
113 ms
amazon-related-books.png
426 ms
network
110 ms
comparison
105 ms
MathJax.js
99 ms
fools-assassin-rating.png
374 ms
anne-rice.png
381 ms
a1-ratings.png
351 ms
bad-categories.png
349 ms
amazon-bn-google.png
372 ms
fault-in-our-stars.png
476 ms
the-strain.png
490 ms
google-atrocity.png
487 ms
soylent-age.png
1170 ms
soylent-effect.png
551 ms
regression-discontinuity.png
613 ms
uploads-calendar.png
695 ms
1_celebrity.png
300 ms
4_network.png
302 ms
2_network.png
300 ms
2_friend.png
303 ms
training_full_followers.png
302 ms
training_full_followees.png
302 ms
test_followers.png
304 ms
test_followees.png
316 ms
317_propagation.png
317 ms
317_following_followers.png
316 ms
317_log_ratio.png
318 ms
317_propagation_local.png
320 ms
1_sim_by_followers.png
318 ms
1_single_connection.png
320 ms
1-regularized.png
320 ms
317_unregularized.png
321 ms
317_regularized.png
322 ms
rf-importance-scores.png
321 ms
pagerank_vs_is_followed_by_v2.png
323 ms
united-states.png
325 ms
united_states_binned.png
323 ms
popvssoda.png
323 ms
world-map.png
324 ms
fizzy-mineral-tonic.png
326 ms
superbowl-snacks.png
325 ms
xmas.png
327 ms
shitguysandgirlssay.png
328 ms
sandy-outages.png
329 ms
sandy-spread.png
327 ms
electoral-map.png
329 ms
tweet.04d20138f67ab41d6b4af6cc583926d9.js
180 ms
BCFBp4rt5gxxFrX6F12DKvesZW2xOQ-xsNqO47m55DA.woff
118 ms
jquery-1.7.1.min-65245b2f8d7c225a5a031ad58bba9194.js
153 ms
jquery.tablesorter.min-f534d8792f8e1526f3f298c8a3410d5d.js
41 ms
jquery-ui-1.8.19.custom.min-a14a9e65a34749cbb0ec1d987a364f8b.js
178 ms
bootstrap.min-7a1d52d9737ba7d1b5fa2c4058f40e95.js
45 ms
bootstrap.min-d96bbcbd60ea9dcf47b027aafe949c9a.css
116 ms
bootstrap-responsive.min-eb43e8a9437abf47efabaf6e1042cc0f.css
45 ms
underscore-min-f856f7863147f1288b13209ad256dd63.js
116 ms
d3.v2.min-ea9b75b49b481e975a08cda9ccf0f1d7.js
177 ms
main-454fd630d4165b98cce06d9ba4443f3b.css
116 ms
network-89766ffb44c45d23759cdf836587bd79.js
175 ms
comparison-c51abbdbf23b57798f6cfe36c33b075b.js
176 ms
TeX-AMS-MML_HTMLorMML.js
28 ms
1_network.png
495 ms
1_friend1.png
518 ms
1_friend2.png
522 ms
1_untrimmed.png
657 ms
jax.js
124 ms
1_celebrity.png
656 ms
1_network.json
92 ms
2_network.png
561 ms
4_network.png
569 ms
training_full_followers.png
559 ms
training_full_followees.png
743 ms
2_friend.png
784 ms
test_followers.png
700 ms
syndication
161 ms
tweets.json
234 ms
test_followees.png
728 ms
317_following_followers.png
714 ms
317_propagation.png
870 ms
1_sim_by_followers.png
874 ms
317_log_ratio.png
882 ms
317_propagation_local.png
905 ms
1_single_connection.png
986 ms
1-regularized.png
1009 ms
317_unregularized.png
1042 ms
rf-importance-scores.png
1068 ms
317_regularized.png
1066 ms
pagerank_vs_is_followed_by_v2.png
1065 ms
united_states_binned.png
1217 ms
popvssoda.png
1174 ms
united-states.png
1308 ms
world-map.png
1252 ms
superbowl-snacks.png
1231 ms
fizzy-mineral-tonic.png
1244 ms
xmas.png
1339 ms
shitguysandgirlssay.png
1381 ms
sandy-spread.png
1423 ms
sandy-outages.png
1429 ms
electoral-map.png
1758 ms
fontdata.js
10 ms
MathJax_Main-Regular.woff
9 ms
MathJax_Math-Italic.woff
11 ms
MathJax_Size1-Regular.woff
12 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
20 ms
tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css
15 ms
b46ab844e61e58be4415f3485be4d067_normal.jpeg
124 ms
GEerkDQ0_normal.jpeg
151 ms
a83887e6a5787acdc18835b407b5303e_normal.png
185 ms
jot.html
5 ms
echen.me accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
echen.me best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
echen.me SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Echen.me 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 Echen.me 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.
echen.me
Open Graph description is not detected on the main page of E Chen. 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: