Tools & Wizards About Us
cnfenghe.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cnfenghe.com

Hebei Fenghe Biotechnology | Biodegradable dental floss | Dental floss |Dental floss tape

Page Load Speed

28.7 sec in total

First Response

750 ms

Resources Loaded

17.9 sec

Page Rendered

10.1 sec

cnfenghe.com screenshot

About Website

Welcome to cnfenghe.com homepage info - get ready to check Cn Fenghe best content right away, or after learning these important things about cnfenghe.com

Founded in 2005,Hebei Fenghe Biotechnology INC.,LTD. is a professional manufacturer of high-tech dental floss production

Visit cnfenghe.com

Key Findings

We analyzed Cnfenghe.com page load time and found that the first response time was 750 ms and then it took 28 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

cnfenghe.com performance score

0

Network Requests Diagram

cnfenghe.com

750 ms

www.cnfenghe.com

488 ms

www.cnfenghe.com

1475 ms

animate.css,iconfont.css,bootstrap.min.css,response.min.css

1818 ms

site_impt_r.css

2070 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 15% of them (14 requests) were addressed to the original Cnfenghe.com, 29% (27 requests) were made to Img202.yun300.cn and 22% (20 requests) were made to Static.yun300.cn. The less responsive or slowest element that took the longest time to load (7.1 sec) relates to the external source Static202.yun300.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (28%)

Content Size

6.7 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cnfenghe.com main page is 6.7 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. 70% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 102.9 kB

  • Original 118.5 kB
  • After minification 97.0 kB
  • After compression 15.6 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 21.4 kB, which is 18% 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 102.9 kB or 87% of the original size.

Image Optimization

-19%

Potential reduce by 1.1 MB

  • Original 5.8 MB
  • After minification 4.7 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. Obviously, Cn Fenghe needs image optimization as it can save up to 1.1 MB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 20.3 kB

  • Original 29.4 kB
  • After minification 20.9 kB
  • After compression 9.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 20.3 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 647.8 kB

  • Original 769.9 kB
  • After minification 619.3 kB
  • After compression 122.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. Cnfenghe.com needs all CSS files to be minified and compressed as it can save up to 647.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (43%)

Requests Now

83

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cnfenghe.com

cnfenghe.com

750 ms

www.cnfenghe.com

www.cnfenghe.com

488 ms

www.cnfenghe.com

www.cnfenghe.com

1475 ms

animate.css,iconfont.css,bootstrap.min.css,response.min.css

animate.css,iconfont.css,bootstrap.min.css,response.min.css

1818 ms

site_impt_r.css

site_impt_r.css

2070 ms

ftmpl_impt_ce73f756-8afa-42a8-9180-91f9c9ea8a63.css

ftmpl_impt_ce73f756-8afa-42a8-9180-91f9c9ea8a63.css

3275 ms

page_impt_home1.css

page_impt_home1.css

3953 ms

public.css

public.css

298 ms

catePublic.css

catePublic.css

302 ms

swiper.min.css

swiper.min.css

427 ms

rBQBHVyLJ8GEdmeyAAAAAGqmAjE7841.js

rBQBHVyLJ8GEdmeyAAAAAGqmAjE7841.js

321 ms

swiper.min.js

swiper.min.js

536 ms

interwords_en.min.js,handle.min.js,libs.min.js,render.min.js

interwords_en.min.js,handle.min.js,libs.min.js,render.min.js

2484 ms

rBQBG1zaKjeEZqnoAAAAAIaDhfQ3178.js

rBQBG1zaKjeEZqnoAAAAAIaDhfQ3178.js

335 ms

rBQBG1zEYY2ENWyFAAAAAMkBaKg1347.js

rBQBG1zEYY2ENWyFAAAAAMkBaKg1347.js

335 ms

rBQBHF0t2j2EOlsxAAAAAO-8cyI5368.js

rBQBHF0t2j2EOlsxAAAAAO-8cyI5368.js

78 ms

waypoints.min.js

waypoints.min.js

2153 ms

jquery.counterup.min.js

jquery.counterup.min.js

2171 ms

wow.min.js

wow.min.js

354 ms

public.js

public.js

262 ms

rBQBHWEscXeETfJKAAAAAKP1gU0033.png

rBQBHWEscXeETfJKAAAAAKP1gU0033.png

581 ms

bann1.png

bann1.png

123 ms

paste1630046243964.png

paste1630046243964.png

1382 ms

s.png

s.png

268 ms

q04.png

q04.png

390 ms

gs.png

gs.png

418 ms

Q05.png

Q05.png

190 ms

Q06.png

Q06.png

435 ms

q33.png

q33.png

232 ms

01.png

01.png

230 ms

02.png

02.png

232 ms

kou2.png

kou2.png

266 ms

kaong.png

kaong.png

267 ms

03.png

03.png

265 ms

04.png

04.png

266 ms

q22.png

q22.png

267 ms

q14.png

q14.png

268 ms

q19.png

q19.png

269 ms

q20.png

q20.png

270 ms

q15.png

q15.png

269 ms

q21.png

q21.png

269 ms

hezi.png

hezi.png

281 ms

q18.png

q18.png

725 ms

q16.png

q16.png

282 ms

EQ_CUfPuT76Mp1qSvzz6RQ.png_%7Bi%7Dxaf.png

EQ_CUfPuT76Mp1qSvzz6RQ.png_%7Bi%7Dxaf.png

1481 ms

raF8KWq6SCGl1yMR7HOGsQ.png_%7Bi%7Dxaf.png

raF8KWq6SCGl1yMR7HOGsQ.png_%7Bi%7Dxaf.png

329 ms

zrmqhizKSACqmvGqo1xKAQ.png_%7Bi%7Dxaf.png

zrmqhizKSACqmvGqo1xKAQ.png_%7Bi%7Dxaf.png

329 ms

rBQBHGEwOLKEJhzHAAAAAOGLIFY865.png

rBQBHGEwOLKEJhzHAAAAAOGLIFY865.png

693 ms

font_2340746_a3r0qochp1u.woff

font_2340746_a3r0qochp1u.woff

919 ms

iconfont.woff

iconfont.woff

14 ms

iconfont.woff

iconfont.woff

1089 ms

rBQBHWEsc8uEXS0gAAAAAJSTDlo286.png

rBQBHWEsc8uEXS0gAAAAAJSTDlo286.png

530 ms

utils.min.js

utils.min.js

255 ms

rBQBHGEsdiSEVI5MAAAAALR68vE719.png

rBQBHGEsdiSEVI5MAAAAALR68vE719.png

495 ms

paste1630460242955.png

paste1630460242955.png

884 ms

camera.png

camera.png

372 ms

bjxian.png

bjxian.png

1106 ms

rBQBG1zmEo6EfEanAAAAAHV_yfE351.png

rBQBG1zmEo6EfEanAAAAAHV_yfE351.png

559 ms

paste1630461673032.png

paste1630461673032.png

7081 ms

rBQBHGEteCGEbwwjAAAAAMz6Y-M583.png

rBQBHGEteCGEbwwjAAAAAMz6Y-M583.png

712 ms

q1.png

q1.png

1557 ms

swiper.min.js

swiper.min.js

1589 ms

rBQBHWEsfM6ECHjkAAAAAKeUSo4704.png

rBQBHWEsfM6ECHjkAAAAAKeUSo4704.png

1056 ms

q12.png

q12.png

1412 ms

img33.jpg

img33.jpg

1476 ms

response.js

response.js

268 ms

portalResVideo_list-01.min.js

portalResVideo_list-01.min.js

1027 ms

portalResPublic_codeContainer-01.min.js

portalResPublic_codeContainer-01.min.js

894 ms

portalResProduct_list-01.min.js

portalResProduct_list-01.min.js

1030 ms

portalResMessage_form-01.min.js

portalResMessage_form-01.min.js

908 ms

iconfont.ttf

iconfont.ttf

230 ms

jquery.mediaQuery.min.js

jquery.mediaQuery.min.js

880 ms

jquery.formValidate.min.js

jquery.formValidate.min.js

1064 ms

jquery.md5.min.js

jquery.md5.min.js

237 ms

jquery.message.min.js

jquery.message.min.js

1935 ms

laydate.min.js

laydate.min.js

1463 ms

cityjson

cityjson

1142 ms

jquery.confirm.min.js

jquery.confirm.min.js

1254 ms

jquery.fileDownload.min.js

jquery.fileDownload.min.js

784 ms

iconfont.svg

iconfont.svg

436 ms

laydate.css

laydate.css

25 ms

portalRouter

portalRouter

2641 ms

portalRouter

portalRouter

1398 ms

initPagination.min.js

initPagination.min.js

464 ms

swiper4.4.2.min.js

swiper4.4.2.min.js

891 ms

pagination.min.js

pagination.min.js

400 ms

EQ_CUfPuT76Mp1qSvzz6RQ.png

EQ_CUfPuT76Mp1qSvzz6RQ.png

921 ms

raF8KWq6SCGl1yMR7HOGsQ.png

raF8KWq6SCGl1yMR7HOGsQ.png

1445 ms

zrmqhizKSACqmvGqo1xKAQ.png

zrmqhizKSACqmvGqo1xKAQ.png

1514 ms

afterLoad.min.js

afterLoad.min.js

1449 ms

sdkStatisticsNew.min.js

sdkStatisticsNew.min.js

915 ms

sensorsdataNew.min.js

sensorsdataNew.min.js

3354 ms

SEO Factors

cnfenghe.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cnfenghe.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Cnfenghe.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

cnfenghe.com

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