Yara.us Site Title

Welcome to Yara US - Crop Nutrition, Chemical and Environmental Solutions

Yara.us Meta Description

Our mission is to responsibly feed the world and protect the planet, to deliver profitable and responsible solutions for agriculture and the environment supporting farmer profitability through knowledge, quality and productivity.

Yara.us Test Results

Yara.us Mobile Performance: 42/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Avoid multiple page redirects. Potential savings of 1,260 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused JavaScript. Potential savings of 296 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Remove unused CSS. Potential savings of 116 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 780 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Reduce initial server response time. Root document took 1,110 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Serve static assets with an efficient cache policy
29 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
2.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Avoid an excessive DOM size
1,036 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Reduce JavaScript execution time
1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid long main-thread tasks
11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
67 requests • 957 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
10 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More

Yara.us Mobile SEO: 92/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
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.
Tap targets are not sized appropriately
92% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Yara.us Mobile Best Practices: 77/100
Quick overview:
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Includes front-end JavaScript libraries with known security vulnerabilities
6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Yara.us Mobile Progressive Web App: 25/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Fast and reliable
Page load is not fast enough on mobile networks
Interactive at 11.1 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Installable
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Yara.us Mobile Accessibility: 100/100
Quick overview:
Similar sites
Similar tests
www.yara.com
www.yara.net
www.yara.org
www.yara.info
www.yara.biz
www.yara.us
www.yara.mobi
www.ara.us
www.yara.us
www.tara.us
www.ytara.us
www.tyara.us
www.gara.us
www.ygara.us
www.gyara.us
www.hara.us
www.yhara.us
www.hyara.us
www.uara.us
www.yuara.us
www.uyara.us
www.yra.us
www.yqra.us
www.yaqra.us
www.yqara.us
www.ywra.us
www.yawra.us
www.ywara.us
www.ysra.us
www.yasra.us
www.ysara.us
www.yzra.us
www.yazra.us
www.yzara.us
www.yaa.us
www.yaea.us
www.yarea.us
www.yaera.us
www.yada.us
www.yarda.us
www.yadra.us
www.yafa.us
www.yarfa.us
www.yafra.us
www.yata.us
www.yarta.us
www.yatra.us
www.yar.us
www.yarq.us
www.yaraq.us
www.yarqa.us
www.yarw.us
www.yaraw.us
www.yarwa.us
www.yars.us
www.yaras.us
www.yarsa.us
www.yarz.us
www.yaraz.us
www.yarza.us
Last Tested: