6 sec in total
527 ms
5 sec
438 ms
Welcome to oasisgrowersolutions.com homepage info - get ready to check Oasis Grower Solutions best content right away, or after learning these important things about oasisgrowersolutions.com
In our Oasis® Grower solutions website you can find all the products, fact sheets, and learn how to become a better grower.
Visit oasisgrowersolutions.comWe analyzed Oasisgrowersolutions.com page load time and found that the first response time was 527 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
oasisgrowersolutions.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value11.8 s
0/100
25%
Value16.1 s
0/100
10%
Value11,330 ms
0/100
30%
Value0.33
34/100
15%
Value20.8 s
2/100
10%
527 ms
2071 ms
86 ms
77 ms
93 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 87% of them (91 requests) were addressed to the original Oasisgrowersolutions.com, 9% (9 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Oasisgrowersolutions.com.
Page size can be reduced by 218.8 kB (18%)
1.2 MB
986.2 kB
In fact, the total size of Oasisgrowersolutions.com main page is 1.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 586.0 kB which makes up the majority of the site volume.
Potential reduce by 212.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. 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 212.4 kB or 87% of the original size.
Potential reduce by 3.6 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. Oasis Grower Solutions images are well optimized though.
Potential reduce by 637 B
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 2.1 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. Oasisgrowersolutions.com has all CSS files already compressed.
Number of requests can be reduced by 78 (86%)
91
13
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oasis Grower Solutions. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
oasisgrowersolutions.com
527 ms
www.oasisgrowersolutions.com
2071 ms
wp-emoji-release.min.js
86 ms
style.min.css
77 ms
frontend-legacy.min.css
93 ms
frontend.min.css
127 ms
general.min.css
144 ms
eael-799.css
135 ms
style.css
134 ms
css
185 ms
style.min.css
136 ms
frontend.css
142 ms
style.min.css
171 ms
style.min.css
157 ms
astra-addon-631a1e8777a755-37873635.css
168 ms
all.min.css
144 ms
v4-shims.min.css
438 ms
public.css
149 ms
jet-elements.css
175 ms
jet-elements-skin.css
271 ms
elementor-icons.min.css
168 ms
post-699.css
197 ms
frontend.min.css
198 ms
uael-frontend.min.css
286 ms
post-8953.css
340 ms
post-799.css
338 ms
post-365.css
281 ms
style.css
272 ms
chosen.min.css
341 ms
jet-search.css
343 ms
css
360 ms
fontawesome.min.css
334 ms
solid.min.css
341 ms
brands.min.css
343 ms
jquery.min.js
346 ms
jquery-migrate.min.js
489 ms
imagesloaded.min.js
363 ms
script.min.js
375 ms
js
372 ms
email-decode.min.js
355 ms
post-1775.css
360 ms
eael-1601.css
461 ms
post-1601.css
340 ms
post-466.css
354 ms
all.min.css
301 ms
v4-shims.min.css
304 ms
animations.min.css
299 ms
general.min.js
295 ms
eael-799.js
292 ms
script.js
284 ms
style.min.js
278 ms
underscore.min.js
277 ms
wp-util.min.js
274 ms
chosen.jquery.min.js
274 ms
jet-search.js
277 ms
dynamic-conditions-public.js
236 ms
astra-addon-631a1e8777ee39-36058406.js
236 ms
vue.min.js
233 ms
jet-menu-public-scripts.js
232 ms
eael-1601.js
231 ms
v4-shims.min.js
221 ms
jquery.smartmenus.min.js
167 ms
webpack-pro.runtime.min.js
166 ms
webpack.runtime.min.js
165 ms
frontend-modules.min.js
396 ms
regenerator-runtime.min.js
390 ms
wp-polyfill.min.js
385 ms
hooks.min.js
382 ms
i18n.min.js
382 ms
frontend.min.js
380 ms
waypoints.min.js
387 ms
core.min.js
383 ms
swiper.min.js
380 ms
share-link.min.js
378 ms
dialog.min.js
375 ms
frontend.min.js
361 ms
preloaded-elements-handlers.min.js
360 ms
jet-elements.min.js
361 ms
widgets-scripts.js
358 ms
preloaded-modules.min.js
359 ms
jquery.sticky.min.js
358 ms
oasis-grower-solutions.svg
191 ms
en.png
188 ms
es.png
189 ms
it.png
188 ms
br.png
213 ms
mexico.png
189 ms
oasis-grower-solutions-fortify.png
215 ms
1000x1000_Hemp-pichi@1x.jpg
209 ms
1000x1000_Hibiscus-pichi@1x.jpg
339 ms
1000x1000_Peppers-pichi@1x.jpg
206 ms
analytics.js
1040 ms
-W__XJnvUD7dzB2KYNoY.ttf
1041 ms
-W_8XJnvUD7dzB2Ck_kIaWMr.ttf
1191 ms
-W_8XJnvUD7dzB2Cy_gIaWMr.ttf
1192 ms
-W_8XJnvUD7dzB2Cr_sIaWMr.ttf
1236 ms
-W_9XJnvUD7dzB2CA-ofTkM.ttf
1239 ms
-W_8XJnvUD7dzB2Cv_4IaWMr.ttf
1240 ms
-W_8XJnvUD7dzB2C2_8IaWMr.ttf
1239 ms
-W_8XJnvUD7dzB2Cx_wIaWMr.ttf
1237 ms
-W_8XJnvUD7dzB2C4_0IaWMr.ttf
1235 ms
fa-solid-900.woff
1037 ms
fa-solid-900.woff
643 ms
fa-regular-400.woff
641 ms
collect
124 ms
oasisgrowersolutions.com 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
Links do not have a discernible name
oasisgrowersolutions.com 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
oasisgrowersolutions.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a valid hreflang
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 Oasisgrowersolutions.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 Oasisgrowersolutions.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.
oasisgrowersolutions.com
Open Graph data is detected on the main page of Oasis Grower Solutions. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: