47.9 sec in total
4.2 sec
43.4 sec
232 ms
Click here to check amazing Kongjie content for China. Otherwise, check out these important facts you probably never knew about kongjie.com
空姐招聘 空姐培训 空乘培训 航校招生 民航网 公众号空姐网民航网民航
Visit kongjie.comWe analyzed Kongjie.com page load time and found that the first response time was 4.2 sec and then it took 43.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
kongjie.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value10.0 s
0/100
25%
Value12.7 s
3/100
10%
Value5,480 ms
0/100
30%
Value0
100/100
15%
Value13.0 s
13/100
10%
4218 ms
4510 ms
4552 ms
1264 ms
991 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 54% of them (93 requests) were addressed to the original Kongjie.com, 10% (17 requests) were made to Jy.kongjie.com and 10% (17 requests) were made to 51love.cc. The less responsive or slowest element that took the longest time to load (19.6 sec) belongs to the original domain Kongjie.com.
Page size can be reduced by 322.3 kB (39%)
820.1 kB
497.9 kB
In fact, the total size of Kongjie.com main page is 820.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. 55% of websites need less resources to load. Images take 396.0 kB which makes up the majority of the site volume.
Potential reduce by 5.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. 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 5.0 kB or 66% of the original size.
Potential reduce by 49.5 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, Kongjie needs image optimization as it can save up to 49.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 195.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 195.4 kB or 60% of the original size.
Potential reduce by 72.4 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. Kongjie.com needs all CSS files to be minified and compressed as it can save up to 72.4 kB or 82% of the original size.
Number of requests can be reduced by 30 (20%)
150
120
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kongjie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
www.kongjie.com
4218 ms
style_14_common.css
4510 ms
common.js
4552 ms
portal.js
1264 ms
logging.js
991 ms
md5.js
3783 ms
c.js
1707 ms
adsbygoogle.js
38 ms
c.js
769 ms
index.php
1307 ms
index.php
1310 ms
kj.js
1997 ms
l.js
1731 ms
discuz_tips.js
635 ms
index.php
1556 ms
index.php
1794 ms
logo.png
831 ms
qq_login.gif
1405 ms
sina_login_btn.png
5617 ms
141451zvimclppnf8phhii.jpg
16739 ms
19cd891372f165add8197ca12fee6b14.jpg
10524 ms
99b187bc8cc07b6dabeebe9892d8d2ea.jpg
2756 ms
fdc412252b2e9a591abd2290414ac387.jpg
6024 ms
bed65cfd360ff0343b0bec0e2ee4fc67.jpg
3901 ms
5f220c3af56f1299113c1ba7d0b9d990.jpg
8948 ms
19_avatar_small.jpg
4822 ms
25_avatar_small.jpg
5717 ms
17_avatar_small.jpg
6519 ms
38_avatar_small.jpg
7127 ms
04_avatar_small.jpg
6721 ms
88_avatar_small.jpg
7638 ms
06_avatar_small.jpg
12716 ms
07_avatar_small.jpg
9886 ms
86_avatar_small.jpg
8533 ms
75_avatar_small.jpg
10800 ms
01_avatar_small.jpg
10862 ms
23_avatar_small.jpg
15730 ms
38_avatar_small.jpg
11308 ms
27_avatar_small.jpg
11811 ms
16_avatar_small.jpg
13771 ms
68_avatar_small.jpg
12747 ms
18_avatar_small.jpg
12835 ms
38_avatar_small.jpg
13649 ms
05_avatar_small.jpg
13685 ms
09_avatar_small.jpg
14373 ms
29_avatar_small.jpg
14378 ms
88_avatar_small.jpg
16093 ms
10_avatar_small.jpg
14790 ms
09_avatar_small.jpg
15342 ms
89_avatar_small.jpg
15329 ms
95_avatar_small.jpg
15778 ms
00_avatar_small.jpg
16080 ms
ask
893 ms
23_avatar_small.jpg
15443 ms
ct
7522 ms
lm.jpg
708 ms
ca-pub-9711080227594786.js
210 ms
zrt_lookup.html
208 ms
show_ads_impl.js
122 ms
zcvm
902 ms
avatar_big.jpg.thumb.jpg
1159 ms
ads
126 ms
avatar_big.jpeg.thumb.jpg
1085 ms
avatar_big.jpeg.thumb.jpg
1118 ms
avatar_big.jpeg.thumb.jpg
1111 ms
avatar_big.jpg.thumb.jpg
1146 ms
avatar_big.jpeg.thumb.jpg
1154 ms
osd.js
16 ms
avatar_big.jpg.thumb.jpg
2269 ms
avatar_big.jpg.thumb.jpg
2271 ms
avatar_big.jpg.thumb.jpg
2273 ms
avatar_big.jpg.thumb.jpg
2276 ms
avatar_big.jpg.thumb.jpg
6446 ms
avatar_big.jpg.thumb.jpg
4479 ms
avatar_big.jpg.thumb.jpg
3193 ms
avatar_big.jpg.thumb.jpg
3210 ms
avatar_big.jpg.thumb.jpg
4757 ms
zcvm
1572 ms
ads
182 ms
ask
2206 ms
m_js_controller.js
43 ms
abg.js
65 ms
favicon
112 ms
googlelogo_color_112x36dp.png
99 ms
mobile_unified_button_icon_white.png
64 ms
s
57 ms
x_button_blue2.png
45 ms
favicon
82 ms
common_extra.js
19630 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
23 ms
zcvm
1062 ms
avatar_big.jpg.thumb.jpg
4027 ms
avatar_big.jpeg.thumb.jpg
14389 ms
avatar_big.jpeg.thumb.jpg
2569 ms
avatar_big.jpeg.thumb.jpg
3524 ms
avatar_big.jpg.thumb.jpg
4401 ms
avatar_big.jpeg.thumb.jpg
12791 ms
activeview
17 ms
activeview
24 ms
93_avatar_small.jpg
14041 ms
zcvm
1877 ms
adx.php
894 ms
reduce_bd-logo1_oper.png
694 ms
avatar_big.jpg.thumb.jpg
2751 ms
avatar_big.jpg.thumb.jpg
3729 ms
avatar_big.jpg.thumb.jpg
4097 ms
avatar_big.jpg.thumb.jpg
4186 ms
ct
6704 ms
closefeedback.min.js
534 ms
82_avatar_small.jpg
13162 ms
avatar_big.jpg.thumb.jpg
3701 ms
avatar_big.jpg.thumb.jpg
4151 ms
reduce_promotion_oper.png
489 ms
bd_logo.png
506 ms
bg_rb.png
540 ms
adx.php
431 ms
97_avatar_small.jpg
12365 ms
91_avatar_small.jpg
12062 ms
avatar_big.jpg.thumb.jpg
4631 ms
65_avatar_small.jpg
11982 ms
avatar_big.jpg.thumb.jpg
4910 ms
85_avatar_small.jpg
11728 ms
88_avatar_small.jpg
11486 ms
27_avatar_small.jpg
13285 ms
64_avatar_small.jpg
11355 ms
avatar_big.jpg.thumb.jpg
2287 ms
26_avatar_small.jpg
11013 ms
fc.js
1844 ms
sogou_icon_wz_1.png
815 ms
38_avatar_small.jpg
10415 ms
03_avatar_small.jpg
11988 ms
81_avatar_small.jpg
10088 ms
35_avatar_small.jpg
9466 ms
15_avatar_small.jpg
9501 ms
19_avatar_small.jpg
9888 ms
60_avatar_small.jpg
11387 ms
60_avatar_small.jpg
10469 ms
fc1efb8c6d70336babee6be94ecb710e.jpg
8516 ms
8fa3b59402eb0535f312046638ce641b.jpg
8951 ms
7b4362c02a620be48b8e72281269547e.jpg
9599 ms
bfad7d26f35ec94dbe6cd69b620b6ddc.jpg
10615 ms
199b349b47fdbfaf547180fcbf5ab20e.jpg
9594 ms
13877aafed49c83f36cddff1fd6bfdff.jpg
9421 ms
740770975ba74ad0435206287c866642.jpg
9281 ms
5da6b9e7f0480f029e4cc579653170e6.jpg
11089 ms
f2a5e221612ae2a06c69c68aad86e954.jpg
11784 ms
62663.jpg
9881 ms
62655.jpg
9784 ms
62662.jpg
9495 ms
62661.jpg
14556 ms
62659.jpg
11794 ms
62657.jpg
12305 ms
62656.jpg
10317 ms
62654.jpg
10515 ms
62633.jpg
11144 ms
security.png
12335 ms
px.png
10963 ms
pn.png
10955 ms
nv.png
11104 ms
qmenu.png
11669 ms
nv_a.png
11510 ms
mu_bg.png
11591 ms
search.png
11451 ms
bg.png
11800 ms
list1.gif
10341 ms
p.gif
10437 ms
scrolltop.png
10975 ms
o.htm
910 ms
ui
57 ms
wh.js
737 ms
ac.js
488 ms
kongjie.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
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
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.
kongjie.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
kongjie.com 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kongjie.com 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 Kongjie.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.
kongjie.com
Open Graph description is not detected on the main page of Kongjie. 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: