Tools & Wizards About Us
yafl.com.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

yafl.com.cn

域名到期-域名续费提醒

Page Load Speed

35.5 sec in total

First Response

2.1 sec

Resources Loaded

32.7 sec

Page Rendered

648 ms

yafl.com.cn screenshot

About Website

Click here to check amazing Yafl content for China. Otherwise, check out these important facts you probably never knew about yafl.com.cn

域名是企业重要的资产,您所访问的域名已经过期,请尽快联络注册商续费

Visit yafl.com.cn

Key Findings

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

Performance Metrics

yafl.com.cn performance score

0

Network Requests Diagram

yafl.com.cn

2122 ms

index_index_3469942563.css

3939 ms

index_index_1852614733.js

5785 ms

scrollpagination.js

1209 ms

index.js

922 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 50% of them (42 requests) were addressed to the original Yafl.com.cn, 15% (13 requests) were made to Img4.duoduo123.com and 5% (4 requests) were made to Img.alicdn.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Image1.900.la.

Page Optimization Overview & Recommendations

Page size can be reduced by 199.7 kB (38%)

Content Size

531.6 kB

After Optimization

331.9 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-82%

Potential reduce by 99.0 kB

  • Original 120.3 kB
  • After minification 113.3 kB
  • After compression 21.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 99.0 kB or 82% of the original size.

Image Optimization

-25%

Potential reduce by 80.4 kB

  • Original 322.5 kB
  • After minification 242.1 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, Yafl needs image optimization as it can save up to 80.4 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 20.3 kB

  • Original 88.8 kB
  • After minification 86.8 kB
  • After compression 68.5 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 20.3 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (61%)

Requests Now

79

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yafl.com.cn

yafl.com.cn

2122 ms

index_index_3469942563.css

index_index_3469942563.css

3939 ms

index_index_1852614733.js

index_index_1852614733.js

5785 ms

scrollpagination.js

scrollpagination.js

1209 ms

index.js

index.js

922 ms

plugin.php

plugin.php

597 ms

wpa.php

wpa.php

1561 ms

tkapi.js

tkapi.js

291 ms

jd.png

jd.png

4166 ms

10335140498.jpg

10335140498.jpg

5436 ms

yihaodian.png

yihaodian.png

4175 ms

dangdang.png

dangdang.png

4174 ms

suning.png

suning.png

4168 ms

yixun.png

yixun.png

4165 ms

nuomi.png

nuomi.png

4165 ms

ly.png

ly.png

4177 ms

mogujie.png

mogujie.png

4405 ms

mi.png

mi.png

4464 ms

09323313463.png

09323313463.png

4460 ms

10491414762.png

10491414762.png

4206 ms

keede.png

keede.png

4183 ms

lamiu.png

lamiu.png

4202 ms

10340842776.jpg

10340842776.jpg

1824 ms

13561135993.jpg

13561135993.jpg

3641 ms

headnav_bg.png

headnav_bg.png

681 ms

top_invite.gif

top_invite.gif

681 ms

header_icon.png

header_icon.png

1014 ms

icon-phone.gif

icon-phone.gif

760 ms

17474710988.png

17474710988.png

2081 ms

switch_width.png

switch_width.png

858 ms

17012722065.png

17012722065.png

1814 ms

search_help.gif

search_help.gif

1882 ms

hotn.gif

hotn.gif

1518 ms

paipai.jpg

paipai.jpg

1865 ms

blank.gif

blank.gif

2157 ms

white-ajax-loader.gif

white-ajax-loader.gif

1998 ms

19565616844.jpg

19565616844.jpg

3241 ms

close.png

close.png

2624 ms

appdl.png

appdl.png

4414 ms

index.php

index.php

2805 ms

top_banner_bg.png

top_banner_bg.png

3750 ms

search_new.png

search_new.png

3415 ms

step-1.png

step-1.png

5066 ms

fanli_layer.png

fanli_layer.png

4134 ms

icon-total.png

icon-total.png

4321 ms

open.gif

open.gif

3681 ms

mall_bg.png

mall_bg.png

4362 ms

time.png

time.png

4607 ms

super_bg.png

super_bg.png

5219 ms

top_logos_sprite.png

top_logos_sprite.png

5533 ms

article_line.png

article_line.png

5028 ms

more.gif

more.gif

4780 ms

service_add.gif

service_add.gif

5601 ms

stat.php

stat.php

2475 ms

click.js

click.js

35 ms

plugin.js

plugin.js

35 ms

load

load

1134 ms

stat.htm

stat.htm

164 ms

core.php

core.php

1847 ms

9.gif

9.gif

1007 ms

hm.js

hm.js

447 ms

loading.gif

loading.gif

1423 ms

Panel.js

Panel.js

910 ms

localStorage.js

localStorage.js

941 ms

index.php

index.php

704 ms

404991.gif

404991.gif

3451 ms

eu2zfu04.gif

eu2zfu04.gif

19973 ms

TB1EPPTLVXXXXXTXXXXXXXXXXXX_!!0-item_pic.jpg_290x290.jpg

TB1EPPTLVXXXXXTXXXXXXXXXXXX_!!0-item_pic.jpg_290x290.jpg

409 ms

index.php

index.php

1132 ms

index.php

index.php

1260 ms

about:blank

about:blank

1262 ms

ban-esc.png

ban-esc.png

2177 ms

TB1xfIqKFXXXXXyXVXXXXXXXXXX_!!0-item_pic.jpg_290x290.jpg

TB1xfIqKFXXXXXyXVXXXXXXXXXX_!!0-item_pic.jpg_290x290.jpg

368 ms

TB2En7dlVXXXXbMXXXXXXXXXXXX_!!2569070479.jpg_290x290.jpg

TB2En7dlVXXXXbMXXXXXXXXXXXX_!!2569070479.jpg_290x290.jpg

331 ms

TB2ExlikpXXXXX6XpXXXXXXXXXX_!!1898825840.jpg_290x290.jpg

TB2ExlikpXXXXX6XpXXXXXXXXXX_!!1898825840.jpg_290x290.jpg

444 ms

hm.gif

hm.gif

224 ms

toolbar_bg.png

toolbar_bg.png

2118 ms

contains.js

contains.js

449 ms

app.gif

app.gif

3955 ms

r.cgi

r.cgi

3801 ms

r.cgi

r.cgi

2079 ms

ta.php

ta.php

552 ms

crmqq.php

crmqq.php

19601 ms

wpa_first_heart_beat.php

wpa_first_heart_beat.php

570 ms

SEO Factors

yafl.com.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 Yafl.com.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 Yafl.com.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

yafl.com.cn

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