Tools & Wizards About Us
fonepedia.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fonepedia.com

华体汇体育直播_唯一官方地址

Page Load Speed

4.8 sec in total

First Response

1.9 sec

Resources Loaded

2.6 sec

Page Rendered

224 ms

fonepedia.com screenshot

About Website

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

中国陶瓷网是陶瓷行业门户网站，提供陶瓷、瓷砖、卫浴、原料设备等企业供求商机发布的电子商务平台，举办陶瓷十大品牌、陶瓷展会和陶瓷卫浴优秀经销商评选等活动，长期致力于服务佛山、山东、江西、福建等大型陶瓷产区，为终端经销商和消费者提供陶瓷卫浴行业一手资讯。现在，中国陶瓷网已成为我国陶瓷行业中专业、丰富、具特色的陶瓷信息资讯网站。

Visit fonepedia.com

Key Findings

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

Performance Metrics

fonepedia.com performance score

0

Network Requests Diagram

fonepedia.com

1949 ms

fonepedia.css

63 ms

toplogo.png

108 ms

search.png

94 ms

fonepedialist.css

22 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 91% of them (50 requests) were addressed to the original Fonepedia.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to S07.flagcounter.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fonepedia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.6 kB (16%)

Content Size

427.2 kB

After Optimization

357.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fonepedia.com main page is 427.2 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. Images take 353.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 16.6 kB

  • Original 20.7 kB
  • After minification 20.5 kB
  • After compression 4.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 16.6 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 28.8 kB

  • Original 353.1 kB
  • After minification 324.3 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. Fonepedia images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 14.0 kB

  • Original 40.3 kB
  • After minification 40.3 kB
  • After compression 26.3 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 14.0 kB or 35% of the original size.

CSS Optimization

-78%

Potential reduce by 10.2 kB

  • Original 13.1 kB
  • After minification 11.1 kB
  • After compression 2.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. Fonepedia.com needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

54

After Optimization

54

  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fonepedia. According to our analytics all requests are already optimized.

Network Requests Diagram

fonepedia.com

fonepedia.com

1949 ms

fonepedia.css

fonepedia.css

63 ms

toplogo.png

toplogo.png

108 ms

search.png

search.png

94 ms

fonepedialist.css

fonepedialist.css

22 ms

cmenu.css

cmenu.css

90 ms

bgp06.gif

bgp06.gif

33 ms

icon-fb.png

icon-fb.png

34 ms

icon-twitter.png

icon-twitter.png

34 ms

icon-rss.png

icon-rss.png

54 ms

nokia.png

nokia.png

119 ms

samsung.png

samsung.png

95 ms

sony-ericsson.png

sony-ericsson.png

127 ms

apple.png

apple.png

92 ms

lg.png

lg.png

97 ms

motorola.png

motorola.png

139 ms

toshiba.png

toshiba.png

136 ms

blackberry.png

blackberry.png

153 ms

dell.png

dell.png

170 ms

hp.png

hp.png

157 ms

964824990670880_thumb.png

964824990670880_thumb.png

393 ms

498032034859312_thumb.png

498032034859312_thumb.png

372 ms

496589353741713_thumb.png

496589353741713_thumb.png

350 ms

212211929519711_thumb.png

212211929519711_thumb.png

351 ms

418573098213287_thumb.png

418573098213287_thumb.png

366 ms

107474293041665_thumb.png

107474293041665_thumb.png

408 ms

306846626900097_thumb.png

306846626900097_thumb.png

455 ms

902104667475906_thumb.png

902104667475906_thumb.png

483 ms

762404182690116_thumb.png

762404182690116_thumb.png

495 ms

420896749867755_thumb.png

420896749867755_thumb.png

519 ms

871837307089548_thumb.png

871837307089548_thumb.png

572 ms

791895090070398_thumb.png

791895090070398_thumb.png

566 ms

234787118735726_thumb.png

234787118735726_thumb.png

609 ms

385016756737565_thumb.png

385016756737565_thumb.png

646 ms

646462901515412_thumb.png

646462901515412_thumb.png

698 ms

589094414042390_thumb.png

589094414042390_thumb.png

744 ms

692583923131911_thumb.png

692583923131911_thumb.png

773 ms

832300841018380_thumb.png

832300841018380_thumb.png

787 ms

852517466295141_thumb.png

852517466295141_thumb.png

790 ms

532660748932617_thumb.png

532660748932617_thumb.png

813 ms

086309031674461_thumb.png

086309031674461_thumb.png

864 ms

252738346859321_thumb.png

252738346859321_thumb.png

883 ms

255183593978116_thumb.png

255183593978116_thumb.png

924 ms

566064032592614_thumb.png

566064032592614_thumb.png

913 ms

657835811615413_thumb.png

657835811615413_thumb.png

1027 ms

107732519404796_thumb.png

107732519404796_thumb.png

895 ms

226 ms

100515716108884_thumb.png

100515716108884_thumb.png

603 ms

499315365110865_thumb.png

499315365110865_thumb.png

647 ms

554611687837998_thumb.png

554611687837998_thumb.png

682 ms

505735159984843_thumb.png

505735159984843_thumb.png

628 ms

ga.js

ga.js

13 ms

quant.js

quant.js

8 ms

pixel;r=683734929;a=p-bdDGwRlElRYUY;fpan=1;fpa=P0-1595080050-1458476306256;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458476306255;tzo=-180;ref=;url=http%3A%2F%2Ffonepedia.com%2F;ogl=

pixel;r=683734929;a=p-bdDGwRlElRYUY;fpan=1;fpa=P0-1595080050-1458476306256;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458476306255;tzo=-180;ref=;url=http%3A%2F%2Ffonepedia.com%2F;ogl=

35 ms

__utm.gif

__utm.gif

18 ms

SEO Factors

fonepedia.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fonepedia.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fonepedia.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

fonepedia.com

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