4.9 sec in total
191 ms
3.4 sec
1.3 sec
Visit worldfertilizer.com now to see the best up-to-date World Fertilizer content for United States and also check out these interesting facts you probably never knew about worldfertilizer.com
The latest fertilizer news, industry trends and events from World Fertilizer magazine, including coverage of the potash, nitrogen and ammonia sectors.
Visit worldfertilizer.comWe analyzed Worldfertilizer.com page load time and found that the first response time was 191 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
worldfertilizer.com performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value3.7 s
58/100
25%
Value6.8 s
35/100
10%
Value1,590 ms
13/100
30%
Value0.647
9/100
15%
Value10.3 s
25/100
10%
191 ms
787 ms
108 ms
124 ms
136 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 8% of them (4 requests) were addressed to the original Worldfertilizer.com, 12% (6 requests) were made to Dfk1kem45npzu.cloudfront.net and 8% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Clarity.ms.
Page size can be reduced by 122.0 kB (31%)
395.2 kB
273.2 kB
In fact, the total size of Worldfertilizer.com main page is 395.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. 70% of websites need less resources to load. Javascripts take 171.8 kB which makes up the majority of the site volume.
Potential reduce by 56.4 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. This page needs HTML code to be minified as it can gain 26.4 kB, which is 40% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 56.4 kB or 85% of the original size.
Potential reduce by 1.2 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. World Fertilizer images are well optimized though.
Potential reduce by 61.0 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 61.0 kB or 35% of the original size.
Potential reduce by 3.4 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. Worldfertilizer.com needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 24% of the original size.
Number of requests can be reduced by 26 (62%)
42
16
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of World Fertilizer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
worldfertilizer.com
191 ms
www.worldfertilizer.com
787 ms
bootstrap.min.css
108 ms
font-awesome.min.css
124 ms
css
136 ms
site-d-01.min.css
101 ms
master.min.css
103 ms
js
228 ms
jquery.min.js
170 ms
modernizr.custom.js
217 ms
bootstrap.min.js
117 ms
jquery.placeholder.min.js
204 ms
main.desktop.min.js
364 ms
cookieconsent.min.css
211 ms
cookieconsent.min.js
358 ms
fbevents.js
462 ms
gpt.js
456 ms
logo.png
220 ms
cse.js
560 ms
free.png
220 ms
social.png
201 ms
analytics.js
363 ms
bat.js
473 ms
S6uyw4BMUTPHjx4wWA.woff
358 ms
S6u9w4BMUTPHh6UVSwiPHw.woff
390 ms
fontawesome-webfont.woff
242 ms
vEFO2_JTCgwQ5ejvMV0O96D01E8J0tKwG6bBjMg.woff
410 ms
vEFO2_JTCgwQ5ejvMV0O96D01E8J0tJXHKbBjMg.woff
408 ms
fertilizer-02.jpg
56 ms
top-story.png
53 ms
brazil-02.jpg
139 ms
phosphate-mine-03.jpg
159 ms
canada-04.jpg
608 ms
collect
129 ms
pubads_impl_2022100301.js
201 ms
ppub_config
534 ms
778510952260052
57 ms
5667067.js
110 ms
cse_element__en.js
669 ms
default+en.css
778 ms
default.css
795 ms
collect
790 ms
5667067
1340 ms
integrator.js
934 ms
ads
266 ms
container.html
904 ms
ga-audiences
645 ms
rx_lidar.js
237 ms
clarity.js
146 ms
worldfertilizer.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
worldfertilizer.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
worldfertilizer.com SEO score
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 Worldfertilizer.com 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 Worldfertilizer.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.
worldfertilizer.com
Open Graph data is detected on the main page of World Fertilizer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: