5.8 sec in total
33 ms
4.4 sec
1.4 sec
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 33 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
hortplus.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value3.7 s
59/100
25%
Value12.5 s
3/100
10%
Value1,380 ms
16/100
30%
Value0.068
96/100
15%
Value19.8 s
2/100
10%
33 ms
525 ms
113 ms
146 ms
443 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 27% of them (34 requests) were addressed to the original Hortplus.com, 33% (42 requests) were made to Maps.googleapis.com and 24% (30 requests) were made to Hortplus-assets.s3-ap-southeast-2.amazonaws.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Hortplus-assets.s3-ap-southeast-2.amazonaws.com.
Page size can be reduced by 432.1 kB (11%)
4.0 MB
3.6 MB
In fact, the total size of Hortplus.com main page is 4.0 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. 80% 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 3.6 MB which makes up the majority of the site volume.
Potential reduce by 207.1 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 207.1 kB or 75% of the original size.
Potential reduce by 191.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. Hort Plus images are well optimized though.
Potential reduce by 33.2 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 33.2 kB or 25% of the original size.
Potential reduce by 123 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 41 (33%)
124
83
The browser has sent 124 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 42 to 1 for JavaScripts and as a result speed up the page load time.
hortplus.com
33 ms
www.hortplus.com
525 ms
freshwidget.js
113 ms
js
146 ms
polyfill-955a789fe391cbf1cd0b.js
443 ms
component---src-pages-index-jsx-e6d760addeb42ea70047.js
434 ms
ce547dc6d67f41c733cc4d699cf6f41da64ed268-1f80e8b7fc69040e4bad.js
435 ms
framework-6dc75a31a18668b93c59.js
433 ms
styles-407fe62976dc5310c43e.js
432 ms
app-b201834d9e684553e698.js
1505 ms
cb1608f2-67005bbb640867e3df77.js
915 ms
webpack-runtime-54ebd852784d8fc783ab.js
1000 ms
freshwidget.css
47 ms
header_logo.svg
1122 ms
weather_machine.png
2243 ms
nz_apples_and_pears.png
1169 ms
summerfruit_nz.png
1114 ms
onions_nz.png
1113 ms
fruitfed_supplies.png
1114 ms
far.png
1328 ms
watties.png
1328 ms
a_lighter_touch.png
1336 ms
fruition_logo.png
1521 ms
nzppi_logo.svg
1473 ms
swnz_logo.jpg
2016 ms
zespri.png
1526 ms
plant_and_food_research.png
1547 ms
kvh.png
1615 ms
woman_spinach.jpg
2630 ms
plant_and_food_research_office.jpg
2257 ms
agritech_new_zealand_member.jpg
2038 ms
notification.png
2069 ms
iphone_metwatch_app.png
2631 ms
the_weather_company.png
2327 ms
metservice2.png
2327 ms
aus_gov.png
2574 ms
green_weather_station_icon.svg
2622 ms
blue_integrate_icon.svg
2622 ms
iphone_psa.png
2748 ms
desktop_psa.png
2647 ms
logo.svg
2950 ms
weather_machine.svg
2926 ms
nz_hills.jpg
2931 ms
analytics.js
186 ms
poppins-all-400-normal-2b7b1aec0bbda049675f582f71d6d9a3.woff
495 ms
bootstrap.js
6 ms
app-data.json
258 ms
page-data.json
271 ms
js
148 ms
page-data.json
603 ms
page-data.json
359 ms
page-data.json
600 ms
page-data.json
365 ms
page-data.json
992 ms
page-data.json
363 ms
page-data.json
644 ms
page-data.json
653 ms
page-data.json
651 ms
page-data.json
761 ms
page-data.json
758 ms
51000002611.json
592 ms
collect
15 ms
gen_204
74 ms
common.js
58 ms
util.js
80 ms
marker.js
81 ms
map.js
70 ms
openhand_8_8.cur
254 ms
onion.js
159 ms
component---src-pages-technology-jsx-ecbb1c50dece11c766d3.js
389 ms
component---src-pages-support-jsx-12060ab2672f7171656d.js
383 ms
component---src-pages-contact-jsx-905910c7126d15cbc435.js
385 ms
ViewportInfoService.GetViewportInfo
159 ms
ViewportInfoService.GetViewportInfo
367 ms
component---src-pages-weather-data-jsx-230c848828f84be62d7d.js
461 ms
component---src-pages-about-jsx-9d7a0359a605eeec14e9.js
461 ms
frame.d7ae132c.css
16 ms
widget.js
38 ms
component---src-pages-demo-jsx-19f7f8ecd50b3c55ce84.js
498 ms
component---src-pages-sustainability-jsx-cabbc3e5321638bc558c.js
529 ms
component---src-pages-disease-models-jsx-b8faf133eaae2a99ccb9.js
511 ms
transparent.png
71 ms
vendors~polyfill.1cd3d839d72b2aac0b8c.widget.js
35 ms
fetch.e830be6402aed1193c54.widget.js
33 ms
vendors~core-js.01ed1e490b25d6fde934.widget.js
36 ms
spotlight-poi2.png
186 ms
component---src-pages-cookies-jsx-06f2272ed389e39dcaba.js
414 ms
component---src-pages-privacy-jsx-a3317d8ae3f1bcc3b8dd.js
560 ms
AuthenticationService.Authenticate
186 ms
vt
138 ms
vt
136 ms
vt
135 ms
vt
172 ms
vt
170 ms
vt
171 ms
vt
197 ms
vt
197 ms
vt
141 ms
vt
182 ms
vt
219 ms
vt
246 ms
QuotaService.RecordEvent
182 ms
0.1c2c4df3af1f24955f03.widget.js
76 ms
1.0e8f0237accf8416de7f.widget.js
75 ms
8.b00b5c47e72483f1ea64.widget.js
75 ms
10.94324fab217fc1ec04d6.widget.js
98 ms
16.f5c2a912e2eea8c50e66.widget.js
96 ms
vt
115 ms
vt
150 ms
vt
150 ms
vt
151 ms
vt
155 ms
vt
180 ms
vt
172 ms
vt
173 ms
vt
182 ms
vt
199 ms
vt
215 ms
vt
215 ms
vt
204 ms
vt
204 ms
vt
215 ms
vt
272 ms
vt
254 ms
vt
236 ms
QuotaService.RecordEvent
276 ms
en.json
38 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.
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
<frame> or <iframe> elements do not have a title
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
Browser errors were logged to the console
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: