12.2 sec in total
2.5 sec
8.8 sec
879 ms
Welcome to 5522111.com homepage info - get ready to check 5522111 best content right away, or after learning these important things about 5522111.com
Visit 5522111.comWe analyzed 5522111.com page load time and found that the first response time was 2.5 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
5522111.com performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value1.5 s
100/100
10%
Value120 ms
97/100
30%
Value0.143
78/100
15%
Value2.9 s
96/100
10%
2502 ms
841 ms
630 ms
653 ms
460 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 80% of them (80 requests) were addressed to the original 5522111.com, 4% (4 requests) were made to Bm.5522111.com and 2% (2 requests) were made to Count31.51yes.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Count31.51yes.com.
Page size can be reduced by 438.9 kB (83%)
527.2 kB
88.2 kB
In fact, the total size of 5522111.com main page is 527.2 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. HTML takes 372.7 kB which makes up the majority of the site volume.
Potential reduce by 347.8 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. This page needs HTML code to be minified as it can gain 166.2 kB, which is 45% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 347.8 kB or 93% of the original size.
Potential reduce by 12.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. Obviously, 5522111 needs image optimization as it can save up to 12.4 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 57.6 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 57.6 kB or 65% of the original size.
Potential reduce by 21.1 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. 5522111.com needs all CSS files to be minified and compressed as it can save up to 21.1 kB or 79% of the original size.
Number of requests can be reduced by 30 (32%)
94
64
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 5522111. 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 as a result speed up the page load time.
5522111.com
2502 ms
style.css
841 ms
biglive.css
630 ms
bindex.js
653 ms
gonggao.js
460 ms
mini.html
978 ms
bg.jpg
226 ms
mainliveBg.jpg
485 ms
logo.gif
229 ms
bglink.gif
226 ms
menu3.gif
443 ms
navbg.gif
444 ms
navbg_hover.gif
443 ms
4.gif
444 ms
7.gif
652 ms
5.gif
674 ms
1.gif
675 ms
2.gif
675 ms
search.htm
1329 ms
title77.gif
658 ms
btn03.gif
840 ms
goldreach.gif
892 ms
leftbar.gif
896 ms
title44.gif
1058 ms
title66.gif
730 ms
title33.gif
556 ms
title22.gif
635 ms
title11.gif
421 ms
biglive.js
220 ms
htmlTime.js
255 ms
ad.js
398 ms
lan.js
405 ms
stat.php
1496 ms
stat.php
1690 ms
click.aspx
4543 ms
linkb.gif
443 ms
linka.gif
455 ms
logo2.gif
470 ms
index.css
895 ms
external.js
910 ms
time.js
1589 ms
search.js
702 ms
mail.js
735 ms
dingbu_nei.js
663 ms
TrojanInspect.aspx
511 ms
ch.js
224 ms
kjzb.png
449 ms
tdflagx0.gif
252 ms
20150823094314776.GIF
219 ms
20141001032011205.GIF
642 ms
20160119065942894.GIF
449 ms
20151111054513777.GIF
629 ms
20150823053827542.GIF
226 ms
20160224060127654.GIF
647 ms
20150514091451197.GIF
435 ms
20151223051102941.GIF
443 ms
20160105082636707.GIF
668 ms
20131101020859901.GIF
894 ms
20141225054748415.GIF
680 ms
20150430120904673.GIF
838 ms
20131205094149359.PNG
849 ms
20131112041517853.GIF
857 ms
20150813030008296.GIF
888 ms
20150117020432051.GIF
897 ms
20160214042400060.GIF
1968 ms
20141226015830593.GIF
1079 ms
20150430120220048.GIF
1080 ms
20150514101656181.GIF
1104 ms
20141226020722736.GIF
1111 ms
20150514101743337.GIF
1116 ms
20140124064446406.GIF
1272 ms
20131110033050650.GIF
1283 ms
20120725044319062.GIF
1324 ms
stat.htm
172 ms
core.php
1632 ms
Logo_25wht.gif
18 ms
cline.png
256 ms
tag.png
243 ms
baidu_logo.gif
255 ms
baidu_mp3.gif
253 ms
baidu_img.gif
1125 ms
baidu_post.gif
955 ms
baidu_know.gif
475 ms
baidu_baike.gif
485 ms
baidu_video.gif
500 ms
baidu_gp.gif
497 ms
mail_login.gif
697 ms
taobao.gif
1533 ms
ciba.gif
1570 ms
yahoo.gif
744 ms
sg.gif
927 ms
9.gif
1279 ms
pic.gif
629 ms
stat.htm
168 ms
core.php
445 ms
9.gif
1387 ms
ch.js
227 ms
app.gif
1326 ms
count1.gif
684 ms
app.gif
1327 ms
5522111.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.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
5522111.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
5522111.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
EN
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 5522111.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 5522111.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.
5522111.com
Open Graph description is not detected on the main page of 5522111. 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: