1.7 sec in total
221 ms
1.3 sec
255 ms
Welcome to potfarm.info homepage info - get ready to check Potfarm best content for United States right away, or after learning these important things about potfarm.info
http://potfarm.info - Complete archive of the first 5 years of Pot Farm. Search stuff by name, contraptions and repeaters by output, and more!
Visit potfarm.infoWe analyzed Potfarm.info page load time and found that the first response time was 221 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
potfarm.info performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value15.4 s
0/100
25%
Value8.2 s
20/100
10%
Value2,580 ms
4/100
30%
Value0.235
53/100
15%
Value21.9 s
1/100
10%
221 ms
97 ms
36 ms
4 ms
10 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 10% of them (9 requests) were addressed to the original Potfarm.info, 13% (12 requests) were made to Fls-na.amazon-adsystem.com and 11% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (379 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 103.9 kB (22%)
475.7 kB
371.8 kB
In fact, the total size of Potfarm.info main page is 475.7 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. 70% of websites need less resources to load. Javascripts take 259.1 kB which makes up the majority of the site volume.
Potential reduce by 66.8 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 66.8 kB or 79% of the original size.
Potential reduce by 1.9 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. Potfarm images are well optimized though.
Potential reduce by 22.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 12.5 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. Potfarm.info needs all CSS files to be minified and compressed as it can save up to 12.5 kB or 65% of the original size.
Number of requests can be reduced by 59 (66%)
89
30
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potfarm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
potfarm.info
221 ms
css.css
97 ms
jquery.min.js
36 ms
adsbygoogle.js
4 ms
q
10 ms
jquery.js
81 ms
jquery.floatThead.min.js
188 ms
ga.js
141 ms
sdk.js
140 ms
json
121 ms
cm
122 ms
ir
122 ms
element.js
132 ms
q
124 ms
cse.js
123 ms
json
107 ms
ir
106 ms
pfi_wurds.png
237 ms
indicator.gif
163 ms
pfm2015.png
292 ms
ca-pub-0327860048446267.js
135 ms
zrt_lookup.html
208 ms
show_ads_impl.js
129 ms
plusone.js
319 ms
mantodea.min.js
189 ms
echo_associate_300x250_final_v2.jpg
153 ms
126 ms
a-logo-amazon.png
149 ms
json
134 ms
ir
65 ms
61SNzXi8d6L._AC_SR98,95_.jpg
144 ms
cart.gif
146 ms
cse.js
250 ms
__utm.gif
86 ms
translateelement.css
213 ms
main.js
239 ms
ads
360 ms
106 ms
osd.js
21 ms
xd_arbiter.php
111 ms
xd_arbiter.php
166 ms
ads
281 ms
ads
251 ms
ads
245 ms
ads
379 ms
jsapi
77 ms
cb=gapi.loaded_0
35 ms
cb=gapi.loaded_1
59 ms
fastbutton
174 ms
element_main.js
49 ms
default+en.css
66 ms
default.css
120 ms
default+en.I.js
136 ms
postmessageRelay
230 ms
translate_24dp.png
227 ms
l
103 ms
cleardot.gif
68 ms
cpm_728x90.php
148 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
35 ms
cpm_728x90.php
133 ms
default.css
51 ms
abg.js
133 ms
cpm_728x90.php
128 ms
m_js_controller.js
131 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
167 ms
async-ads.js
141 ms
google_custom_search_watermark.gif
76 ms
small-logo.png
68 ms
clear.gif
68 ms
nav_logo114.png
40 ms
te_ctrl3.gif
65 ms
api.js
59 ms
core:rpc:shindig.random:shindig.sha1.js
131 ms
2536007149-postmessagerelay.js
102 ms
getads.js
50 ms
s
55 ms
googlelogo_color_112x36dp.png
48 ms
nessie_icon_tiamat_white.png
48 ms
x_button_blue2.png
48 ms
getad
89 ms
getad
85 ms
getad
72 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
3 ms
json
18 ms
cm
21 ms
json
17 ms
json
9 ms
json
9 ms
json
8 ms
json
9 ms
VXD168-evergreenAssociateAds-lifestyle-assoc-728x90
11 ms
6 ms
7 ms
potfarm.info accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
potfarm.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
potfarm.info SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potfarm.info 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), while the claimed language is English. Our system also found out that Potfarm.info 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.
potfarm.info
Open Graph data is detected on the main page of Potfarm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: