51.8 sec in total
11.7 sec
39.8 sec
337 ms
Visit 52eshu.com now to see the best up-to-date 52 Eshu content for South Korea and also check out these interesting facts you probably never knew about 52eshu.com
访问安全
Visit 52eshu.comWe analyzed 52eshu.com page load time and found that the first response time was 11.7 sec and then it took 40.1 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 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
52eshu.com performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value1.2 s
100/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value0.9 s
100/100
10%
11749 ms
16483 ms
2988 ms
1043 ms
2277 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 43% of them (26 requests) were addressed to the original 52eshu.com, 15% (9 requests) were made to Cpro.baidustatic.com and 10% (6 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain 52eshu.com.
Page size can be reduced by 352.2 kB (61%)
575.0 kB
222.8 kB
In fact, the total size of 52eshu.com main page is 575.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 423.8 kB which makes up the majority of the site volume.
Potential reduce by 69.2 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 69.2 kB or 81% of the original size.
Potential reduce by 2.1 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. 52 Eshu images are well optimized though.
Potential reduce by 281.0 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 281.0 kB or 66% of the original size.
Potential reduce by 17 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. 52eshu.com has all CSS files already compressed.
Number of requests can be reduced by 35 (63%)
56
21
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 52 Eshu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
52eshu.com
11749 ms
style.css
16483 ms
mainforindex.js
2988 ms
f.js
1043 ms
banner.js
2277 ms
top.js
2296 ms
2260160.js
1097 ms
count.asp
456 ms
footer.js
525 ms
body_bg.gif
522 ms
hd_arrowDown.gif
532 ms
logo.gif
522 ms
btn_search.gif
554 ms
drop_down_button.gif
860 ms
20126281242564647.jpg
20020 ms
201551118264348328.jpg
20020 ms
20155520315219994.jpg
20022 ms
wcdm
2022 ms
ad1.htm
1348 ms
menu_pic_2.gif
4329 ms
icon-search.gif
10701 ms
c.js
1028 ms
wcdm
1428 ms
strap_bg.gif
3128 ms
shell_v2.js
618 ms
bg_pic.png
6590 ms
ico_2.gif
3541 ms
ico_1.gif
3970 ms
head_bg_pic.png
4415 ms
top_pane.png
4842 ms
ico_link.gif
5305 ms
bot_bg.gif
7535 ms
logger.js
295 ms
bds_s_v2.js
706 ms
wcdm
1200 ms
wcdm
997 ms
bdsstyle.css
292 ms
getnum
910 ms
468x609999999.jpg
845 ms
wcdm
3836 ms
is.png
932 ms
sc.png
260 ms
adx.php
959 ms
reduce_bd-logo1_oper.png
516 ms
adPic.new.20150909.min.js
58 ms
bot-patch.min.js
56 ms
click.min.js
63 ms
rBEhWlJYrAEIAAAAAAACetYAYQwAAECuwP__W4AAAKS951.png
53 ms
5703cbf9N21b63008.jpg
82 ms
adx.php
741 ms
cpro.js
743 ms
adx.php
712 ms
closefeedback.min.js
508 ms
reduce_promotion_oper.png
476 ms
bd_logo.png
514 ms
bg_rb.png
544 ms
icon_12px.png
494 ms
55e40d3fN2a01189f.png
31 ms
o.htm
464 ms
wh.js
748 ms
ac.js
554 ms
52eshu.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
52eshu.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
52eshu.com SEO score
N/A
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 52eshu.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 52eshu.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
52eshu.com
Open Graph description is not detected on the main page of 52 Eshu. 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: