Tools & Wizards About Us
potteryfish.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

potteryfish.com

股票網站-股票投資分析

Page Load Speed

3.5 sec in total

First Response

310 ms

Resources Loaded

3 sec

Page Rendered

247 ms

potteryfish.com screenshot

About Website

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

股票網站-股票投資分析

Visit potteryfish.com

Key Findings

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

potteryfish.com performance score

0

Network Requests Diagram

potteryfish.com

310 ms

stock-blog2.css

116 ms

addthis_widget.js

9 ms

post_02.gif

1129 ms

addblackcolor_8015.gif

570 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 15% of them (6 requests) were addressed to the original Potteryfish.com, 21% (8 requests) were made to Apis.google.com and 8% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cacafly.com.

Page Optimization Overview & Recommendations

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

Content Size

529.3 kB

After Optimization

196.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Potteryfish.com main page is 529.3 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. 45% of websites need less resources to load. Javascripts take 444.3 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 56.6 kB

  • Original 81.7 kB
  • After minification 81.4 kB
  • After compression 25.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 56.6 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.3 kB
  • After minification 1.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. Potteryfish images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 274.9 kB

  • Original 444.3 kB
  • After minification 444.3 kB
  • After compression 169.4 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 274.9 kB or 62% of the original size.

CSS Optimization

-71%

Potential reduce by 1.4 kB

  • Original 2.0 kB
  • After minification 1.6 kB
  • After compression 583 B

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. Potteryfish.com needs all CSS files to be minified and compressed as it can save up to 1.4 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (45%)

Requests Now

31

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

potteryfish.com

potteryfish.com

310 ms

stock-blog2.css

stock-blog2.css

116 ms

addthis_widget.js

addthis_widget.js

9 ms

post_02.gif

post_02.gif

1129 ms

addblackcolor_8015.gif

addblackcolor_8015.gif

570 ms

ga.js

ga.js

6 ms

img13.gif

img13.gif

201 ms

rss.gif

rss.gif

200 ms

img03.gif

img03.gif

201 ms

img08.gif

img08.gif

202 ms

300lo.json

300lo.json

79 ms

all.js&version=v2.0

all.js&version=v2.0

183 ms

widgets.js

widgets.js

179 ms

plusone.js

plusone.js

120 ms

counter.5524cceca805eb4b9b2b.js

counter.5524cceca805eb4b9b2b.js

89 ms

__utm.gif

__utm.gif

89 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

81 ms

shares.json

shares.json

107 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

107 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

93 ms

fastbutton

fastbutton

196 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

251 ms

233 ms

xd_arbiter.php

xd_arbiter.php

111 ms

xd_arbiter.php

xd_arbiter.php

160 ms

postmessageRelay

postmessageRelay

130 ms

404.html

404.html

439 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

68 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

68 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

94 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

33 ms

rpc:shindig_random.js

rpc:shindig_random.js

35 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

64 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

jot

jot

92 ms

cacafly.com

cacafly.com

1282 ms

ping

ping

59 ms

like.php

like.php

114 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

35 ms

SEO Factors

potteryfish.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 Potteryfish.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 Potteryfish.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

potteryfish.com

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