2 sec in total
99 ms
1.8 sec
71 ms
Welcome to hortisulrs.com homepage info - get ready to check Hortisul Rs best content for Brazil right away, or after learning these important things about hortisulrs.com
Somos fabricantes de perfis hidropônicos com tampa, de estufas agrícolas, de fertilizantes hidropônicos e de uma linha de sementes específicas para hidroponia.
Visit hortisulrs.comWe analyzed Hortisulrs.com page load time and found that the first response time was 99 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
hortisulrs.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value12.4 s
0/100
25%
Value7.3 s
28/100
10%
Value1,420 ms
15/100
30%
Value0.022
100/100
15%
Value22.0 s
1/100
10%
99 ms
56 ms
56 ms
883 ms
91 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hortisulrs.com, 38% (17 requests) were made to Static.parastorage.com and 27% (12 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (883 ms) relates to the external source Polyfill-fastly.io.
Page size can be reduced by 677.1 kB (58%)
1.2 MB
490.8 kB
In fact, the total size of Hortisulrs.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. 45% of websites need less resources to load. HTML takes 608.0 kB which makes up the majority of the site volume.
Potential reduce by 474.3 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 474.3 kB or 78% of the original size.
Potential reduce by 6.0 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. Hortisul Rs images are well optimized though.
Potential reduce by 196.9 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 196.9 kB or 44% of the original size.
Number of requests can be reduced by 11 (39%)
28
17
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hortisul Rs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
www.hortisulrs.com
99 ms
minified.js
56 ms
focus-within-polyfill.js
56 ms
polyfill.min.js
883 ms
thunderbolt-commons.d1a46914.bundle.min.js
91 ms
main.e312dfc9.bundle.min.js
94 ms
main.renderer.1d21f023.bundle.min.js
89 ms
lodash.min.js
92 ms
react.production.min.js
90 ms
react-dom.production.min.js
92 ms
siteTags.bundle.min.js
90 ms
wix-perf-measure.umd.min.js
92 ms
8fa4e4_caae2bf20c144cf88f89548861f98b0f.png
356 ms
8fa4e4_610642508ba24524a6b64275a4ae4aed~mv2.png
357 ms
8fa4e4_b1167c581115493182eb5fa67856dfa7~mv2.jpg
510 ms
8fa4e4_f6f40e0dcf4d46a78f9055eaf8a4bd91~mv2.jpg
337 ms
8fa4e4_76ac8b7222164bf082b0b98a7074167c~mv2.jpg
365 ms
8fa4e4_596f9a97fd0548719a58e493dc173f12~mv2.jpg
302 ms
8fa4e4_59ecc901698c478cbf1f8f695a3b30a2~mv2.jpg
528 ms
8fa4e4_4bff88cb6da3413f83ccec09198825bb.png
563 ms
8fa4e4_d9a450c315974a2488891e3eaa9e74f0~mv2.jpg
534 ms
8fa4e4_610642508ba24524a6b64275a4ae4aed~mv2.png
479 ms
8fa4e4_8bfac57ec72341d9a3eec0c8b6fa756b.png
589 ms
8fa4e4_84f48f28f46f4e61afc18e6a085fb4ad.png
685 ms
bundle.min.js
66 ms
efbfc170-aaf0-4472-91f4-dbb5bc2f4c59.woff
6 ms
120 ms
118 ms
113 ms
114 ms
110 ms
105 ms
151 ms
144 ms
142 ms
138 ms
142 ms
139 ms
deprecation-pt.v5.html
5 ms
bolt-performance
27 ms
deprecation-style.v5.css
6 ms
right-arrow.svg
21 ms
WixMadeforDisplay_W_Bd.woff
3 ms
WixMadeforText_W_Bd.woff
6 ms
WixMadeforText_W_Rg.woff
6 ms
hortisulrs.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
hortisulrs.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hortisulrs.com SEO score
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hortisulrs.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Hortisulrs.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.
hortisulrs.com
Open Graph data is detected on the main page of Hortisul Rs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: