2.6 sec in total
226 ms
2.2 sec
158 ms
Welcome to potashcorp.com homepage info - get ready to check Potashcorp best content for United States right away, or after learning these important things about potashcorp.com
As the world’s largest provider of crop inputs, services and solutions, Nutrien helps growers to increase food production in a sustainable manner.
Visit potashcorp.comWe analyzed Potashcorp.com page load time and found that the first response time was 226 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
potashcorp.com performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value8.5 s
1/100
25%
Value4.9 s
64/100
10%
Value410 ms
67/100
30%
Value0.142
78/100
15%
Value9.7 s
28/100
10%
226 ms
361 ms
88 ms
146 ms
155 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 73% of them (51 requests) were addressed to the original Potashcorp.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Wd-edge.sharethis.com. The less responsive or slowest element that took the longest time to load (776 ms) belongs to the original domain Potashcorp.com.
Page size can be reduced by 730.5 kB (41%)
1.8 MB
1.0 MB
In fact, the total size of Potashcorp.com main page is 1.8 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. 40% of websites need less resources to load. Javascripts take 840.6 kB which makes up the majority of the site volume.
Potential reduce by 25.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 25.8 kB or 82% of the original size.
Potential reduce by 26.7 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. Potashcorp images are well optimized though.
Potential reduce by 609.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 609.8 kB or 73% of the original size.
Potential reduce by 68.2 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. Potashcorp.com needs all CSS files to be minified and compressed as it can save up to 68.2 kB or 76% of the original size.
Number of requests can be reduced by 45 (68%)
66
21
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potashcorp. 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 from 19 to 1 for CSS and as a result speed up the page load time.
potashcorp.com
226 ms
www.potashcorp.com
361 ms
reset-fonts-grids.css
88 ms
core.css
146 ms
font-awesome.min.css
155 ms
quickconcat.php
175 ms
mobile.css
186 ms
menu.css
207 ms
menu_skin-main.css
205 ms
widget-togglebox.css
217 ms
rotating_banner.css
230 ms
news.css
259 ms
promo.css
276 ms
buttons.js
7 ms
sharethis.js
302 ms
yui-page-combo.js
662 ms
jquery.min.js
358 ms
modernizr-custom.js
304 ms
widget-togglebox.js
343 ms
rotating_banner.js
367 ms
pot_tools.js
402 ms
common.js
380 ms
quickconcat.php
429 ms
menu.js
427 ms
search.js
458 ms
dashed_seperator.png
124 ms
pot_logo.png
124 ms
button__search.png
126 ms
sprite__icons.png
124 ms
nav__submenu_arrow.png
122 ms
sprite__nav_tools.png
125 ms
fontawesome-webfont.woff
340 ms
IRC2016_homepromo1.jpg
552 ms
icon__mobile.png
162 ms
home_brownlee_clr.jpg
466 ms
Tilk_hmpromo_conf_clr%20(4).jpg
335 ms
leaf_homepage.jpg
776 ms
button_bg.png
224 ms
We_day_promo2.jpg
489 ms
small_promo_Stewart_1.jpg
403 ms
fieldreports_sp16_smpromo.jpg
427 ms
skin__homepage_feature_corner.png
486 ms
analytics.js
77 ms
getAllAppDefault.esi
60 ms
combo
51 ms
niceforms-default.css
379 ms
library_calendar.css
416 ms
loading.gif
404 ms
fancybox_overlay.png
425 ms
sprite__icons_new_utility.png
472 ms
lightbox_close_default.png
471 ms
library.css
473 ms
calendar.css
503 ms
tabs.css
510 ms
combo
23 ms
collect
21 ms
getSegment.php
156 ms
checkOAuth.esi
15 ms
t.dhj
34 ms
t.dhj
25 ms
cm
37 ms
s-3271.xgi
18 ms
16 ms
hbpix
35 ms
pixel
23 ms
7 ms
52154.gif
8 ms
pixel
17 ms
2981
30 ms
quickconcat.php
89 ms
potashcorp.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
potashcorp.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
potashcorp.com 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potashcorp.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Potashcorp.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.
potashcorp.com
Open Graph description is not detected on the main page of Potashcorp. 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: