Tools & Wizards About Us
facesea.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

facesea.com

超滤净水器 - 深圳市菲喜斯科技有限公司

Page Load Speed

9.6 sec in total

First Response

3.4 sec

Resources Loaded

6.1 sec

Page Rendered

161 ms

facesea.com screenshot

About Website

Visit facesea.com now to see the best up-to-date Facesea content and also check out these interesting facts you probably never knew about facesea.com

深圳市菲喜斯科技有限公司拥有业内非常完善的的超滤净水机生产线和国内较大的超滤膜生产车间，实现产品自主开模，产品设计、生产、开发制造一体化，严格把控产品生产的每一个工艺流程，引进国际先进全数字化生产检测设备， 严把产品检测程序，突出产品品质和售后服务，为全国经销商提供完善的售后服务体系，为消费者提供更完善的售后服务体验，成为行业以及社会有影响力的综合服务型企业。

Visit facesea.com

Key Findings

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

Performance Metrics

facesea.com performance score

0

Network Requests Diagram

facesea.com

3365 ms

css.css

872 ms

css.css

908 ms

css.css

665 ms

nivo-slider.css

951 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 36% of them (13 requests) were addressed to the original Facesea.com, 64% (23 requests) were made to Static.facesea.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Facesea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.1 kB (63%)

Content Size

170.4 kB

After Optimization

63.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Facesea.com main page is 170.4 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. Javascripts take 110.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 8.6 kB

  • Original 11.7 kB
  • After minification 11.5 kB
  • After compression 3.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 8.6 kB or 74% of the original size.

Image Optimization

-34%

Potential reduce by 9.0 kB

  • Original 26.0 kB
  • After minification 17.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. Obviously, Facesea needs image optimization as it can save up to 9.0 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 72.9 kB

  • Original 110.8 kB
  • After minification 109.6 kB
  • After compression 37.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 72.9 kB or 66% of the original size.

CSS Optimization

-76%

Potential reduce by 16.6 kB

  • Original 21.9 kB
  • After minification 18.9 kB
  • After compression 5.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. Facesea.com needs all CSS files to be minified and compressed as it can save up to 16.6 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

facesea.com

facesea.com

3365 ms

css.css

css.css

872 ms

css.css

css.css

908 ms

css.css

css.css

665 ms

nivo-slider.css

nivo-slider.css

951 ms

default.css

default.css

1251 ms

galleriffic-3.css

galleriffic-3.css

441 ms

jquery-1.9.0.min.js

jquery-1.9.0.min.js

718 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

914 ms

SLib.js

SLib.js

622 ms

Global.min.js

Global.min.js

933 ms

SLib.Navigation.min.js

SLib.Navigation.min.js

688 ms

OnlineService.min.js

OnlineService.min.js

952 ms

header-bg.gif

header-bg.gif

121 ms

logo.gif

logo.gif

373 ms

search-bg.png

search-bg.png

126 ms

menu-bg.gif

menu-bg.gif

115 ms

menu-line.gif

menu-line.gif

143 ms

20140412231422482583.gif

20140412231422482583.gif

790 ms

XM20140429095133468929.gif

XM20140429095133468929.gif

1101 ms

XM20140429095537490696.gif

XM20140429095537490696.gif

1048 ms

XM20140429110816315202.gif

XM20140429110816315202.gif

1055 ms

XM20140429111135214716.gif

XM20140429111135214716.gif

1164 ms

XM20140429110710652948.gif

XM20140429110710652948.gif

1184 ms

XM20140429110858543411.gif

XM20140429110858543411.gif

977 ms

XM20140429110640417979.gif

XM20140429110640417979.gif

1271 ms

XM20140429111345922019.gif

XM20140429111345922019.gif

1355 ms

about.gif

about.gif

1102 ms

loading.gif

loading.gif

50 ms

Mdefault-no-image.png

Mdefault-no-image.png

179 ms

index-main.gif

index-main.gif

1401 ms

index-product.gif

index-product.gif

1420 ms

dot.jpg

dot.jpg

1454 ms

contact.gif

contact.gif

1413 ms

online.png

online.png

779 ms

bullets.png

bullets.png

42 ms

SEO Factors

facesea.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 Facesea.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 Facesea.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

facesea.com

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