4.8 sec in total
1.3 sec
3.4 sec
166 ms
Click here to check amazing Potato Congress content. Otherwise, check out these important facts you probably never knew about potatocongress.org
Visit potatocongress.orgWe analyzed Potatocongress.org page load time and found that the first response time was 1.3 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
potatocongress.org performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value36.8 s
0/100
25%
Value20.1 s
0/100
10%
Value430 ms
64/100
30%
Value0.001
100/100
15%
Value33.4 s
0/100
10%
1280 ms
76 ms
148 ms
168 ms
191 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 86% of them (48 requests) were addressed to the original Potatocongress.org, 5% (3 requests) were made to S.ytimg.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Potatocongress.org.
Page size can be reduced by 620.6 kB (42%)
1.5 MB
860.4 kB
In fact, the total size of Potatocongress.org main page is 1.5 MB. 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. Images take 800.4 kB which makes up the majority of the site volume.
Potential reduce by 14.6 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 14.6 kB or 74% of the original size.
Potential reduce by 122.8 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, Potato Congress needs image optimization as it can save up to 122.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 254.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 254.3 kB or 67% of the original size.
Potential reduce by 228.8 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. Potatocongress.org needs all CSS files to be minified and compressed as it can save up to 228.8 kB or 82% of the original size.
Number of requests can be reduced by 23 (43%)
53
30
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potato Congress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.potatocongress.org
1280 ms
reset.css
76 ms
style.css
148 ms
nivo-slider.css
168 ms
tubepress.css
191 ms
style.css
146 ms
lightbox.min.css
139 ms
jquery.js
314 ms
jquery-migrate.min.js
211 ms
tubepress.js
246 ms
userscripts.js
211 ms
potato.js
239 ms
jquery.touchwipe.min.js
261 ms
jquery.lightbox.min.js
291 ms
wp-embed.min.js
287 ms
jquery.nivo.slider.pack.js
359 ms
bar.css
357 ms
dark.css
357 ms
default.css
358 ms
light.css
358 ms
wp-emoji-release.min.js
232 ms
world_bg.gif
431 ms
container_bg.gif
122 ms
header.jpg
222 ms
logo.jpg
147 ms
menu_bg.gif
121 ms
news.gif
122 ms
breaking_news.gif
220 ms
griffin.jpg
546 ms
AWSS%20Nivo%202015.jpg
422 ms
potatomagazine.jpg
479 ms
grimme.png
471 ms
IPM-master_sized.png
419 ms
homegrown_wisconsin_potatoes.jpg
482 ms
spud.jpg
503 ms
dewulf.jpg
550 ms
wada_farms.jpg
573 ms
foodpark.jpg
614 ms
cavendish_farms.jpg
568 ms
hzpc.jpg
592 ms
europlant_logo.jpg
673 ms
prince_edward_island.jpg
762 ms
united_potato_growers_of_america.jpg
647 ms
pei_potato_board.jpg
703 ms
cygnet_logo.jpg
658 ms
mccain.jpg
760 ms
086-300x231.jpg
718 ms
header_line.gif
733 ms
8mYuIYUHP_k
159 ms
www-embed-player-vflfNyN_r.css
24 ms
www-embed-player.js
39 ms
base.js
65 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
52 ms
ad_status.js
49 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
45 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
47 ms
potatocongress.org 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
potatocongress.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
potatocongress.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potatocongress.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Potatocongress.org 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.
potatocongress.org
Open Graph description is not detected on the main page of Potato Congress. 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: