43.9 sec in total
734 ms
42.6 sec
594 ms
Visit zdtxt.com now to see the best up-to-date Zdtxt content for China and also check out these interesting facts you probably never knew about zdtxt.com
紫蝶休闲家园-原创写作发布,娱乐休闲,寻书互助,贴图水吧,书生意气,心情物语,好看的电子书交流
Visit zdtxt.comWe analyzed Zdtxt.com page load time and found that the first response time was 734 ms and then it took 43.2 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.
zdtxt.com performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.4 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
734 ms
1852 ms
93 ms
65 ms
65 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 88% of them (86 requests) were addressed to the original Zdtxt.com, 5% (5 requests) were made to Bdimg.share.baidu.com and 2% (2 requests) were made to Js.users.51.la. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Cpro.baidu.com.
Page size can be reduced by 232.7 kB (43%)
537.1 kB
304.4 kB
In fact, the total size of Zdtxt.com main page is 537.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. Images take 265.9 kB which makes up the majority of the site volume.
Potential reduce by 72.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 72.2 kB or 78% of the original size.
Potential reduce by 37.0 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, Zdtxt needs image optimization as it can save up to 37.0 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 109.3 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 109.3 kB or 69% of the original size.
Potential reduce by 14.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. Zdtxt.com needs all CSS files to be minified and compressed as it can save up to 14.2 kB or 69% of the original size.
Number of requests can be reduced by 45 (47%)
95
50
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zdtxt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
zdtxt.com
734 ms
www.zdtxt.com
1852 ms
wind-reset.css
93 ms
core.js
65 ms
pw_ajax.js
65 ms
wei.js
67 ms
c.js
20043 ms
picplayer.js
64 ms
Deploy.js
81 ms
popup.js
124 ms
1127193.js
876 ms
i.js
11926 ms
global.js
108 ms
pw_jobcenter.js
110 ms
Compatibility.js
37 ms
zh_cn.js
51 ms
foot.gif
64 ms
close.gif
33 ms
bg.png
64 ms
54_269850_09e2f4a202e1025.png
100 ms
rss.png
66 ms
2_639577_a63609f6dda9256.png
221 ms
2_639577_3079d5661347986.jpg
69 ms
4_767187_5f75452a969a1c8.jpg
171 ms
4_767187_60bcdd99b71eaba.jpg
157 ms
4_767187_ed1017b6fd222bc.jpg
232 ms
cate_fold.gif
136 ms
old.gif
162 ms
44_175133_eae6739ad2d61ca.gif
203 ms
1.gif
222 ms
2.gif
224 ms
3.gif
232 ms
44_175133_15e263f1e3d5181.gif
265 ms
44_175133_1decd22fb384eb8.gif
280 ms
44_175133_6365962baa35825.gif
282 ms
44_175133_9d8ce3e3e55acf0.gif
285 ms
44_175133_7e8d72d14871ee5.gif
291 ms
new.gif
293 ms
44_175133_dbb6a7675e6e28d.gif
328 ms
44_175133_0fe66f6975eabe9.gif
346 ms
44_175133_15eb7aee28c1fb6.gif
345 ms
44_175133_2ba057fcb631e37.gif
346 ms
44_175133_5ce79be9347ef74.gif
354 ms
44_175133_1cab3c764f502d9.gif
356 ms
44_175133_1e6548ae1bfd815.gif
389 ms
44_175133_1d4b0541ea68bc0.gif
408 ms
44_175133_4641cf33c14ea8c.gif
408 ms
44_175133_c3468e97f787248.gif
411 ms
44_175133_8bf21a5d5c9da98.gif
417 ms
44_175133_0b2c1e899c0d9de.gif
418 ms
44_175133_65a0d1658fb355e.gif
450 ms
44_175133_c63a925196eb9a0.gif
469 ms
44_175133_e7dd8a09111a2cc.gif
471 ms
44_175133_68323970f721a6e.gif
451 ms
foot.gif
427 ms
44_175133_a44ee36d687e724.gif
424 ms
44_175133_414fed3aee515be.gif
453 ms
44_175133_409acb3e676179a.gif
443 ms
44_175133_e022f2827de32d7.gif
408 ms
44_175133_0dad3c56594a23f.gif
389 ms
44_175133_57a7dc77e1e5f5a.gif
389 ms
44_175133_ecc2bc06bdbaae8.gif
383 ms
lock.gif
380 ms
44_175133_30b3f0fa11b64a9.gif
385 ms
44_175133_bc814ccd550c949.gif
384 ms
share.gif
384 ms
online.gif
383 ms
15.gif
385 ms
14.gif
383 ms
13.gif
386 ms
12.gif
387 ms
11.gif
384 ms
10.gif
386 ms
3.gif
386 ms
4.gif
379 ms
5.gif
386 ms
34.gif
386 ms
35.gif
385 ms
6.gif
382 ms
logo.png
382 ms
zd5.png
20000 ms
nav-bg.png
89 ms
nav-search.png
89 ms
shortcut.gif
85 ms
nav-cur.png
85 ms
select_arrow.gif
85 ms
anc.png
68 ms
focus1.gif
77 ms
focus2.gif
81 ms
tr2.png
79 ms
icon_8.gif
13264 ms
14764694.js
4032 ms
icon_9.gif
9847 ms
shell_v2.js
5642 ms
logger.js
7812 ms
bds_s_v2.js
5693 ms
bdsstyle.css
1632 ms
r1.gif
616 ms
zdtxt.com accessibility score
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
Document doesn't have a <title> element
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
zdtxt.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
zdtxt.com SEO score
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zdtxt.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 Zdtxt.com main page’s claimed encoding is gbk. 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.
zdtxt.com
Open Graph description is not detected on the main page of Zdtxt. 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: