11.2 sec in total
630 ms
10.3 sec
335 ms
Visit horti.co.za now to see the best up-to-date Horti content for South Africa and also check out these interesting facts you probably never knew about horti.co.za
Buy plants online in South Africa. Horticulture. Flowers, compost, camellias, indigenous, exotic. Rare plant sales. independent nurseries.
Visit horti.co.zaWe analyzed Horti.co.za page load time and found that the first response time was 630 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
horti.co.za performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value13.6 s
0/100
25%
Value20.7 s
0/100
10%
Value830 ms
35/100
30%
Value0.136
80/100
15%
Value14.2 s
9/100
10%
630 ms
4706 ms
391 ms
622 ms
717 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Horti.co.za, 78% (90 requests) were made to Shop.horti.co.za and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Shop.horti.co.za.
Page size can be reduced by 226.4 kB (31%)
740.2 kB
513.8 kB
In fact, the total size of Horti.co.za main page is 740.2 kB. 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. CSS take 334.7 kB which makes up the majority of the site volume.
Potential reduce by 211.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 211.5 kB or 84% of the original size.
Potential reduce by 3.1 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. Obviously, Horti needs image optimization as it can save up to 3.1 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 6.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 5.3 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. Horti.co.za has all CSS files already compressed.
Number of requests can be reduced by 90 (92%)
98
8
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Horti. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
horti.co.za
630 ms
shop.horti.co.za
4706 ms
wp-emoji-release.min.js
391 ms
dashicons.min.css
622 ms
style.min.css
717 ms
wc-blocks-vendors-style.css
713 ms
wc-blocks-style.css
953 ms
style.css
718 ms
magnific-popup.css
712 ms
geolocation.min.css
848 ms
style.css
937 ms
style.css
957 ms
front-peach.css
958 ms
woo-conditional-shipping.css
960 ms
css2
58 ms
font-electro.css
1086 ms
animate.min.css
1167 ms
style.min.css
1635 ms
style.css
1165 ms
font-awesome.min.css
1177 ms
all.css
219 ms
elementor-icons.min.css
1182 ms
frontend-legacy.min.css
1305 ms
frontend.min.css
1625 ms
post-20.css
1408 ms
font-awesome.min.css
1403 ms
post-5159.css
1401 ms
all.min.css
1545 ms
green.min.css
1670 ms
v4-shims.css
268 ms
css
38 ms
jquery.min.js
1877 ms
jquery-migrate.min.js
1687 ms
jquery.magnific-popup.min.js
1785 ms
jed.js
1859 ms
sweetalert2.all.min.js
1860 ms
helper.js
1896 ms
jquery.blockUI.min.js
1897 ms
add-to-cart.min.js
2025 ms
woocommerce-add-to-cart.js
2096 ms
js
55 ms
analytics.js
2115 ms
css
15 ms
js_composer.min.css
2034 ms
animations.min.css
1805 ms
rs6.css
1562 ms
wpforms-full.min.css
1600 ms
jquery.cookie.min.js
1659 ms
woo-conditional-shipping.js
1658 ms
jquery.selectBox.min.js
1879 ms
jquery.prettyPhoto.min.js
1759 ms
jquery.yith-wcwl.min.js
1676 ms
rbtools.min.js
1657 ms
rs6.min.js
2327 ms
js.cookie.min.js
1652 ms
woocommerce.min.js
1755 ms
cart-fragments.min.js
1627 ms
script.js
1933 ms
enquiry.js
1903 ms
script.js
1903 ms
front-peach.js
1899 ms
mailchimp-woocommerce-public.min.js
1779 ms
bootstrap.bundle.min.js
1969 ms
waypoints.min.js
1968 ms
waypoints-sticky.min.js
1854 ms
typeahead.bundle.min.js
1825 ms
handlebars.min.js
1630 ms
electro.min.js
1820 ms
owl.carousel.min.js
1805 ms
login-form-popup.js
1808 ms
smush-lazy-load.min.js
1713 ms
js_composer_front.min.js
1642 ms
webpack.runtime.min.js
1643 ms
frontend-modules.min.js
1829 ms
core.min.js
1831 ms
swiper.min.js
2072 ms
share-link.min.js
1707 ms
js
56 ms
analytics.js
22 ms
dialog.min.js
1608 ms
frontend.min.js
1606 ms
preloaded-modules.min.js
1825 ms
underscore.min.js
1829 ms
wp-util.min.js
2307 ms
collect
56 ms
collect
31 ms
frontend.min.js
1719 ms
collect
226 ms
collect
252 ms
fbevents.js
247 ms
jquery.validate.min.js
1510 ms
mailcheck.min.js
1629 ms
punycode.min.js
1631 ms
utils.min.js
1638 ms
fa-solid-900.woff
503 ms
fa-regular-400.woff
582 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
110 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
111 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
428 ms
KFOkCnqEu92Fr1MmgVxIIzQXKMny.woff
503 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
503 ms
KFOlCnqEu92Fr1MmYUtfBBc-AMP6lQ.woff
501 ms
wpforms.min.js
1645 ms
font-electro.woff
1645 ms
fa-solid-900.woff
2212 ms
fa-solid-900.woff
1821 ms
fa-regular-400.woff
2122 ms
7712549e5e244bb76b799fbbe.js
566 ms
identity.js
300 ms
325088029262356
384 ms
fa-brands-400.woff
478 ms
fa-regular-400.woff
1731 ms
fa-brands-400.woff
1733 ms
fa-brands-400.woff
1851 ms
dummy.png
1726 ms
logo300x60.png
1312 ms
horti.co.za accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
horti.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
horti.co.za SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Horti.co.za 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 Horti.co.za 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.
horti.co.za
Open Graph data is detected on the main page of Horti. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: