8.4 sec in total
676 ms
6.9 sec
847 ms
Click here to check amazing 21 Ks content for China. Otherwise, check out these important facts you probably never knew about 21ks.net
公务员期刊网在线提供学术咨询、期刊咨询、杂志订阅服务,一站式期刊推荐咨询服务,让您省时省力!
Visit 21ks.netWe analyzed 21ks.net page load time and found that the first response time was 676 ms and then it took 7.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.
21ks.net performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value4.4 s
39/100
25%
Value6.3 s
42/100
10%
Value520 ms
56/100
30%
Value0
100/100
15%
Value6.8 s
54/100
10%
676 ms
1056 ms
413 ms
589 ms
594 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 94% of them (81 requests) were addressed to the original 21ks.net, 2% (2 requests) were made to Hm.baidu.com and 2% (2 requests) were made to Aux.soperson.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Aux.soperson.com.
Page size can be reduced by 505.4 kB (23%)
2.2 MB
1.7 MB
In fact, the total size of 21ks.net main page is 2.2 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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 99.0 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 16.5 kB, which is 14% 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 99.0 kB or 83% of the original size.
Potential reduce by 2.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. 21 Ks images are well optimized though.
Potential reduce by 216.4 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 216.4 kB or 71% of the original size.
Potential reduce by 188.0 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. 21ks.net needs all CSS files to be minified and compressed as it can save up to 188.0 kB or 60% of the original size.
Number of requests can be reduced by 19 (23%)
84
65
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 21 Ks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
21ks.net
676 ms
www.21ks.net
1056 ms
base.css
413 ms
login.css
589 ms
common.css
594 ms
base_ksnet.css
1192 ms
jquery.min.js
620 ms
jquery.form.js
835 ms
jquery.validate.js
651 ms
jquery.showDialog.js
783 ms
showDialog.css
791 ms
app.min.js
825 ms
common.js
1298 ms
header-common.js
978 ms
top_menu.js
988 ms
footer-common.js
1028 ms
mobile.js
1041 ms
svg.js
1172 ms
leyu.js
1185 ms
tk-leyuxs.js
1234 ms
cf7b_4244.jpg_260x355.jpg
209 ms
5863_43fa.jpg_260x355.jpg
200 ms
c354_11bc7.jpg_260x355.jpg
399 ms
1adca_4bb9.jpg_260x355.jpg
213 ms
1dd16_c96a.jpg_260x355.jpg
220 ms
24e3f_91b7.jpg_260x355.jpg
202 ms
3407c_10d06.jpg_260x355.jpg
398 ms
19927_13019.jpg_260x355.jpg
404 ms
27f3d_5eea.jpg_260x355.jpg
420 ms
579b_115b1.jpg_260x355.jpg
425 ms
1ae3d_dcd8.jpg_260x355.jpg
439 ms
eed2_169d7.jpg_260x355.jpg
596 ms
f8a4_10caf.jpg_260x355.jpg
598 ms
f067_2a17.jpg_260x355.jpg
604 ms
d745_87d5.jpg_260x355.jpg
628 ms
31c46_13956.jpg_260x355.jpg
635 ms
16d41_9614.jpg_260x355.jpg
655 ms
19c88_181f3.jpg_260x355.jpg
794 ms
273c7_1451a.jpg_260x355.jpg
797 ms
19860_570e.jpg_260x355.jpg
804 ms
5bd4_a53b.jpg_260x355.jpg
835 ms
1e9f6_a471.jpg_260x355.jpg
844 ms
11c6_12fd5.jpg_260x355.jpg
873 ms
197d4_7a44.jpg_260x355.jpg
989 ms
3191d_149b5.jpg_260x355.jpg
996 ms
2a71d_144c3.jpg_260x355.jpg
1002 ms
166c5_c11b.jpg_260x355.jpg
1042 ms
5081_14f14.jpg_260x355.jpg
1056 ms
235db_de94.jpg_260x355.jpg
1091 ms
1e9ad_3aa6.jpg_260x355.jpg
1187 ms
2736d_70ff.jpg_260x355.jpg
1195 ms
29820_be06.jpg_260x355.jpg
1202 ms
2a89d_d348.jpg_260x355.jpg
1250 ms
278d5_8112.jpg_260x355.jpg
1266 ms
2a386_6d71.jpg_260x355.jpg
1309 ms
27632_d676.jpg_260x355.jpg
1374 ms
10095484.js
1517 ms
hm.js
1720 ms
2a5c5_13164.jpg_260x355.jpg
1201 ms
2a8f5_1254a.jpg_260x355.jpg
1206 ms
2a8ee_42f2.jpg_260x355.jpg
1255 ms
2a3de_12adf.jpg_260x355.jpg
1271 ms
1922e_db49.jpg_260x355.jpg
1313 ms
16dca_146fd.jpg_260x355.jpg
1216 ms
27562_49cc.jpg_260x355.jpg
1201 ms
1b544_697c.jpg_260x355.jpg
1204 ms
17323_13a3a.jpg_260x355.jpg
1251 ms
186a6_9244.jpg_260x355.jpg
1268 ms
16010_a0f0.jpg_260x355.jpg
1316 ms
16601_182d8.jpg_260x355.jpg
1204 ms
1650d_14917.jpg_260x355.jpg
1210 ms
1b619_17fad.jpg_260x355.jpg
1208 ms
icon_cart.png
1253 ms
icon_logo.png
1266 ms
icon_search_gray.png
1313 ms
icon_fldh.png
1206 ms
bg_jxfw.png
1212 ms
bg_bottom_tgfa.png
1403 ms
icon_shbz.png
1248 ms
icon_footer_tel.png
1263 ms
icon_gaba.png
1310 ms
looyu.f7bf1efc8b105c9c95d249e08b3cceda.css
1318 ms
looyu.315303dff8b25e824b4bf805d7b89712.js
2178 ms
hm.gif
298 ms
dlsicon.png
859 ms
index.php
846 ms
21ks.net 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
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.
21ks.net 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
21ks.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 21ks.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 21ks.net 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.
21ks.net
Open Graph description is not detected on the main page of 21 Ks. 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: