72.3 sec in total
14.6 sec
46.1 sec
11.6 sec
Welcome to 22444.com homepage info - get ready to check 22444 best content right away, or after learning these important things about 22444.com
Visit 22444.comWe analyzed 22444.com page load time and found that the first response time was 14.6 sec and then it took 57.7 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 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
22444.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value3.3 s
70/100
25%
Value5.7 s
51/100
10%
Value1,480 ms
14/100
30%
Value0.026
100/100
15%
Value8.5 s
38/100
10%
14583 ms
484 ms
580 ms
785 ms
7793 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 29% of them (33 requests) were addressed to the original 22444.com, 20% (23 requests) were made to 899111.com and 6% (7 requests) were made to Kj.888lhc.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Pcookie.cnzz.com.
Page size can be reduced by 467.8 kB (64%)
730.1 kB
262.3 kB
In fact, the total size of 22444.com main page is 730.1 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 331.4 kB which makes up the majority of the site volume.
Potential reduce by 270.9 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 270.9 kB or 82% of the original size.
Potential reduce by 41.7 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, 22444 needs image optimization as it can save up to 41.7 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 145.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 145.8 kB or 64% of the original size.
Potential reduce by 9.3 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. 22444.com needs all CSS files to be minified and compressed as it can save up to 9.3 kB or 66% of the original size.
Number of requests can be reduced by 45 (45%)
101
56
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 22444. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
22444.com
14583 ms
index.css
484 ms
1234.js
580 ms
ttt1.gif
785 ms
bg.gif
7793 ms
ttt2.gif
784 ms
22.gif
7490 ms
ttt5.gif
690 ms
ttt6.gif
699 ms
88.gif
11000 ms
ttt8.gif
119 ms
top.gif
223 ms
top1.jpg
740 ms
click.aspx
1276 ms
click.aspx
1259 ms
click.aspx
403 ms
ttt3.gif
118 ms
ttt4.gif
117 ms
gd.js
20148 ms
004.gif
902 ms
dibu.js
204 ms
icon_top_5.gif
105 ms
icon_reply.gif
194 ms
icon_top_3.gif
194 ms
B.html
571 ms
001.htm
3793 ms
002.htm
3450 ms
003.htm
4609 ms
ttt7.gif
115 ms
006.htm
8920 ms
004.htm
6538 ms
tj1.gif
3643 ms
fhsy.jpg
5877 ms
fbtz.jpg
5953 ms
zczh.jpg
5405 ms
xgmm.jpg
5437 ms
xckj.jpg
6238 ms
smzt.jpg
5878 ms
am.gif
320 ms
xbt.jpg
6172 ms
wdlx.jpg
6118 ms
stat.php
4158 ms
jquery.min.js
19850 ms
icon_top_2.gif
5815 ms
23567.gif
699 ms
icon_top_1.gif
4184 ms
2012112701965543.png
1085 ms
icon_top_3.gif
330 ms
363888.gif
3606 ms
7843.gif
4607 ms
89012.gif
235 ms
22444.html
495 ms
icon_topic.gif
3103 ms
i.gif
274 ms
jing.gif
392 ms
tj1.gif
115 ms
stat.htm
2087 ms
core.php
1837 ms
stat.htm
2082 ms
01.htm
119 ms
118111.gif
723 ms
new1.gif
108 ms
9.gif
930 ms
9.gif
985 ms
click.aspx
552 ms
click.aspx
36 ms
app.gif
4581 ms
app.gif
1842 ms
title_bg.gif
19676 ms
128.gif
488 ms
pujing.gif
89 ms
iocs06.gif
81 ms
enter.gif
137 ms
into.gif
234 ms
aomen.gif
1607 ms
128.gif
2618 ms
128.gif
113 ms
dingbu.gif
93 ms
007.htm
1462 ms
008.htm
597 ms
02.htm
10988 ms
010.htm
3943 ms
dibu.html
455 ms
03.htm
735 ms
009.htm
578 ms
tuku.htm
581 ms
qnzl.htm
1527 ms
A.html
475 ms
b11.jpg
411 ms
hot11.gif
296 ms
d.gif
408 ms
titBg.jpg
467 ms
ararar.gif
141 ms
006.jpg
5681 ms
am.gif
167 ms
style.css
141 ms
caihot.gif
313 ms
stat.htm
285 ms
9.gif
939 ms
qnzl.htm
282 ms
bg1.png
147 ms
caihotb.png
219 ms
jilu.png
217 ms
gsbj.jpg
121 ms
shell_v2.js
3894 ms
jquery.min.js
349 ms
jquery.min.js
369 ms
jquery.min.js
281 ms
app.gif
20435 ms
logger.js
2299 ms
bds_s_v2.js
4545 ms
bdsstyle.css
400 ms
l7.gif
278 ms
22444.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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
22444.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
22444.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
ZH
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 22444.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), while the claimed language is Chinese. Our system also found out that 22444.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.
22444.com
Open Graph description is not detected on the main page of 22444. 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: