4.1 sec in total
26 ms
3.2 sec
892 ms
Click here to check amazing Hort Plus content. Otherwise, check out these important facts you probably never knew about hortplus.com
At HortPlus we build digital decision support platforms for agriculture, horticulture, and other primary-sector industries.
Visit hortplus.comWe analyzed Hortplus.com page load time and found that the first response time was 26 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
hortplus.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value3.8 s
55/100
25%
Value7.4 s
27/100
10%
Value120 ms
97/100
30%
Value0.068
96/100
15%
Value13.6 s
11/100
10%
26 ms
78 ms
57 ms
66 ms
225 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 50% of them (46 requests) were addressed to the original Hortplus.com, 32% (29 requests) were made to Hortplus-assets.s3-ap-southeast-2.amazonaws.com and 14% (13 requests) were made to Aus-widget.freshworks.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Hortplus-assets.s3-ap-southeast-2.amazonaws.com.
Page size can be reduced by 291.6 kB (8%)
3.7 MB
3.4 MB
In fact, the total size of Hortplus.com main page is 3.7 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. 60% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 194.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 194.3 kB or 73% of the original size.
Potential reduce by 94.7 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. Hort Plus images are well optimized though.
Potential reduce by 2.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 101 B
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. Hortplus.com has all CSS files already compressed.
Number of requests can be reduced by 34 (38%)
89
55
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hort Plus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and as a result speed up the page load time.
hortplus.com
26 ms
www.hortplus.com
78 ms
freshwidget.js
57 ms
js
66 ms
polyfill-01af7bb6dd4d0eb52665.js
225 ms
component---src-pages-index-jsx-1f4b93d96ccbd89585a0.js
229 ms
d4f28fed4b32bd5e631ca76a267c41336bf87116-1ce5cec75c098196a8c7.js
229 ms
ce547dc6d67f41c733cc4d699cf6f41da64ed268-0acfa3313f5d653ca746.js
228 ms
0e86cf399de6a0723e40dd37777762f2ff2c9229-45f89c7bda28500eea77.js
232 ms
framework-6dc75a31a18668b93c59.js
294 ms
styles-407fe62976dc5310c43e.js
229 ms
app-dc5b8363630dd332166b.js
435 ms
cb1608f2-9fdf42141825f2af37db.js
434 ms
webpack-runtime-8b97e87d47e269f0ebb4.js
439 ms
freshwidget.css
47 ms
header_logo.svg
852 ms
weather_machine.png
1899 ms
nz_apples_and_pears.png
1053 ms
summerfruit_nz.png
852 ms
onions_nz.png
881 ms
fruitfed_supplies.png
869 ms
far.png
1093 ms
watties.png
1298 ms
a_lighter_touch.png
1092 ms
VegetablesNZ_logo-cropped.png
1325 ms
fruitionhort-green.svg
1296 ms
nzppi_logo.svg
1340 ms
swnz_logo.jpg
1776 ms
zespri.png
1515 ms
plant_and_food_research.png
1510 ms
kvh.png
1571 ms
woman_spinach.jpg
2210 ms
plant_and_food_research_office.jpg
2197 ms
agritech-logo.svg
1731 ms
notification.png
2041 ms
iphone_metwatch_app.png
2601 ms
the_weather_company.png
2039 ms
metservice2.png
2137 ms
aus_gov.png
2278 ms
green_weather_station_icon.svg
2260 ms
blue_integrate_icon.svg
2381 ms
logo.svg
2445 ms
weather_machine.svg
2394 ms
nz_hills.jpg
2697 ms
poppins-all-400-normal-2b7b1aec0bbda049675f582f71d6d9a3.woff
257 ms
app-data.json
8 ms
page-data.json
216 ms
bootstrap.js
5 ms
image1.png
272 ms
js
100 ms
page-data.json
210 ms
page-data.json
213 ms
page-data.json
255 ms
page-data.json
18 ms
page-data.json
210 ms
page-data.json
214 ms
page-data.json
816 ms
page-data.json
215 ms
page-data.json
221 ms
page-data.json
425 ms
page-data.json
438 ms
page-data.json
430 ms
page-data.json
485 ms
page-data.json
269 ms
page-data.json
276 ms
image1.png
528 ms
image2.png
684 ms
robandcatherine.jpg
732 ms
51000002611.json
431 ms
component---src-pages-support-jsx-eff7e78ea91e4b6359cc.js
634 ms
component---src-pages-about-jsx-315d8621b61d9f1effd7.js
468 ms
component---src-pages-news-jsx-193604cacaf19304eeff.js
512 ms
component---src-pages-technology-jsx-112952238735817ae3ba.js
1045 ms
component---src-pages-contact-jsx-55a7fe9e785abeaa51e4.js
673 ms
component---src-pages-disease-models-jsx-38f7b2237a84eeb4042e.js
693 ms
component---src-pages-sustainability-jsx-f6271f88c5bec1360a49.js
714 ms
component---src-pages-weather-data-jsx-1f3afd876d934b45a7cc.js
708 ms
component---src-pages-privacy-jsx-d60e6e00576a7192fcf4.js
751 ms
component---src-pages-cookies-jsx-399dfe73edab98026d3e.js
820 ms
component---src-templates-blog-post-jsx-41e744246215088643de.js
697 ms
frame.d7ae132c.css
2 ms
widget.js
4 ms
vendors~polyfill.48e7248658de9dcdb948.widget.js
4 ms
fetch.494792a1d06d9c0901ed.widget.js
3 ms
vendors~core-js.ff243d8f0de9187e3c1b.widget.js
26 ms
0.e2caf280750f3ece06da.widget.js
8 ms
1.0e8f0237accf8416de7f.widget.js
8 ms
8.1ed2c9b768dda7509bd5.widget.js
8 ms
10.e2a6e1199313e5325e57.widget.js
7 ms
16.1c68a125e5ba66106936.widget.js
7 ms
en.json
17 ms
component---src-pages-demo-jsx-961277bf45d4d6fd3d3a.js
334 ms
hortplus.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
hortplus.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
hortplus.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hortplus.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 Hortplus.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.
hortplus.com
Open Graph description is not detected on the main page of Hort Plus. 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: