Tools & Wizards About Us
9611111.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

9611111.com

Page Load Speed

46.9 sec in total

First Response

10.5 sec

Resources Loaded

36.2 sec

Page Rendered

165 ms

9611111.com screenshot

About Website

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

Visit 9611111.com

Key Findings

We analyzed 9611111.com page load time and found that the first response time was 10.5 sec and then it took 36.4 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 were 14 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

9611111.com performance score

0

Network Requests Diagram

9611111.com

10469 ms

style.css

3721 ms

css.css

3747 ms

jquery-1[1].2.1.pack.js

8987 ms

slide.js

3879 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 58% of them (38 requests) were addressed to the original 9611111.com, 23% (15 requests) were made to Sysimages.tq.cn and 3% (2 requests) were made to 0. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain 9611111.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.0 kB (37%)

Content Size

434.8 kB

After Optimization

274.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 32.1 kB

  • Original 40.9 kB
  • After minification 31.5 kB
  • After compression 8.7 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. This page needs HTML code to be minified as it can gain 9.4 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 32.1 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 12.8 kB

  • Original 235.2 kB
  • After minification 222.4 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. 9611111 images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 97.1 kB

  • Original 137.0 kB
  • After minification 134.9 kB
  • After compression 39.9 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 97.1 kB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 17.9 kB

  • Original 21.7 kB
  • After minification 19.3 kB
  • After compression 3.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. 9611111.com needs all CSS files to be minified and compressed as it can save up to 17.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (40%)

Requests Now

48

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

9611111.com

9611111.com

10469 ms

style.css

style.css

3721 ms

css.css

css.css

3747 ms

jquery-1[1].2.1.pack.js

jquery-1[1].2.1.pack.js

8987 ms

slide.js

slide.js

3879 ms

stat.php

stat.php

2546 ms

a

a

8 ms

floatcard

floatcard

5660 ms

bg.jpg

bg.jpg

1156 ms

tel.jpg

tel.jpg

4458 ms

logo.jpg

logo.jpg

8289 ms

menu_bg.jpg

menu_bg.jpg

20040 ms

menu_bg_hover1.jpg

menu_bg_hover1.jpg

2815 ms

kstd.jpg

kstd.jpg

2071 ms

search.jpg

search.jpg

2512 ms

khzq_bg.jpg

khzq_bg.jpg

2952 ms

khzq.jpg

khzq.jpg

3573 ms

khzq_line_bg.jpg

khzq_line_bg.jpg

3397 ms

img2.jpg

img2.jpg

8314 ms

guize.jpg

guize.jpg

14659 ms

zscspt.jpg

zscspt.jpg

6690 ms

dzqzcspt.jpg

dzqzcspt.jpg

9019 ms

title_bg.jpg

title_bg.jpg

7081 ms

xglj.jpg

xglj.jpg

8434 ms

ad.jpg

ad.jpg

20035 ms

bg_transparent.gif

bg_transparent.gif

8755 ms

ad2.jpg

ad2.jpg

20035 ms

ad3.jpg

ad3.jpg

20035 ms

cp_szzs.jpg

cp_szzs.jpg

9932 ms

cp_hc.jpg

cp_hc.jpg

10371 ms

cp_hyyy.jpg

cp_hyyy.jpg

15017 ms

magazine1.jpg

magazine1.jpg

20035 ms

magazine2.jpg

magazine2.jpg

20036 ms

zxzx.jpg

zxzx.jpg

19998 ms

point_2.jpg

point_2.jpg

19998 ms

cp.jpg

cp.jpg

19998 ms

cp_bg1.jpg

cp_bg1.jpg

19998 ms

point_1.jpg

point_1.jpg

19997 ms

cp_bg2.jpg

cp_bg2.jpg

19997 ms

cp_bg3.jpg

cp_bg3.jpg

19998 ms

magazine3.jpg

magazine3.jpg

19998 ms

icon_zz.gif

icon_zz.gif

688 ms

stat.htm

stat.htm

168 ms

core.php

core.php

1101 ms

9.gif

9.gif

967 ms

pic1.gif

pic1.gif

789 ms

s.gif

s.gif

34 ms

app.gif

app.gif

833 ms

all_20100501.js

all_20100501.js

5038 ms

as.js

as.js

711 ms

style.css

style.css

1129 ms

getonline

getonline

15501 ms

float.js

float.js

2137 ms

invite.js

invite.js

3866 ms

icooff.gif

icooff.gif

565 ms

off.gif

off.gif

4423 ms

on103.gif

on103.gif

563 ms

on104.gif

on104.gif

1900 ms

on108.gif

on108.gif

2823 ms

on107.gif

on107.gif

1122 ms

on110.gif

on110.gif

1130 ms

btm.gif

btm.gif

1678 ms

head.gif

head.gif

1191 ms

body.gif

body.gif

2300 ms

scriptonline.js

scriptonline.js

545 ms

SEO Factors

9611111.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

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

9611111.com

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