42.5 sec in total
2.9 sec
39.2 sec
376 ms
Click here to check amazing Eenot content for China. Otherwise, check out these important facts you probably never knew about eenot.com
首页
Visit eenot.comWe analyzed Eenot.com page load time and found that the first response time was 2.9 sec and then it took 39.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
eenot.com performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value3.7 s
59/100
25%
Value7.0 s
33/100
10%
Value1,020 ms
26/100
30%
Value0.003
100/100
15%
Value11.6 s
18/100
10%
2937 ms
1053 ms
798 ms
2832 ms
904 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 93% of them (75 requests) were addressed to the original Eenot.com, 2% (2 requests) were made to Hm.baidu.com and 2% (2 requests) were made to Pub.idqqimg.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Eenot.com.
Page size can be reduced by 433.5 kB (22%)
2.0 MB
1.6 MB
In fact, the total size of Eenot.com main page is 2.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. 30% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 73.5 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 73.5 kB or 78% of the original size.
Potential reduce by 91.8 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. Eenot images are well optimized though.
Potential reduce by 180.1 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 180.1 kB or 68% of the original size.
Potential reduce by 88.2 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. Eenot.com needs all CSS files to be minified and compressed as it can save up to 88.2 kB or 81% of the original size.
Number of requests can be reduced by 11 (14%)
77
66
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eenot. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
www.eenot.com
2937 ms
style_1_common.css
1053 ms
style_1_forum_index.css
798 ms
common.js
2832 ms
forum.js
904 ms
eenot_pace.js
2778 ms
jQuery.js
13136 ms
eenotjs.js
1400 ms
logging.js
1747 ms
md5.js
3226 ms
api.php
2128 ms
api.php
2262 ms
jqueryIstudy.js
2867 ms
For_KF_Dialog.js
2316 ms
discuz_tips.js
475 ms
hm.js
1012 ms
logo.png
395 ms
qq_login.gif
709 ms
6e92810040c9f1a5d50307a834694ac2.jpg
13428 ms
0db1eb132bb4bc757520bbabb1592964.jpg
7491 ms
eef2a26cbae2c30190063bb20e3cdcfd.jpg
20444 ms
e37153d67beddc3d0ce6ac54f70369fc.jpg
20445 ms
2646bbc84488f50d772ca59fa389bcbb.jpg
11151 ms
140721p16x4zrfhlvgbbp7.jpg
4692 ms
collapsed_no.gif
5034 ms
common_118_icon.png
5941 ms
common_69_icon.png
7455 ms
common_2_icon.png
8392 ms
common_103_icon.png
8610 ms
common_158_icon.png
10125 ms
common_157_icon.png
10982 ms
common_124_icon.png
10455 ms
common_63_icon.png
11111 ms
forum.gif
11364 ms
forum_new.gif
11443 ms
809f086273d936ce40c49420efe428c0.jpg
16722 ms
09d486a155502eb8618ddcf0a7dd5036.jpg
15594 ms
b343b59f11f650a8db70847e365fb0e4.jpg
12876 ms
48a62cd0a900362a2f2055f93c63e891.jpg
15987 ms
common_extra.js
19447 ms
hm.gif
739 ms
s.js
3138 ms
weixin.jpg
9741 ms
site_qq.jpg
7602 ms
security.png
7557 ms
202127wud33uio4jevjubh.gif
10032 ms
203036vyw9mt1tyt60py90.gif
6762 ms
chart.png
6606 ms
noavatar_small.gif
6376 ms
noavatar_small.gif
6279 ms
noavatar_small.gif
5903 ms
noavatar_small.gif
5754 ms
noavatar_small.gif
5427 ms
allico.gif
5488 ms
button_121.gif
486 ms
button_121.gif
474 ms
noavatar_small.gif
5292 ms
noavatar_small.gif
5129 ms
sign.gif
7188 ms
noavatar_small.gif
5043 ms
noavatar_small.gif
5021 ms
noavatar_small.gif
4866 ms
noavatar_small.gif
4696 ms
float_s.gif
5083 ms
noavatar_small.gif
4829 ms
noavatar_small.gif
4817 ms
noavatar_small.gif
4535 ms
noavatar_small.gif
4312 ms
noavatar_small.gif
4404 ms
noavatar_small.gif
4237 ms
noavatar_small.gif
4207 ms
noavatar_small.gif
4124 ms
noavatar_small.gif
4071 ms
noavatar_small.gif
4109 ms
noavatar_small.gif
4007 ms
noavatar_small.gif
3866 ms
noavatar_small.gif
3886 ms
float_bg.gif
3727 ms
social-media.png
3661 ms
logo.png
3225 ms
scrolltop.png
2751 ms
eenot.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
eenot.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
eenot.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eenot.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eenot.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.
eenot.com
Open Graph description is not detected on the main page of Eenot. 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: