Tools & Wizards About Us
123qwe1qaz.7958.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

123qwe1qaz.7958.com

LNMP一键安装包 by Licess

Page Load Speed

76.4 sec in total

First Response

1.8 sec

Resources Loaded

74.4 sec

Page Rendered

137 ms

123qwe1qaz.7958.com screenshot

About Website

Click here to check amazing 123 Qwe 1 Qaz 7958 content for China. Otherwise, check out these important facts you probably never knew about 123qwe1qaz.7958.com

您已成功安装LNMP一键安装包！

Visit 123qwe1qaz.7958.com

Key Findings

We analyzed 123qwe1qaz.7958.com page load time and found that the first response time was 1.8 sec and then it took 74.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.

Performance Metrics

123qwe1qaz.7958.com performance score

0

Network Requests Diagram

123qwe1qaz.7958.com.cn

1820 ms

personage.css

5966 ms

jquery-1.3.2.min.js

3387 ms

index.js

2425 ms

jquery.cookie.js

1181 ms

Our browser made a total of 149 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 123qwe1qaz.7958.com, 4% (6 requests) were made to Imgcdn.ahzlep.com and 4% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source V.behe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 634.4 kB (59%)

Content Size

1.1 MB

After Optimization

437.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 123qwe1qaz.7958.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. Javascripts take 855.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 41.7 kB

  • Original 57.2 kB
  • After minification 54.1 kB
  • After compression 15.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 41.7 kB or 73% of the original size.

Image Optimization

-19%

Potential reduce by 25.1 kB

  • Original 130.4 kB
  • After minification 105.3 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, 123 Qwe 1 Qaz 7958 needs image optimization as it can save up to 25.1 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 543.7 kB

  • Original 855.0 kB
  • After minification 718.1 kB
  • After compression 311.3 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 543.7 kB or 64% of the original size.

CSS Optimization

-80%

Potential reduce by 23.8 kB

  • Original 29.7 kB
  • After minification 26.1 kB
  • After compression 5.8 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. 123qwe1qaz.7958.com needs all CSS files to be minified and compressed as it can save up to 23.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 77 (57%)

Requests Now

136

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

123qwe1qaz.7958.com.cn

123qwe1qaz.7958.com.cn

1820 ms

personage.css

personage.css

5966 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

3387 ms

index.js

index.js

2425 ms

jquery.cookie.js

jquery.cookie.js

1181 ms

wpa.php

wpa.php

1044 ms

o.js

o.js

1733 ms

stat.php

stat.php

4155 ms

stat.php

stat.php

3575 ms

c.php

c.php

2458 ms

cpv.js

cpv.js

940 ms

jq.js

jq.js

1635 ms

7ef3509df59177fcc7d85d3c2c062b98

7ef3509df59177fcc7d85d3c2c062b98

1168 ms

qjwm.gif

qjwm.gif

3813 ms

ss_mr.png

ss_mr.png

3549 ms

qie.jpg

qie.jpg

450 ms

yhdl.png

yhdl.png

1773 ms

gbb.png

gbb.png

2074 ms

aqzx1.png

aqzx1.png

803 ms

aqzx2.png

aqzx2.png

2091 ms

aqzx3.png

aqzx3.png

1157 ms

aqzx4.png

aqzx4.png

2751 ms

toux.jpg

toux.jpg

2639 ms

touxq.jpg

touxq.jpg

2504 ms

gzwm.jpg

gzwm.jpg

2832 ms

fenxiang_1.gif

fenxiang_1.gif

2934 ms

jubao.gif

jubao.gif

11642 ms

qrcode.jpg

qrcode.jpg

6964 ms

dqxz.png

dqxz.png

3204 ms

sjkhd.jpg

sjkhd.jpg

4826 ms

xlwb.jpg

xlwb.jpg

3574 ms

txwb.gif

txwb.gif

3900 ms

zgzs.png

zgzs.png

9315 ms

zgzs1.png

zgzs1.png

4726 ms

zgzs2.gif

zgzs2.gif

4604 ms

zgzs3.png

zgzs3.png

7465 ms

topdb.gif

topdb.gif

5186 ms

views.js

views.js

1179 ms

taskMgr.js

taskMgr.js

1244 ms

ecom

ecom

3630 ms

contains.js

contains.js

70 ms

r.cgi

r.cgi

717 ms

conv.php

conv.php

600 ms

ta.php

ta.php

626 ms

31345.js

31345.js

2390 ms

facade_mainPush.gif

facade_mainPush.gif

2412 ms

ecom

ecom

1629 ms

ex

ex

1307 ms

ecom

ecom

318 ms

ex

ex

980 ms

ex

ex

982 ms

books.php

books.php

6921 ms

tanxssp.js

tanxssp.js

573 ms

main.js

main.js

50 ms

ex

ex

6368 ms

ex

ex

6024 ms

ex

ex

4708 ms

acbeacon2.html

acbeacon2.html

1097 ms

spf

spf

1363 ms

TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png

TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png

137 ms

TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png

TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png

154 ms

0.js

0.js

1908 ms

tc.js

tc.js

2258 ms

t.gif

t.gif

3955 ms

v.php

v.php

1370 ms

v.js

v.js

5023 ms

stat.htm

stat.htm

167 ms

core.php

core.php

1602 ms

t.gif

t.gif

4009 ms

b-1b.png

b-1b.png

1343 ms

spf

spf

9965 ms

spf

spf

3661 ms

t.gif

t.gif

1955 ms

524ff330f2edb6f701c429ba5cccdae9.jpg

524ff330f2edb6f701c429ba5cccdae9.jpg

5206 ms

300-250yyr.html

300-250yyr.html

2300 ms

stat.php

stat.php

546 ms

0.html

0.html

1133 ms

behe_logo_v.png

behe_logo_v.png

19729 ms

9.gif

9.gif

9730 ms

stat.htm

stat.htm

161 ms

core.php

core.php

1289 ms

stat.htm

stat.htm

167 ms

core.php

core.php

541 ms

9.gif

9.gif

974 ms

jquery-1.9.1.js

jquery-1.9.1.js

19597 ms

9.gif

9.gif

801 ms

c.php

c.php

2399 ms

m

m

7129 ms

cm.gif

cm.gif

753 ms

app.gif

app.gif

736 ms

adsbygoogle.js

adsbygoogle.js

6 ms

ca-pub-3026087928670293.js

ca-pub-3026087928670293.js

42 ms

zrt_lookup.html

zrt_lookup.html

42 ms

show_ads_impl.js

show_ads_impl.js

58 ms

app.gif

app.gif

782 ms

ads

ads

174 ms

osd.js

osd.js

6 ms

css

css

65 ms

m_js_controller.js

m_js_controller.js

31 ms

abg.js

abg.js

38 ms

nessie_icon_magazine_black.png

nessie_icon_magazine_black.png

41 ms

s

s

27 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

33 ms

nessie_icon_magazine_white.png

nessie_icon_magazine_white.png

11 ms

x_button_blue2.png

x_button_blue2.png

7 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

12 ms

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

44 ms

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

48 ms

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

50 ms

t.gif

t.gif

948 ms

activeview

activeview

14 ms

app.gif

app.gif

953 ms

chain

chain

2701 ms

um.js

um.js

1078 ms

img

img

1294 ms

stat.htm

stat.htm

242 ms

core.php

core.php

271 ms

stat.htm

stat.htm

166 ms

core.php

core.php

430 ms

i.php

i.php

2443 ms

10493 ms

um.json

um.json

2798 ms

getDeviceInfo

getDeviceInfo

2251 ms

lr_s.js

lr_s.js

1463 ms

ha0000.php

ha0000.php

1634 ms

save_log.php

save_log.php

1568 ms

i2.php

i2.php

4707 ms

getDeviceInfo

getDeviceInfo

1912 ms

iiadclosepf.png

iiadclosepf.png

5423 ms

iiadlogo.png

iiadlogo.png

4627 ms

akk.gif

akk.gif

14274 ms

app.gif

app.gif

3357 ms

ha0000.php

ha0000.php

1248 ms

save_log.php

save_log.php

339 ms

rich_media_show_bottom_bg.gif

rich_media_show_bottom_bg.gif

1283 ms

iiadlogodl.png

iiadlogodl.png

1446 ms

couplet_close.jpg

couplet_close.jpg

1367 ms

show.php

show.php

4001 ms

cpf.js

cpf.js

3463 ms

pf_ico.gif

pf_ico.gif

346 ms

b-1.png

b-1.png

1484 ms

close.gif

close.gif

1510 ms

358 ms

o.htm

o.htm

860 ms

ui

ui

36 ms

wh.js

wh.js

848 ms

ac.js

ac.js

641 ms

fp.htm

fp.htm

1328 ms

fp.htm

fp.htm

773 ms

SEO Factors

123qwe1qaz.7958.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 123qwe1qaz.7958.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 123qwe1qaz.7958.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.

Social Sharing Optimization

123qwe1qaz.7958.com

Open Graph description is not detected on the main page of 123 Qwe 1 Qaz 7958. 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: