Tools & Wizards About Us
spii.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

spii.cn

没有找到站点

Page Load Speed

23.8 sec in total

First Response

240 ms

Resources Loaded

22.7 sec

Page Rendered

827 ms

spii.cn screenshot

About Website

Click here to check amazing Spii content. Otherwise, check out these important facts you probably never knew about spii.cn

亚晟轻钢提供轻钢别墅讨论，自建房屋设计图，宅基地交流，合作集资建房探讨，土地流转交流，自建房日志连载，钢框架结构房屋，木结构房屋，自建房智能家居，家用太阳能发电系统等服务。亚晟轻钢-为了造更好的房子而努力。

Visit spii.cn

Key Findings

We analyzed Spii.cn page load time and found that the first response time was 240 ms and then it took 23.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 were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

spii.cn performance score

0

Network Requests Diagram

index.html

240 ms

common.css

231 ms

index.css

442 ms

idangerous.swiper.css

442 ms

animate.min.css

444 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 52% of them (70 requests) were addressed to the original Spii.cn, 38% (51 requests) were made to Views-cdn.easyliao.com and 6% (8 requests) were made to Group-prd3-chat.easyliao.com. The less responsive or slowest element that took the longest time to load (19.9 sec) belongs to the original domain Spii.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 780.9 kB (16%)

Content Size

5.0 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spii.cn main page is 5.0 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 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 42.1 kB

  • Original 51.3 kB
  • After minification 38.3 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 12.9 kB, which is 25% 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 42.1 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 198.0 kB

  • Original 4.1 MB
  • After minification 3.9 MB

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. Spii images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 527.3 kB

  • Original 795.0 kB
  • After minification 791.9 kB
  • After compression 267.8 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 527.3 kB or 66% of the original size.

CSS Optimization

-23%

Potential reduce by 13.6 kB

  • Original 59.8 kB
  • After minification 59.8 kB
  • After compression 46.2 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. Spii.cn needs all CSS files to be minified and compressed as it can save up to 13.6 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (23%)

Requests Now

127

After Optimization

98

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index.html

index.html

240 ms

common.css

common.css

231 ms

index.css

index.css

442 ms

idangerous.swiper.css

idangerous.swiper.css

442 ms

animate.min.css

animate.min.css

444 ms

swiper.min.css

swiper.min.css

449 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

705 ms

swiper.min.js

swiper.min.js

463 ms

transform.js

transform.js

658 ms

regexkit.js

regexkit.js

658 ms

index.js

index.js

660 ms

from.js

from.js

669 ms

service.js

service.js

689 ms

menu.js

menu.js

876 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

77 ms

easyliao.js

easyliao.js

1379 ms

108722.js

108722.js

1735 ms

logo.png

logo.png

258 ms

phone-number.png

phone-number.png

253 ms

erweima_header.png

erweima_header.png

487 ms

c61d66407f7148bab22e54af65c7eb0a.png

c61d66407f7148bab22e54af65c7eb0a.png

244 ms

c61d66407f7148bab22e54af65c7eb0b.png

c61d66407f7148bab22e54af65c7eb0b.png

240 ms

c61d66407f7148bab22e54af65c7eb0c.png

c61d66407f7148bab22e54af65c7eb0c.png

391 ms

c61d66407f7148bab22e54af65c7eb0d.png

c61d66407f7148bab22e54af65c7eb0d.png

462 ms

green_left.png

green_left.png

469 ms

shadow.png

shadow.png

704 ms

153da71c8ba3447692e842e662066648.png

153da71c8ba3447692e842e662066648.png

512 ms

fdb9dc6b7f994e32b00bb57b8b4ca803.png

fdb9dc6b7f994e32b00bb57b8b4ca803.png

1058 ms

58f8f25e441044eb94c5153a2bb3dd65.png

58f8f25e441044eb94c5153a2bb3dd65.png

690 ms

a122306bba3a467789fb0b32d5a4b62a.png

a122306bba3a467789fb0b32d5a4b62a.png

920 ms

f6ba06943919478883da7120aeb0d0d8.png

f6ba06943919478883da7120aeb0d0d8.png

725 ms

c848f510eac14710add884a3bc22f31f.png

c848f510eac14710add884a3bc22f31f.png

750 ms

2c6786806f4549e082edc51dda6674cf.png

2c6786806f4549e082edc51dda6674cf.png

918 ms

index_01.jpg

index_01.jpg

1408 ms

right_btn.png

right_btn.png

955 ms

1-1FR91523200-L.jpg

1-1FR91523200-L.jpg

1690 ms

1-1FR91523420-L.jpg

1-1FR91523420-L.jpg

2027 ms

left_btn.png

left_btn.png

1144 ms

1-230Q3141A24U.jpg

1-230Q3141A24U.jpg

2828 ms

1-1FR91523580-L.jpg

1-1FR91523580-L.jpg

1986 ms

index_10.jpg

index_10.jpg

2276 ms

plus.png

plus.png

1630 ms

1-230Q5140RCK.jpg

1-230Q5140RCK.jpg

4948 ms

1-230Q610130D56.jpg

1-230Q610130D56.jpg

7152 ms

1-230Q609402D15.jpg

1-230Q609402D15.jpg

3420 ms

1-230Q6092241B5.jpg

1-230Q6092241B5.jpg

19900 ms

1-230Q6091G2494.jpg

1-230Q6091G2494.jpg

19901 ms

1-230Q5144625N4.jpg

1-230Q5144625N4.jpg

19902 ms

1-230Q5141S43J.jpg

1-230Q5141S43J.jpg

19902 ms

48be07fe1e1b40cba247984171d21bd7.jpg

48be07fe1e1b40cba247984171d21bd7.jpg

5550 ms

1-230Q314592a23.jpg

1-230Q314592a23.jpg

6005 ms

1-230Q40RS2P7.jpg

1-230Q40RS2P7.jpg

8146 ms

collect

collect

1245 ms

hm.js

hm.js

1067 ms

iconfont.woff

iconfont.woff

7211 ms

1-230Q40RPS40.jpg

1-230Q40RPS40.jpg

11768 ms

1-230Q40RH0295.jpg

1-230Q40RH0295.jpg

13027 ms

1-230Q31454212T.jpg

1-230Q31454212T.jpg

17729 ms

footer_bottom_7.png

footer_bottom_7.png

13249 ms

footer_erweima.jpg

footer_erweima.jpg

13338 ms

weibo.jpg

weibo.jpg

13498 ms

tianmao.jpg

tianmao.jpg

13719 ms

footer_bottom_1.png

footer_bottom_1.png

13924 ms

z1.png

z1.png

14130 ms

z2.png

z2.png

14185 ms

z3.png

z3.png

14392 ms

z4.png

z4.png

14591 ms

z5.png

z5.png

14787 ms

z6.png

z6.png

14842 ms

1-230Q2162H62c.jpg

1-230Q2162H62c.jpg

16908 ms

1-230Q2164411K7.jpg

1-230Q2164411K7.jpg

19119 ms

webcall.css

webcall.css

950 ms

force.css

force.css

1155 ms

main.js

main.js

2221 ms

1-230Q2164629406.jpg

1-230Q2164629406.jpg

18530 ms

3cfe598724294ad0a525dd0295aadc52.jpg

3cfe598724294ad0a525dd0295aadc52.jpg

19143 ms

hm.gif

hm.gif

296 ms

footbg.jpg

footbg.jpg

19566 ms

bj.png

bj.png

18938 ms

add

add

1041 ms

init

init

1020 ms

isChatExist

isChatExist

997 ms

icon.png

icon.png

233 ms

sprite.png

sprite.png

875 ms

open1.png

open1.png

288 ms

contact_from.jpg

contact_from.jpg

968 ms

01.png

01.png

243 ms

chat

chat

328 ms

02.png

02.png

341 ms

03.png

03.png

252 ms

04.png

04.png

251 ms

05.png

05.png

557 ms

06.png

06.png

494 ms

07.png

07.png

558 ms

08.png

08.png

551 ms

09.png

09.png

488 ms

10.png

10.png

570 ms

11.png

11.png

735 ms

12.png

12.png

881 ms

13.png

13.png

841 ms

14.png

14.png

877 ms

15.png

15.png

849 ms

16.png

16.png

859 ms

17.png

17.png

1044 ms

18.png

18.png

1085 ms

19.png

19.png

1168 ms

20.png

20.png

1356 ms

21.png

21.png

1130 ms

22.png

22.png

1160 ms

23.png

23.png

1324 ms

24.png

24.png

1400 ms

25.png

25.png

1396 ms

26.png

26.png

1511 ms

27.png

27.png

1413 ms

28.png

28.png

1668 ms

29.png

29.png

1583 ms

30.png

30.png

1653 ms

31.png

31.png

1650 ms

32.png

32.png

1697 ms

33.png

33.png

1777 ms

34.png

34.png

1877 ms

35.png

35.png

1912 ms

36.png

36.png

1934 ms

getEvent

getEvent

277 ms

37.png

37.png

1795 ms

38.png

38.png

1750 ms

39.png

39.png

1794 ms

fieldList

fieldList

284 ms

40.png

40.png

1814 ms

41.png

41.png

1751 ms

42.png

42.png

1715 ms

report

report

550 ms

datepicker.css

datepicker.css

1642 ms

datepicker.js

datepicker.js

1909 ms

getEvent

getEvent

272 ms

SEO Factors

spii.cn 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 Spii.cn 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 Spii.cn 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

spii.cn

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