9.1 sec in total
1.7 sec
7 sec
362 ms
Welcome to jszp.org homepage info - get ready to check Jszp best content right away, or after learning these important things about jszp.org
中国高校招聘网是中国权威的高校人才招聘门户网站、内容主要包括:教师招聘、研究生招聘、高校招聘、高校人才、博士招聘、特聘教授、高校教师招聘、高层次人才招聘、北京、广州、上海、河南、深圳等全国各地高校教师、管理人才及科研人才招聘信息网(官方站)
Visit jszp.orgWe analyzed Jszp.org page load time and found that the first response time was 1.7 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jszp.org performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.6 s
18/100
25%
Value10.2 s
8/100
10%
Value570 ms
52/100
30%
Value0.029
100/100
15%
Value11.1 s
20/100
10%
1720 ms
1297 ms
428 ms
111 ms
872 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 99% of them (130 requests) were addressed to the original Jszp.org, 1% (1 request) were made to Static.geetest.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Jszp.org.
Page size can be reduced by 134.7 kB (38%)
357.6 kB
222.9 kB
In fact, the total size of Jszp.org main page is 357.6 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. 55% of websites need less resources to load. Javascripts take 118.1 kB which makes up the majority of the site volume.
Potential reduce by 89.3 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 89.3 kB or 81% of the original size.
Potential reduce by 3.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. Jszp images are well optimized though.
Potential reduce by 28.9 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 28.9 kB or 24% of the original size.
Potential reduce by 13.5 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. Jszp.org needs all CSS files to be minified and compressed as it can save up to 13.5 kB or 27% of the original size.
Number of requests can be reduced by 16 (12%)
129
113
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jszp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
jszp.org
1720 ms
jquery.min.js
1297 ms
htmlspecialchars.js
428 ms
gt.js
111 ms
common.css
872 ms
swiper.min.css
656 ms
index.css
868 ms
common_ajax_dialog.css
861 ms
font-awesome.min.css
880 ms
jquery.nivo.slider.pack.js
874 ms
jquery.modal.dialog.js
645 ms
swiper.min.js
1115 ms
jquery.disappear.tooltip.js
655 ms
jquery.vticker-min.js
663 ms
vaptcha.js
670 ms
jquery.select.js
860 ms
scroll.js
683 ms
myjs.js
683 ms
logo_home.png
1830 ms
6600fa41c192b.gif
1840 ms
6600faa7346de.gif
1840 ms
6444bc2731781.gif
1829 ms
65dedf9690321.gif
1829 ms
5ddc6fdeb4d0d.gif
1830 ms
6597cbef4c62b.gif
1839 ms
5ddc70e68c5bf.gif
1841 ms
60473ac012863.gif
1841 ms
5ddc725c8f04c.gif
1842 ms
5e7d783203069.gif
1842 ms
62e386abbf538.jpg
1843 ms
5f8836a991cfd.gif
1843 ms
5f7fe12ea97b0.gif
1843 ms
622f597e4175d.jpg
1844 ms
65542ec13279e.gif
1848 ms
65e6e0bdb2584.gif
1919 ms
65b34068d9125.gif
1847 ms
618255d70db45.gif
1844 ms
6627358908367.gif
1844 ms
5def72c200baf.gif
1845 ms
6061390b52a6f.gif
1846 ms
6153cdafaa5c0.gif
1847 ms
65ee9a589f457.gif
1848 ms
5dee15aee427a.gif
1944 ms
5def6cd76f855.gif
1962 ms
5ff42f462b028.gif
2017 ms
5def71e64246e.gif
2018 ms
61c4400b00c35.gif
2016 ms
6444bdef79f2c.gif
2131 ms
6572c9794c89c.gif
2159 ms
601def56e6564.gif
2179 ms
614c5095d4fb7.gif
2239 ms
6487f9fc98215.gif
2241 ms
5fe1a18abfe34.gif
2243 ms
65043178b25c0.gif
2343 ms
109.png
223 ms
mb_code.gif
215 ms
qr_weixin.jpg
217 ms
index.php
287 ms
cho_bt.png
235 ms
zhaopin.jpg
399 ms
new_lik.png
402 ms
notice_bg.png
416 ms
240.png
417 ms
fot_link_bg.png
443 ms
140.png
475 ms
fontawesome-webfont.woff
1726 ms
search_ico.png
403 ms
get_header_min.html
471 ms
jszp.org
1572 ms
company_ajax_dialog.css
1096 ms
5e05d1a754b96.gif
550 ms
5ddc7b57909fd.gif
571 ms
5ddc7bb2814e0.gif
636 ms
5e09c23ce0571.gif
629 ms
65ab7ac531781.gif
633 ms
5ddc7cfa93a53.gif
721 ms
650423173c1a9.gif
754 ms
642a6c010f307.gif
778 ms
60b856c7c5da0.gif
846 ms
5ddca20ad1c8f.gif
849 ms
5ddca2a9c3245.gif
854 ms
5ddca2f42e7d8.gif
929 ms
5ddca32dd0605.gif
965 ms
5ddca39e32b72.gif
991 ms
5ddca3e6c8f12.gif
1066 ms
5ddca42435ab1.gif
1068 ms
5e0aa0868c7a0.gif
1074 ms
5ddca4c469b64.gif
1139 ms
5ddca54db4c12.gif
1177 ms
5ddca5d576baf.gif
1205 ms
5ddca6510437b.gif
1285 ms
5ddca68203645.gif
1287 ms
5ddca6e358b0b.gif
1285 ms
5ddca730ebd41.gif
1280 ms
5ddca782ef153.gif
1296 ms
5ddca7c9ca4e1.gif
1311 ms
5ddca831d8b03.gif
1339 ms
5ddca8b32e253.gif
1342 ms
649e86bd0704e.gif
1350 ms
5ddca95e3ae28.gif
1279 ms
5ddcd2f1d80f6.gif
1298 ms
5ddcda4ede342.gif
1311 ms
5ddcebf0735a9.gif
1340 ms
5ddcee3dcbbf2.gif
1341 ms
62e38a3adf046.gif
1349 ms
5ddcd3fbd6a3e.gif
1280 ms
65e03f8fe41e7.gif
1299 ms
5ddf4a40d905a.gif
1311 ms
5ddf51ecec785.gif
1340 ms
5ddf560c2ffec.gif
1342 ms
5ddf73abd730b.gif
1350 ms
5ddf7921043cc.gif
1280 ms
5ddf7c06d43c2.gif
1299 ms
5ddf7dbb80688.gif
1310 ms
5ddf80e587598.gif
1339 ms
5ddcd4a11cf61.gif
1341 ms
5ddcd53014a46.gif
1349 ms
65e03f7380efd.gif
1280 ms
5ddcd61c86b1d.gif
1300 ms
5ddcd6761e684.gif
1311 ms
5ddcd6c7e9b24.gif
1340 ms
5ddcd722594f4.gif
1341 ms
5ddcd7519be81.gif
1349 ms
65e6c44a97a45.gif
1279 ms
5ddcd81c3b2c4.gif
1299 ms
608a5f2b2e533.gif
1527 ms
5dfd7c1cd1bdb.jpg
1339 ms
6481504688df1.gif
1342 ms
648a93c5efde4.gif
1332 ms
64197bf2c3f41.gif
1295 ms
63e34e038732f.gif
1299 ms
jszp.org 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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
jszp.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
jszp.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jszp.org 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 Jszp.org 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.
jszp.org
Open Graph description is not detected on the main page of Jszp. 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: