Tools & Wizards About Us
fzeson.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fzeson.com

Page Load Speed

19 sec in total

First Response

3.8 sec

Resources Loaded

15.1 sec

Page Rendered

115 ms

fzeson.com screenshot

About Website

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

福建爱生电气有限公司

Visit fzeson.com

Key Findings

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

fzeson.com performance score

0

Network Requests Diagram

fzeson.com

3790 ms

index.css

541 ms

common.css

772 ms

nav.js

560 ms

banner3.jpg

3710 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that all of those requests were addressed to Fzeson.com and no external sources were called. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Fzeson.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.1 kB (28%)

Content Size

68.0 kB

After Optimization

48.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fzeson.com main page is 68.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 51.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 6.0 kB

  • Original 8.4 kB
  • After minification 6.7 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 1.8 kB, which is 21% 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 6.0 kB or 72% of the original size.

Image Optimization

-14%

Potential reduce by 7.1 kB

  • Original 51.1 kB
  • After minification 44.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, Fzeson needs image optimization as it can save up to 7.1 kB or 14% 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 1.1 kB

  • Original 1.7 kB
  • After minification 1.4 kB
  • After compression 564 B

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 1.1 kB or 66% of the original size.

CSS Optimization

-71%

Potential reduce by 4.8 kB

  • Original 6.7 kB
  • After minification 5.7 kB
  • After compression 2.0 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. Fzeson.com needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 71% of the original size.

Requests Breakdown

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

Requests Now

22

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fzeson.com

fzeson.com

3790 ms

index.css

index.css

541 ms

common.css

common.css

772 ms

nav.js

nav.js

560 ms

banner3.jpg

banner3.jpg

3710 ms

20130618155603970.jpg

20130618155603970.jpg

496 ms

20130618144053394.jpg

20130618144053394.jpg

517 ms

20130618143604903.jpg

20130618143604903.jpg

558 ms

04.jpg

04.jpg

1323 ms

20130618160816791.jpg

20130618160816791.jpg

1032 ms

20130618160719231.jpg

20130618160719231.jpg

761 ms

20130618160611862.jpg

20130618160611862.jpg

800 ms

top.gif

top.gif

1383 ms

nav_bg.gif

nav_bg.gif

998 ms

scrollUl.gif

scrollUl.gif

1077 ms

sc_li_a.gif

sc_li_a.gif

1919 ms

scor_li.gif

scor_li.gif

1271 ms

b03_bg.gif

b03_bg.gif

1328 ms

more.gif

more.gif

1513 ms

footer_left.gif

footer_left.gif

1567 ms

footer_right.gif

footer_right.gif

1586 ms

banner2.jpg

banner2.jpg

3840 ms

banner1.jpg

banner1.jpg

5042 ms

SEO Factors

fzeson.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fzeson.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 Fzeson.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

fzeson.com

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