Tools & Wizards About Us
fanlihe.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fanlihe.com

微信小程序开发_微信小程序开发工具_国内领先微信小程序开发平台-地球城微信小程序官网

Page Load Speed

24.6 sec in total

First Response

2.2 sec

Resources Loaded

22.1 sec

Page Rendered

278 ms

fanlihe.com screenshot

About Website

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

【地球城微信小程序】是国内领先的微信小程序开发工具,微信小程序开发数量突破10万个,是第2名至第5名的累加和,地球城微信小程序开发平台提出营销型微信小程序概念,历经18次优化,制定"四大系统+七大角度"的行业标准.微信小程序开发工具-地球城微信小程序,客户满意度近乎100%.

Visit fanlihe.com

Key Findings

We analyzed Fanlihe.com page load time and found that the first response time was 2.2 sec and then it took 22.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.

Performance Metrics

fanlihe.com performance score

0

Network Requests Diagram

fanlihe.com

2176 ms

index.css

1058 ms

advss.css

594 ms

mootools-1.2.1.js

4966 ms

myfocus-2.0.2.js

4540 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 33% of them (27 requests) were addressed to the original Fanlihe.com, 40% (32 requests) were made to Image.dqccc.com and 15% (12 requests) were made to Pic.dq3c.cn. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Pic.dq3c.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 143.4 kB (33%)

Content Size

432.5 kB

After Optimization

289.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 40.4 kB

  • Original 50.5 kB
  • After minification 47.1 kB
  • After compression 10.1 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 40.4 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 27.1 kB

  • Original 269.7 kB
  • After minification 242.6 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. Fanlihe images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 57.5 kB

  • Original 87.6 kB
  • After minification 86.5 kB
  • After compression 30.1 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 57.5 kB or 66% of the original size.

CSS Optimization

-75%

Potential reduce by 18.4 kB

  • Original 24.7 kB
  • After minification 22.4 kB
  • After compression 6.3 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. Fanlihe.com needs all CSS files to be minified and compressed as it can save up to 18.4 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (34%)

Requests Now

79

After Optimization

52

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fanlihe.com

fanlihe.com

2176 ms

index.css

index.css

1058 ms

advss.css

advss.css

594 ms

mootools-1.2.1.js

mootools-1.2.1.js

4966 ms

myfocus-2.0.2.js

myfocus-2.0.2.js

4540 ms

fanlihe.js

fanlihe.js

3082 ms

main.css

main.css

265 ms

head.css

head.css

305 ms

help.css

help.css

266 ms

right.css

right.css

530 ms

footer.css

footer.css

535 ms

top_login.jpg

top_login.jpg

269 ms

10002.jpg

10002.jpg

924 ms

loading.gif

loading.gif

225 ms

1001.jpg

1001.jpg

836 ms

1002.jpg

1002.jpg

509 ms

1003.jpg

1003.jpg

454 ms

1004.jpg

1004.jpg

1197 ms

biaoshi.gif

biaoshi.gif

529 ms

beian.png

beian.png

1019 ms

xinlang.jpg

xinlang.jpg

299 ms

top_bg.jpg

top_bg.jpg

267 ms

logo.jpg

logo.jpg

560 ms

head_text_bg.gif

head_text_bg.gif

289 ms

navi_left.jpg

navi_left.jpg

521 ms

navi_line.jpg

navi_line.jpg

530 ms

login_top.jpg

login_top.jpg

583 ms

regsymbol.jpg

regsymbol.jpg

581 ms

qq.gif

qq.gif

598 ms

10057.jpg

10057.jpg

913 ms

10005.jpg

10005.jpg

911 ms

10056.gif

10056.gif

791 ms

10001.jpg

10001.jpg

974 ms

10039.jpg

10039.jpg

745 ms

10008.jpg

10008.jpg

976 ms

10011.jpg

10011.jpg

1020 ms

10016.jpg

10016.jpg

1130 ms

10025.jpg

10025.jpg

1131 ms

10017.jpg

10017.jpg

1133 ms

10018.jpg

10018.jpg

1204 ms

10012.jpg

10012.jpg

1209 ms

10024.jpg

10024.jpg

1277 ms

10036.jpg

10036.jpg

1352 ms

10044.jpg

10044.jpg

1356 ms

10027.jpg

10027.jpg

1359 ms

10028.jpg

10028.jpg

1435 ms

10029.jpg

10029.jpg

1440 ms

10035.jpg

10035.jpg

1533 ms

10009.jpg

10009.jpg

1595 ms

10050.jpg

10050.jpg

1579 ms

10040.jpg

10040.jpg

1586 ms

10043.jpg

10043.jpg

1664 ms

10037.jpg

10037.jpg

1670 ms

10021.jpg

10021.jpg

1789 ms

10049.jpg

10049.jpg

1808 ms

10004.jpg

10004.jpg

1814 ms

10033.jpg

10033.jpg

1819 ms

10045.bmp

10045.bmp

2125 ms

10038.jpg

10038.jpg

1899 ms

10022.jpg

10022.jpg

2055 ms

navi_mid.jpg

navi_mid.jpg

749 ms

navi_on.jpg

navi_on.jpg

749 ms

navi_bottom.jpg

navi_bottom.jpg

791 ms

mF_quwan.css

mF_quwan.css

606 ms

mF_quwan.js

mF_quwan.js

671 ms

index_bg.jpg

index_bg.jpg

706 ms

trigger_bg.jpg

trigger_bg.jpg

710 ms

loginbg.jpg

loginbg.jpg

744 ms

enter_login.jpg

enter_login.jpg

896 ms

ico.jpg

ico.jpg

904 ms

stat.php

stat.php

1847 ms

stat.htm

stat.htm

179 ms

core.php

core.php

975 ms

9.gif

9.gif

768 ms

pic1.gif

pic1.gif

768 ms

qq_bg.jpg

qq_bg.jpg

273 ms

h.js

h.js

603 ms

hm.gif

hm.gif

304 ms

app.gif

app.gif

1834 ms

button_21.gif

button_21.gif

452 ms

button_21.gif

button_21.gif

450 ms

SEO Factors

fanlihe.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 Fanlihe.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 Fanlihe.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

fanlihe.com

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