10.9 sec in total
1.7 sec
7.2 sec
2 sec
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 9.2 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.4 s
16/100
10%
Value6.4 s
10/100
25%
Value10.0 s
9/100
10%
Value2,330 ms
5/100
30%
Value0.109
87/100
15%
Value13.1 s
12/100
10%
1676 ms
1310 ms
442 ms
121 ms
878 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.4 sec) belongs to the original domain Jszp.org.
Page size can be reduced by 124.9 kB (38%)
325.8 kB
200.9 kB
In fact, the total size of Jszp.org main page is 325.8 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. 60% of websites need less resources to load. HTML takes 111.1 kB which makes up the majority of the site volume.
Potential reduce by 89.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 89.9 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 18.5 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 18.5 kB or 25% 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
1676 ms
jquery.min.js
1310 ms
htmlspecialchars.js
442 ms
gt.js
121 ms
common.css
878 ms
swiper.min.css
659 ms
index.css
877 ms
common_ajax_dialog.css
861 ms
font-awesome.min.css
868 ms
jquery.nivo.slider.pack.js
880 ms
jquery.modal.dialog.js
669 ms
swiper.min.js
1028 ms
jquery.disappear.tooltip.js
679 ms
jquery.vticker-min.js
674 ms
vaptcha.js
679 ms
jquery.select.js
1025 ms
scroll.js
819 ms
myjs.js
820 ms
logo_home.png
1884 ms
6229755c177fa.gif
1907 ms
62e38afaa5328.gif
1900 ms
62dfaafbbcab4.gif
1882 ms
6099fe6ae0639.gif
1882 ms
5ddc6fdeb4d0d.gif
1883 ms
6022e5bd57305.gif
1898 ms
5ddc70e68c5bf.gif
1900 ms
60473ac012863.gif
1901 ms
5ddc725c8f04c.gif
1902 ms
5e7d783203069.gif
1903 ms
62e386abbf538.jpg
1889 ms
5f8836a991cfd.gif
1890 ms
5f7fe12ea97b0.gif
1891 ms
622f597e4175d.jpg
1891 ms
6229854439d4b.gif
1936 ms
620f51f5b7b74.gif
1949 ms
622ab862caca1.gif
1966 ms
618255d70db45.gif
1891 ms
624ede9fa0cc1.gif
1892 ms
5def72c200baf.gif
1893 ms
6061390b52a6f.gif
1894 ms
6153cdafaa5c0.gif
1896 ms
5f6db4b719edf.gif
1895 ms
5dee15aee427a.gif
1994 ms
5def6cd76f855.gif
2002 ms
5ff42f462b028.gif
2005 ms
5def71e64246e.gif
2149 ms
61c4400b00c35.gif
2169 ms
61711b85a14e6.gif
2184 ms
619f117c791ae.gif
2215 ms
601def56e6564.gif
2224 ms
614c5095d4fb7.gif
2225 ms
5f59a72a10eb0.gif
2363 ms
5fe1a18abfe34.gif
2385 ms
6059a7edd65b3.gif
2401 ms
109.png
367 ms
mb_code.gif
366 ms
qr_weixin.jpg
380 ms
index.php
381 ms
cho_bt.png
313 ms
zhaopin.jpg
313 ms
new_lik.png
373 ms
notice_bg.png
375 ms
240.png
414 ms
fot_link_bg.png
415 ms
140.png
440 ms
search_ico.png
221 ms
fontawesome-webfont.woff
1426 ms
get_header_min.html
263 ms
jszp.org
1387 ms
company_ajax_dialog.css
1120 ms
5e05d1a754b96.gif
577 ms
5ddc7b57909fd.gif
594 ms
5ddc7bb2814e0.gif
594 ms
5e09c23ce0571.gif
704 ms
61f4d544009c4.gif
730 ms
5ddc7cfa93a53.gif
750 ms
5eec6e03eb76e.gif
784 ms
5ffd4cd79944d.gif
798 ms
60b856c7c5da0.gif
796 ms
5ddca20ad1c8f.gif
913 ms
5ddca2a9c3245.gif
941 ms
5ddca2f42e7d8.gif
963 ms
5ddca32dd0605.gif
1001 ms
5ddca39e32b72.gif
1016 ms
5ddca3e6c8f12.gif
1016 ms
5ddca42435ab1.gif
1126 ms
5e0aa0868c7a0.gif
1157 ms
5ddca4c469b64.gif
1177 ms
5ddca54db4c12.gif
1221 ms
5ddca5d576baf.gif
1230 ms
5ddca6510437b.gif
1196 ms
5ddca68203645.gif
1298 ms
5ddca6e358b0b.gif
1319 ms
5ddca730ebd41.gif
1330 ms
5ddca782ef153.gif
1344 ms
5ddca7c9ca4e1.gif
1348 ms
5ddca831d8b03.gif
1351 ms
5ddca8b32e253.gif
1306 ms
62e3892e197e3.gif
1313 ms
5ddca95e3ae28.gif
1329 ms
5ddcd2f1d80f6.gif
1344 ms
5ddcda4ede342.gif
1346 ms
5ddcebf0735a9.gif
1349 ms
5ddcee3dcbbf2.gif
1303 ms
62e38a3adf046.gif
1311 ms
5ddcd3fbd6a3e.gif
1327 ms
61711883bc025.gif
1343 ms
5ddf4a40d905a.gif
1341 ms
5ddf51ecec785.gif
1369 ms
5ddf560c2ffec.gif
1305 ms
5ddf73abd730b.gif
1308 ms
5ddf7921043cc.gif
1300 ms
5ddf7c06d43c2.gif
1337 ms
5ddf7dbb80688.gif
1339 ms
5ddf80e587598.gif
1348 ms
5ddcd4a11cf61.gif
1306 ms
5ddcd53014a46.gif
1310 ms
620dc9c97e7ed.gif
1328 ms
5ddcd61c86b1d.gif
1339 ms
5ddcd6761e684.gif
1371 ms
5ddcd6c7e9b24.gif
1364 ms
5ddcd722594f4.gif
1319 ms
5ddcd7519be81.gif
1312 ms
620dca0dc6f98.gif
1327 ms
5ddcd81c3b2c4.gif
1339 ms
608a5f2b2e533.gif
1590 ms
5dfd7c1cd1bdb.jpg
1370 ms
61f0031f7e7ed.gif
1323 ms
622f62ffa8750.gif
1312 ms
6275d37e9bb66.gif
1332 ms
622f5ad38dc11.gif
1335 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: