Tools & Wizards About Us
quanji.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

quanji.com

www.quanji.com-官网首页

Page Load Speed

61.4 sec in total

First Response

7.9 sec

Resources Loaded

52.4 sec

Page Rendered

1.1 sec

quanji.com screenshot

About Website

Visit quanji.com now to see the best up-to-date Quanji content for China and also check out these interesting facts you probably never knew about quanji.com

lol电影天堂网-01-19年记录-历史百度权重8-外链超多

Visit quanji.com

Key Findings

We analyzed Quanji.com page load time and found that the first response time was 7.9 sec and then it took 53.5 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

quanji.com performance score

0

Network Requests Diagram

quanji.com

7857 ms

www.loldytt.com

5437 ms

loldytt.css

12051 ms

ds.js

764 ms

sy96090.js

12050 ms

Our browser made a total of 177 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Quanji.com, 25% (45 requests) were made to Img.cnsofas.com and 6% (10 requests) were made to Img01.taobaocdn.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Bdimg.share.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 265.7 kB (23%)

Content Size

1.1 MB

After Optimization

867.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Quanji.com main page is 1.1 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. 45% of websites need less resources to load. Images take 836.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 64.2 kB

  • Original 78.4 kB
  • After minification 78.4 kB
  • After compression 14.2 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 64.2 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 60.9 kB

  • Original 836.1 kB
  • After minification 775.2 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. Quanji images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 127.4 kB

  • Original 202.7 kB
  • After minification 200.0 kB
  • After compression 75.2 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 127.4 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 13.1 kB

  • Original 16.0 kB
  • After minification 15.2 kB
  • After compression 2.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. Quanji.com needs all CSS files to be minified and compressed as it can save up to 13.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 86 (53%)

Requests Now

161

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 161 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Quanji. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

quanji.com

quanji.com

7857 ms

www.loldytt.com

www.loldytt.com

5437 ms

loldytt.css

loldytt.css

12051 ms

ds.js

ds.js

764 ms

sy96090.js

sy96090.js

12050 ms

sy3001.js

sy3001.js

12139 ms

sy3002.js

sy3002.js

12140 ms

sy3003.js

sy3003.js

12140 ms

sy3004.js

sy3004.js

12139 ms

sy3005.js

sy3005.js

12142 ms

sy3006.js

sy3006.js

12141 ms

sy3007.js

sy3007.js

12142 ms

sy3008.js

sy3008.js

12145 ms

sy3009.js

sy3009.js

12142 ms

sy30010.js

sy30010.js

12145 ms

sy30011.js

sy30011.js

12147 ms

sy30012.js

sy30012.js

12147 ms

sy.js

sy.js

12148 ms

push.js

push.js

1683 ms

hm.js

hm.js

2321 ms

qdb.jpg

qdb.jpg

64 ms

loldytt.gif

loldytt.gif

66 ms

ss.png

ss.png

63 ms

dytl.jpg

dytl.jpg

81 ms

20164819252057798.jpg

20164819252057798.jpg

81 ms

201512311812543277.jpg

201512311812543277.jpg

142 ms

201632023435872299.jpg

201632023435872299.jpg

137 ms

201611117402653251.jpg

201611117402653251.jpg

141 ms

20164723165278102.jpg

20164723165278102.jpg

138 ms

2016469552080389.jpg

2016469552080389.jpg

139 ms

20158615354261940.jpg

20158615354261940.jpg

139 ms

201632120502353336.jpg

201632120502353336.jpg

140 ms

201510919224679635.jpg

201510919224679635.jpg

141 ms

201511161561938388.jpg

201511161561938388.jpg

145 ms

201631120382862926.jpg

201631120382862926.jpg

143 ms

20164121134911620.jpg

20164121134911620.jpg

147 ms

20153241991650294.jpg

20153241991650294.jpg

170 ms

20159519255089190.jpg

20159519255089190.jpg

174 ms

share.js

share.js

1025 ms

ex

ex

1140 ms

sh_2.jpg

sh_2.jpg

105 ms

bg05.gif

bg05.gif

118 ms

soso.gif

soso.gif

119 ms

i_v5.png

i_v5.png

119 ms

tcim

tcim

853 ms

14733_2623.html

14733_2623.html

2861 ms

tcim

tcim

400 ms

tanxssp.js

tanxssp.js

890 ms

14733_2754.html

14733_2754.html

2475 ms

tcim

tcim

381 ms

14733_4068.html

14733_4068.html

2099 ms

ex

ex

9776 ms

ex

ex

760 ms

ex

ex

9845 ms

tcim

tcim

410 ms

ex

ex

1515 ms

lol3001.html

lol3001.html

43 ms

tcim

tcim

1380 ms

hm.gif

hm.gif

462 ms

301043.js

301043.js

1797 ms

viid.php

viid.php

1918 ms

ex

ex

1769 ms

lol3002.html

lol3002.html

45 ms

tcim

tcim

471 ms

acbeacon2.html

acbeacon2.html

377 ms

TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png

TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png

147 ms

TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png

TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png

150 ms

TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png

TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png

148 ms

TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png

TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png

154 ms

301044.js

301044.js

3574 ms

TB1FYxFIFXXXXcRXXXXO04pFXXX.html

TB1FYxFIFXXXXcRXXXXO04pFXXX.html

405 ms

300X250.jpg

300X250.jpg

335 ms

refer

refer

2284 ms

dot.gif

dot.gif

256 ms

getPosData0

getPosData0

1664 ms

t.gif

t.gif

4081 ms

bl

bl

1087 ms

lol3003.html

lol3003.html

28 ms

tcim

tcim

490 ms

301045.js

301045.js

3447 ms

fmt3.php

fmt3.php

3361 ms

spf

spf

3860 ms

tanx_ui.js

tanx_ui.js

32 ms

test-u.min.js

test-u.min.js

4050 ms

t.gif

t.gif

874 ms

y.gif

y.gif

6500 ms

lol3004.html

lol3004.html

36 ms

ex

ex

984 ms

tcim

tcim

505 ms

301046.js

301046.js

513 ms

7lol3005.html

7lol3005.html

71 ms

repeat.gif

repeat.gif

65 ms

ico_01.gif

ico_01.gif

66 ms

Bg1.png

Bg1.png

64 ms

tcim

tcim

474 ms

tcim

tcim

989 ms

fmt3.php

fmt3.php

2520 ms

T2c37PXcFXXXXXXXXX_!!0-2-newland.png

T2c37PXcFXXXXXXXXX_!!0-2-newland.png

386 ms

TB1FVfCFVXXXXXKXFXXFK449VXX-100-90.gif

TB1FVfCFVXXXXXKXFXXFK449VXX-100-90.gif

1062 ms

tanxclick.js

tanxclick.js

51 ms

T2zZ3NXjBaXXXXXXXX_!!0-2-newland.png

T2zZ3NXjBaXXXXXXXX_!!0-2-newland.png

1099 ms

T28yAPXktXXXXXXXXX_!!0-2-newland.png

T28yAPXktXXXXXXXXX_!!0-2-newland.png

1096 ms

m

m

4250 ms

dot.gif

dot.gif

91 ms

ex

ex

2136 ms

mr_14539_6828.js

mr_14539_6828.js

1255 ms

i20150908.php

i20150908.php

311 ms

32f9626829457a65.php

32f9626829457a65.php

1348 ms

view_p20150908.php

view_p20150908.php

716 ms

rich_20160407.js

rich_20160407.js

134 ms

share_api.js

share_api.js

343 ms

share_view.js

share_view.js

678 ms

getPosData0

getPosData0

1033 ms

fmt3.php

fmt3.php

909 ms

tangram.js

tangram.js

19739 ms

api_base.js

api_base.js

2889 ms

dot.gif

dot.gif

748 ms

0726f4b45b394194.php

0726f4b45b394194.php

791 ms

flash.js

flash.js

937 ms

fmt3.php

fmt3.php

1091 ms

view_base.js

view_base.js

1179 ms

TB1.mtxIFXXXXXnXFXXO04pFXXX.html

TB1.mtxIFXXXXXnXFXXO04pFXXX.html

78 ms

bl

bl

1982 ms

app.gif

app.gif

1091 ms

cm.gif

cm.gif

866 ms

blank2.gif

blank2.gif

1629 ms

jk.php

jk.php

506 ms

T20pBVXdhdXXXXXXXX_!!0-0-newland.jpg

T20pBVXdhdXXXXXXXX_!!0-0-newland.jpg

261 ms

T2B5cOXhlXXXXXXXXX_!!0-2-newland.png

T2B5cOXhlXXXXXXXXX_!!0-2-newland.png

258 ms

T2t_yFXaVcXXXXXXXX_!!0-1-newland.gif

T2t_yFXaVcXXXXXXXX_!!0-1-newland.gif

249 ms

dot.gif

dot.gif

107 ms

close2.gif

close2.gif

112 ms

um.js

um.js

478 ms

img

img

1071 ms

um.json

um.json

1835 ms

getDeviceInfo

getDeviceInfo

2039 ms

T2KatmXlJNXXXXXXXX_!!0-0-newland.jpg

T2KatmXlJNXXXXXXXX_!!0-0-newland.jpg

455 ms

TB1khblFVXXXXbPXXXXPNezMFXX-319-34.gif

TB1khblFVXXXXbPXXXXPNezMFXX-319-34.gif

292 ms

logger.js

logger.js

782 ms

pixel

pixel

21 ms

pixel

pixel

21 ms

Mapping.do

Mapping.do

295 ms

t.gif

t.gif

926 ms

ex

ex

849 ms

ex

ex

2363 ms

getDeviceInfo

getDeviceInfo

687 ms

cm.gif

cm.gif

285 ms

spf

spf

1719 ms

imp

imp

1575 ms

media.html

media.html

3140 ms

t.gif

t.gif

790 ms

T2zHtbXkVOXXXXXXXX_!!0-1-newland.gif

T2zHtbXkVOXXXXXXXX_!!0-1-newland.gif

27 ms

T266IOXXhaXXXXXXXX_!!0-2-newland.png

T266IOXXhaXXXXXXXX_!!0-2-newland.png

148 ms

T28qB0XddeXXXXXXXX_!!0-2-newland.png

T28qB0XddeXXXXXXXX_!!0-2-newland.png

192 ms

T2os4CXjlOXXXXXXXX_!!0-2-newland.png

T2os4CXjlOXXXXXXXX_!!0-2-newland.png

31 ms

cm.gif

cm.gif

302 ms

cm.gif

cm.gif

3060 ms

spf

spf

3991 ms

imp

imp

1900 ms

media.html

media.html

1186 ms

t.gif

t.gif

1719 ms

a_1.png

a_1.png

378 ms

T2KcAnXfRbXXXXXXXX_!!0-2-newland.png

T2KcAnXfRbXXXXXXXX_!!0-2-newland.png

94 ms

m

m

478 ms

T2Y99dXl4bXXXXXXXX_!!0-1-newland.gif

T2Y99dXl4bXXXXXXXX_!!0-1-newland.gif

54 ms

T2y.SkXldbXXXXXXXX_!!0-1-newland.gif

T2y.SkXldbXXXXXXXX_!!0-1-newland.gif

43 ms

T2EP5UXatbXXXXXXXX_!!0-1-newland.gif

T2EP5UXatbXXXXXXXX_!!0-1-newland.gif

47 ms

T27j8bXldOXXXXXXXX_!!0-2-newland.png

T27j8bXldOXXXXXXXX_!!0-2-newland.png

44 ms

T2APe5XipXXXXXXXXX_!!0-0-newland.jpg

T2APe5XipXXXXXXXXX_!!0-0-newland.jpg

71 ms

T2SCgOXldXXXXXXXXX_!!0-2-newland.png

T2SCgOXldXXXXXXXXX_!!0-2-newland.png

122 ms

T2siH3Xb4bXXXXXXXX_!!0-2-newland.png

T2siH3Xb4bXXXXXXXX_!!0-2-newland.png

326 ms

T2tBWXXeVcXXXXXXXX_!!0-1-newland.gif

T2tBWXXeVcXXXXXXXX_!!0-1-newland.gif

199 ms

T2uWaUXXlbXXXXXXXX_!!0-1-newland.gif

T2uWaUXXlbXXXXXXXX_!!0-1-newland.gif

40 ms

T24c7OXcJaXXXXXXXX_!!0-2-newland.png

T24c7OXcJaXXXXXXXX_!!0-2-newland.png

32 ms

T2Q1QPXe4XXXXXXXXX_!!0-2-newland.png

T2Q1QPXe4XXXXXXXXX_!!0-2-newland.png

29 ms

T2pIAOXkJXXXXXXXXX_!!0-2-newland.png

T2pIAOXkJXXXXXXXXX_!!0-2-newland.png

150 ms

T2VkTqXmXaXXXXXXXX_!!0-1-newland.gif

T2VkTqXmXaXXXXXXXX_!!0-1-newland.gif

25 ms

SEO Factors

quanji.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Quanji.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Quanji.com main page’s claimed encoding is gb2312. 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.

Social Sharing Optimization

quanji.com

Open Graph description is not detected on the main page of Quanji. 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: