Tools & Wizards About Us
faam.com.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

faam.com.cn

宜兴法阿姆工业电池有限公司

Page Load Speed

32.8 sec in total

First Response

1.9 sec

Resources Loaded

29.2 sec

Page Rendered

1.7 sec

faam.com.cn screenshot

About Website

Welcome to faam.com.cn homepage info - get ready to check Faam best content right away, or after learning these important things about faam.com.cn

FAAM集团在1974年成立于意大利中部东海岸，是SERI集团旗下欧洲最重要的铅酸电池、启动电池、锂电池及环保车制造商。2006年在江苏宜兴成立了宜兴法阿姆工业电池有限公司，为中国市场提供优质、高效、清洁的各类电池产品，如有需求，请联系：0510-87600222

Visit faam.com.cn

Key Findings

We analyzed Faam.com.cn page load time and found that the first response time was 1.9 sec and then it took 30.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 30 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

faam.com.cn performance score

0

Network Requests Diagram

faam.com.cn

1893 ms

497 ms

reset.css

490 ms

style.css

724 ms

style_sjj.css

729 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 33% of them (22 requests) were addressed to the original Faam.com.cn, 50% (33 requests) were made to Faam.com.cn.hi.72la.com and 15% (10 requests) were made to V3.jiathis.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Faam.com.cn.hi.72la.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 419.4 kB (74%)

Content Size

568.5 kB

After Optimization

149.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Faam.com.cn main page is 568.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. 25% of websites need less resources to load. HTML takes 193.6 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 166.8 kB

  • Original 193.6 kB
  • After minification 185.6 kB
  • After compression 26.9 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 166.8 kB or 86% of the original size.

Image Optimization

-36%

Potential reduce by 24.4 kB

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

JavaScript Optimization

-67%

Potential reduce by 127.0 kB

  • Original 189.8 kB
  • After minification 166.8 kB
  • After compression 62.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 127.0 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 101.3 kB

  • Original 117.2 kB
  • After minification 99.3 kB
  • After compression 15.9 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. Faam.com.cn needs all CSS files to be minified and compressed as it can save up to 101.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (72%)

Requests Now

29

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

faam.com.cn

faam.com.cn

1893 ms

497 ms

reset.css

reset.css

490 ms

style.css

style.css

724 ms

style_sjj.css

style_sjj.css

729 ms

page.css

page.css

510 ms

jQuery.js

jQuery.js

1534 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

532 ms

prefixfree.min.js

prefixfree.min.js

707 ms

jquery.validate.js

jquery.validate.js

999 ms

jquery.cookie.min.js

jquery.cookie.min.js

808 ms

tools.js

tools.js

922 ms

template.min.js

template.min.js

943 ms

init.js

init.js

958 ms

jia.js

jia.js

4814 ms

main.js

main.js

838 ms

ban.js

ban.js

930 ms

marquee.js

marquee.js

950 ms

jquery.SuperSlide.2.1.1.js

jquery.SuperSlide.2.1.1.js

960 ms

reset.css

reset.css

1111 ms

style.css

style.css

1594 ms

style_sjj.css

style_sjj.css

1638 ms

page.css

page.css

1374 ms

tran.gif

tran.gif

9493 ms

logo.png

logo.png

19538 ms

size_03.png

size_03.png

14494 ms

img_09.jpg

img_09.jpg

20368 ms

img_10.jpg

img_10.jpg

20354 ms

img_11.jpg

img_11.jpg

20252 ms

img_12.jpg

img_12.jpg

20118 ms

img_13.jpg

img_13.jpg

20107 ms

size_04.png

size_04.png

19889 ms

1432017480240xz2.jpg

1432017480240xz2.jpg

19885 ms

foot.png

foot.png

19862 ms

foot_04.png

foot_04.png

19716 ms

foot_05.png

foot_05.png

19664 ms

jiathis_utility.html

jiathis_utility.html

36 ms

jiathis_share.css

jiathis_share.css

68 ms

plugin.client.js

plugin.client.js

60 ms

jiathis_counter.css

jiathis_counter.css

39 ms

shares.php

shares.php

4194 ms

jiathis_ico.png

jiathis_ico.png

88 ms

counter.gif

counter.gif

87 ms

bg_subbox.png

bg_subbox.png

19595 ms

head_04.png

head_04.png

19595 ms

head_02.png

head_02.png

19594 ms

banner1.jpg

banner1.jpg

19593 ms

banner2.jpg

banner2.jpg

19594 ms

banner3.jpg

banner3.jpg

20475 ms

jiathis_share.css

jiathis_share.css

293 ms

jiathis_counter.css

jiathis_counter.css

281 ms

index_bg01.jpg

index_bg01.jpg

19942 ms

icon.png

icon.png

19940 ms

img_14.png

img_14.png

19930 ms

index_bg02.jpg

index_bg02.jpg

19929 ms

img_15.png

img_15.png

19928 ms

jiathis_counter.css

jiathis_counter.css

295 ms

img_16.png

img_16.png

19639 ms

img_18.png

img_18.png

19602 ms

foot_06.png

foot_06.png

19601 ms

foot_07.png

foot_07.png

19577 ms

foot_08.png

foot_08.png

19575 ms

foot_02.png

foot_02.png

19572 ms

foot_01.png

foot_01.png

20455 ms

foot_03.png

foot_03.png

20076 ms

icon01.png

icon01.png

20192 ms

SEO Factors

faam.com.cn 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 Faam.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 Faam.com.cn 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

faam.com.cn

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