54.4 sec in total
6 sec
48 sec
418 ms
Click here to check amazing Qinglanji content for China. Otherwise, check out these important facts you probably never knew about qinglanji.com
新片场是下一代传媒公司,最大的新媒体内容出品和发行平台.聚拢众多优秀创作人,出品发行影视作品.在这里,你可以找到最优秀的创作人;在这里,你可以用作品打动世界;创作吧!少年
Visit qinglanji.comWe analyzed Qinglanji.com page load time and found that the first response time was 6 sec and then it took 48.4 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. Unfortunately, there were 17 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
qinglanji.com performance score
5974 ms
9142 ms
4905 ms
926 ms
26 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Qinglanji.com, 36% (39 requests) were made to Xinpianchang.com and 35% (38 requests) were made to Cs.xinpianchang.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Xinpianchang.com.
Page size can be reduced by 573.0 kB (18%)
3.2 MB
2.7 MB
In fact, the total size of Qinglanji.com main page is 3.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. 40% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 176.4 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 176.4 kB or 90% of the original size.
Potential reduce by 155.6 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. Qinglanji images are well optimized though.
Potential reduce by 129.1 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 129.1 kB or 49% of the original size.
Potential reduce by 111.9 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. Qinglanji.com needs all CSS files to be minified and compressed as it can save up to 111.9 kB or 79% of the original size.
Number of requests can be reduced by 43 (48%)
90
47
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qinglanji. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
qinglanji.com
5974 ms
www.xinpianchang.com
9142 ms
common.css
4905 ms
rl_login_p.css
926 ms
wb.js
26 ms
jquery-1.7.1.min.js
14115 ms
style.css
7656 ms
style.css
2911 ms
jquery-1.7.1.min.js
18341 ms
jquery.cookie.js
463 ms
qrcode.js
3073 ms
jquery.qrcode.min.js
3214 ms
common.js
8073 ms
simple.css
3934 ms
artDialog.min.js
5246 ms
artDialog.plugins.min.js
5181 ms
jquery.goToTop.js
6424 ms
rl_login.js
5826 ms
54f7cc35f3121.jpg
813 ms
54efd9f3f29d1.jpg
725 ms
54eaa3c80f082.jpg
734 ms
54dee73b9af4e.jpg
698 ms
54dd62a3e8023.jpg
731 ms
57078475bb0ee.jpg@1160w_760h_1e_1c.jpg
19666 ms
57071223379d7.jpg@560w_360h_1e_1c.jpg
19668 ms
570712a9c24cd.jpg@560w_360h_1e_1c.jpg
848 ms
570712f401c91.jpg@560w_360h_1e_1c.jpg
19668 ms
570713831fed9.jpg@560w_360h_1e_1c.jpg
9763 ms
5705bea12f800.jpg@560w_360h_1e_1c.jpg
19669 ms
5705bfbf92928.jpg@560w_360h_1e_1c.jpg
947 ms
5707ca7bebc9e_180.jpeg
5775 ms
56c556900f9bc_180.jpeg
5807 ms
56fb609c0ae77_180.jpeg
5855 ms
2856f9112967eab_180.jpeg
5887 ms
56f81e455180b_180.jpeg
5918 ms
56ed2034e5785_180.jpeg
5974 ms
570365e2d591a.jpg@500w_300h_1e_1c.jpg
6007 ms
55ee7fa080970.jpeg@500w_300h_1e_1c.jpg
6067 ms
5703307abf373.jpg@500w_300h_1e_1c.jpg
11747 ms
57036727bb9e9.jpg@500w_300h_1e_1c.jpg
17007 ms
5703649809b75.jpg@500w_300h_1e_1c.jpg
19666 ms
562c969cc789e.jpeg@500w_300h_1e_1c.jpg
19667 ms
56ef75a90ab74.jpeg@500w_300h_1e_1c.jpg
19668 ms
570362a7c74a6.jpg@500w_300h_1e_1c.jpg
19669 ms
5428c18da2f22.jpeg@500w_300h_1e_1c.jpg
19670 ms
56daaa402c705.jpeg@500w_300h_1e_1c.jpg
19671 ms
56d03e62dbdd0.jpeg@500w_300h_1e_1c.jpg
19671 ms
57036be08ab2d.jpg@500w_300h_1e_1c.jpg
19671 ms
57076b38d355a.jpg
19672 ms
56f8ec7e087d6.jpg
19673 ms
56f4d0769b7e6.jpg
19674 ms
logo.png
6577 ms
common-icon.png
19674 ms
header_pub.png
5527 ms
login_layer_bg.png
5337 ms
xpc_weixin.jpg
12089 ms
user-card-bg.jpg
15045 ms
art-icon.png
7157 ms
new-funding.png
11399 ms
funding-beta-v2.png
9750 ms
new-movie.png
11338 ms
new-pgc-lm-1.png
12478 ms
login.html
3499 ms
exp-cover-hover.png
3334 ms
common-icon-v3.png
20438 ms
icon-work.png
4978 ms
service-icon.png
8215 ms
top-suggestion.jpg
7761 ms
rl_login.css
4282 ms
jquery.cookie.js
5059 ms
getUnreadNum
4138 ms
hm.js
480 ms
share.js
700 ms
shell_v2.js
509 ms
loading1.gif
133 ms
bundle.js
133 ms
ts-square
3736 ms
logo_share.png
4468 ms
top-suggestion.jpg
5913 ms
client.js
19 ms
iframeWidget.js
4 ms
aj_relationship.php
895 ms
aj_relationship.php
868 ms
hm.gif
222 ms
logger.js
254 ms
bds_s_v2.js
715 ms
share_api.js
249 ms
share_view.js
292 ms
tangram.js
991 ms
api_base.js
230 ms
view_base.js
452 ms
followbutton.php
5153 ms
login_sf.png
8827 ms
bdsstyle.css
285 ms
share_style1_24.css
241 ms
logger.js
272 ms
54c7208c7fbff_80.jpeg
1201 ms
615946_80.jpeg
669 ms
56a09b049f805_80.jpeg
1643 ms
54b949c2702cc_80.jpeg
672 ms
55e5934bb79f3_80.jpeg
1419 ms
54ba9c12a5ebc_80.jpeg
670 ms
followButton.css
30 ms
bg_flbtn.png
3 ms
sso.js
51 ms
followButton.js
16 ms
suda.js
49 ms
b.gif
863 ms
b.gif
3862 ms
qinglanji.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qinglanji.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 Qinglanji.com 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.
qinglanji.com
Open Graph description is not detected on the main page of Qinglanji. 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: