Tools & Wizards About Us
ftzwo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ftzwo.com

Page Load Speed

10.9 sec in total

First Response

639 ms

Resources Loaded

9.5 sec

Page Rendered

740 ms

ftzwo.com screenshot

About Website

Click here to check amazing Ftzwo content. Otherwise, check out these important facts you probably never knew about ftzwo.com

Visit ftzwo.com

Key Findings

We analyzed Ftzwo.com page load time and found that the first response time was 639 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

ftzwo.com performance score

0

Network Requests Diagram

www.ftzwo.com

639 ms

push.js

1013 ms

tj.js

224 ms

common.js

430 ms

hm.js

1440 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Ftzwo.com, 19% (16 requests) were made to Img01.whatfugui.com and 7% (6 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source P.qlogo.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.8 kB (7%)

Content Size

688.8 kB

After Optimization

642.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-50%

Potential reduce by 804 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 803 B

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 804 B or 50% of the original size.

Image Optimization

-5%

Potential reduce by 29.6 kB

  • Original 631.7 kB
  • After minification 602.0 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. Ftzwo images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 5.0 kB

  • Original 19.1 kB
  • After minification 18.4 kB
  • After compression 14.0 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 5.0 kB or 26% of the original size.

CSS Optimization

-31%

Potential reduce by 11.3 kB

  • Original 36.5 kB
  • After minification 36.5 kB
  • After compression 25.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. Ftzwo.com needs all CSS files to be minified and compressed as it can save up to 11.3 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (28%)

Requests Now

58

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ftzwo.com

www.ftzwo.com

639 ms

push.js

push.js

1013 ms

tj.js

tj.js

224 ms

common.js

common.js

430 ms

hm.js

hm.js

1440 ms

21348097.js

21348097.js

1658 ms

hm.gif

hm.gif

329 ms

thsp.html

thsp.html

432 ms

0.22608238505199552

0.22608238505199552

430 ms

0.3095325625035912

0.3095325625035912

427 ms

0.60989586613141

0.60989586613141

429 ms

0.8292628682684153

0.8292628682684153

429 ms

0.09438113449141383

0.09438113449141383

428 ms

165.3.92.59

165.3.92.59

241 ms

ate.css

ate.css

220 ms

zui.css

zui.css

641 ms

tb.js

tb.js

415 ms

qq1.js

qq1.js

416 ms

dht.js

dht.js

445 ms

dh.js

dh.js

443 ms

sp.js

sp.js

443 ms

sp1.js

sp1.js

466 ms

gg.js

gg.js

615 ms

dl.js

dl.js

618 ms

tz.js

tz.js

863 ms

z1.js

z1.js

869 ms

qq2.js

qq2.js

870 ms

qq3.js

qq3.js

883 ms

CE42AF7258D2FC4E.jpg

CE42AF7258D2FC4E.jpg

1488 ms

9F13D5E3B76A92AD.jpg

9F13D5E3B76A92AD.jpg

1622 ms

F128CD3A2615604D.jpg

F128CD3A2615604D.jpg

1795 ms

29FC45E96E154ECF.jpg

29FC45E96E154ECF.jpg

1576 ms

171DC5982349CE0A.jpg

171DC5982349CE0A.jpg

1617 ms

3E66DE33540485F4.jpg

3E66DE33540485F4.jpg

1793 ms

5D60B5DCD097A250.jpg

5D60B5DCD097A250.jpg

1698 ms

2D9D7AEAC1A2D335.jpg

2D9D7AEAC1A2D335.jpg

2065 ms

8536593125F42581.jpg

8536593125F42581.jpg

1784 ms

E1090776C3C7B194.jpg

E1090776C3C7B194.jpg

2067 ms

5D10E01F8982854A.jpg

5D10E01F8982854A.jpg

1959 ms

57CF1D29FC967E61.jpg

57CF1D29FC967E61.jpg

2064 ms

8B58F2B5CB90106A.jpg

8B58F2B5CB90106A.jpg

2064 ms

062EE3FE0BD072BA.jpg

062EE3FE0BD072BA.jpg

2415 ms

6A1665E9111811C9.jpg

6A1665E9111811C9.jpg

2497 ms

7D014F02010353B0.jpg

7D014F02010353B0.jpg

2524 ms

1.gif

1.gif

256 ms

3aa1141b05a84013924b02e75634d2c3.gif

3aa1141b05a84013924b02e75634d2c3.gif

1972 ms

4fe2b2a7d33f4c66a1aa0bd1ae2b2824.gif

4fe2b2a7d33f4c66a1aa0bd1ae2b2824.gif

2259 ms

ae1c0bf33ec54d47b79b60bafdc5045f.gif

ae1c0bf33ec54d47b79b60bafdc5045f.gif

1782 ms

631ae484b62b4063cbda48ea.gif

631ae484b62b4063cbda48ea.gif

997 ms

6319c14df74eb42056026c86.gif

6319c14df74eb42056026c86.gif

999 ms

03964120009rs6jjg70FF.gif

03964120009rs6jjg70FF.gif

797 ms

video-play.png

video-play.png

269 ms

230-160.gif

230-160.gif

697 ms

0yFUidjGHhQ

0yFUidjGHhQ

828 ms

0

0

2997 ms

0yFVWR9AM6k

0yFVWR9AM6k

721 ms

0

0

3651 ms

FAEB9081-6DBB-16416-34-0293D8D59276.alpha

FAEB9081-6DBB-16416-34-0293D8D59276.alpha

1165 ms

iconfont.woff

iconfont.woff

240 ms

iconfont.woff

iconfont.woff

223 ms

iconfont.ttf

iconfont.ttf

269 ms

iconfont.ttf

iconfont.ttf

304 ms

iconfont.svg

iconfont.svg

232 ms

iconfont.svg

iconfont.svg

231 ms

hm.js

hm.js

546 ms

hm.js

hm.js

1306 ms

692cdac1f5eb4eba9271f2ea2c0f0772.gif

692cdac1f5eb4eba9271f2ea2c0f0772.gif

673 ms

d8766c5ff8e42ad5dafb8044a9ffd1e1.gif

d8766c5ff8e42ad5dafb8044a9ffd1e1.gif

647 ms

6322becc136c30cff133c82c.gif

6322becc136c30cff133c82c.gif

737 ms

xxww.gif

xxww.gif

770 ms

1.gif

1.gif

375 ms

200200.gif

200200.gif

659 ms

aa17e173a4c65df1ec1b23879a2d31.gif

aa17e173a4c65df1ec1b23879a2d31.gif

2083 ms

gif22.gif

gif22.gif

1633 ms

0a3595890550d9575b764483eb6f7fdb.gif

0a3595890550d9575b764483eb6f7fdb.gif

1035 ms

0103d120009h1026r1BFC.gif

0103d120009h1026r1BFC.gif

369 ms

290299ed48d84c7b99d8fbd8a96a254c

290299ed48d84c7b99d8fbd8a96a254c

878 ms

008rpxqrgy1h385k3gbgwg302s02swf0.gif

008rpxqrgy1h385k3gbgwg302s02swf0.gif

886 ms

0

0

1630 ms

631ae484b62b4063cbda48ea.gif

631ae484b62b4063cbda48ea.gif

728 ms

6319c14df74eb42056026c86.gif

6319c14df74eb42056026c86.gif

727 ms

hm.gif

hm.gif

313 ms

default_d_s_large.gif

default_d_s_large.gif

11 ms

hm.gif

hm.gif

312 ms

SEO Factors

ftzwo.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 Ftzwo.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 Ftzwo.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

ftzwo.com

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