2.6 sec in total
150 ms
2.2 sec
271 ms
Visit hortipro.com now to see the best up-to-date Hortipro content and also check out these interesting facts you probably never knew about hortipro.com
Feromonen, Gewashbescherming, Hulpstffen... HortiPro provides horticulture products.
Visit hortipro.comWe analyzed Hortipro.com page load time and found that the first response time was 150 ms and then it took 2.5 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.
hortipro.com performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value6.8 s
7/100
25%
Value5.9 s
47/100
10%
Value1,010 ms
27/100
30%
Value0.003
100/100
15%
Value8.8 s
35/100
10%
150 ms
117 ms
134 ms
148 ms
148 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Hortipro.com, 70% (28 requests) were made to Static.parastorage.com and 15% (6 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (833 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.0 MB (76%)
2.6 MB
625.6 kB
In fact, the total size of Hortipro.com main page is 2.6 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. 75% 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. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 94.5 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 94.5 kB or 83% of the original size.
Potential reduce by 1.9 MB
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 1.9 MB or 76% of the original size.
Potential reduce by 5.8 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. Hortipro.com needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.
Number of requests can be reduced by 32 (84%)
38
6
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hortipro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
hortipro.com
150 ms
www.hortipro.net
117 ms
bt
134 ms
require.min.js
148 ms
main-r.min.js
148 ms
viewer.css
283 ms
ugc-viewer
84 ms
dynamicmodel
75 ms
b76944_9e2fb34b2791fa3a6994c96d20de8a50_274.json.z
833 ms
b76944_66a7ac5b1b61dfb7ecafadd8edb7d552_271.json.z
826 ms
ugc-viewer
199 ms
bt
189 ms
skins.min.js
186 ms
components.min.js
45 ms
utils.min.js
175 ms
core.min.js
169 ms
react-with-addons.min.js
167 ms
lodash.min.js
169 ms
TweenMax.min.js
169 ms
layout.min.js
190 ms
tpa.min.js
188 ms
fonts.min.js
184 ms
animations.min.js
182 ms
swfobject.min.js
182 ms
mousetrap.min.js
170 ms
tweenEngine.min.js
183 ms
DrawSVGPlugin.min.js
185 ms
react-dom.min.js
185 ms
ScrollToPlugin.min.js
185 ms
widgets.min.js
186 ms
experiment.js
187 ms
render.min.js
180 ms
wixappsCore.min.js
766 ms
wixappsBuilder.min.js
765 ms
zepto.min.js
758 ms
color.min.js
173 ms
react-dom-server.min.js
621 ms
bt
304 ms
dc.js
276 ms
bt
116 ms
hortipro.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
hortipro.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
Page has valid source maps
hortipro.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hortipro.com can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 Hortipro.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.
hortipro.com
Open Graph description is not detected on the main page of Hortipro. 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: