11.3 sec in total
2.8 sec
8.1 sec
392 ms
Click here to check amazing Horticulture content. Otherwise, check out these important facts you probably never knew about horticulture.org.uk
Become a member of the Chartered Institute of Horticulture (CIH) today and grow your career with us. We are the professional voice for horticulture.
Visit horticulture.org.ukWe analyzed Horticulture.org.uk page load time and found that the first response time was 2.8 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
horticulture.org.uk performance score
name
value
score
weighting
Value13.8 s
0/100
10%
Value22.5 s
0/100
25%
Value24.2 s
0/100
10%
Value550 ms
54/100
30%
Value0.145
77/100
15%
Value30.4 s
0/100
10%
2846 ms
216 ms
411 ms
415 ms
248 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 57% of them (56 requests) were addressed to the original Horticulture.org.uk, 18% (18 requests) were made to Platform.twitter.com and 17% (17 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Horticulture.org.uk.
Page size can be reduced by 2.8 MB (29%)
9.7 MB
6.9 MB
In fact, the total size of Horticulture.org.uk main page is 9.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. 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. Images take 7.3 MB which makes up the majority of the site volume.
Potential reduce by 58.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 58.5 kB or 79% of the original size.
Potential reduce by 875.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, Horticulture needs image optimization as it can save up to 875.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 616.6 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 616.6 kB or 71% of the original size.
Potential reduce by 1.3 MB
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. Horticulture.org.uk needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 86% of the original size.
Number of requests can be reduced by 59 (75%)
79
20
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Horticulture. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
www.horticulture.org.uk
2846 ms
wp-emoji-release.min.js
216 ms
cv.css
411 ms
style.min.css
415 ms
vendors-style.css
248 ms
style.css
528 ms
theme-my-login.min.css
248 ms
woocommerce-layout.css
331 ms
woocommerce.css
448 ms
frontend.css
330 ms
job-listings.css
412 ms
style.css
579 ms
css
68 ms
wc-memberships-frontend.min.css
444 ms
style.css
446 ms
css
87 ms
dashicons.min.css
576 ms
jquery.min.js
607 ms
jquery-migrate.min.js
532 ms
events-manager.js
611 ms
frontend.js
610 ms
es6-promise.auto.min.js
610 ms
recaptcha.js
659 ms
et-core-unified-128-17241450078274.min.css
660 ms
widgets.js
15 ms
mediaelementplayer-legacy.min.css
611 ms
wp-mediaelement.min.css
612 ms
css
23 ms
cv.js
613 ms
theme-my-login.min.js
613 ms
jquery.blockUI.min.js
661 ms
js.cookie.min.js
662 ms
woocommerce.min.js
692 ms
cart-fragments.min.js
694 ms
idle-timer.min.js
695 ms
custom.js
695 ms
custom.unified.js
908 ms
common.js
744 ms
wp-embed.min.js
774 ms
mediaelement-and-player.min.js
858 ms
mediaelement-migrate.min.js
776 ms
wp-mediaelement.min.js
696 ms
style.css
712 ms
analytics.js
113 ms
CIH.svg
184 ms
Scientist-1.jpg
291 ms
v33.2-Summer-2024-cover.jpg
699 ms
Untitled-design-19.png
183 ms
apples-1873078_1280.jpg
947 ms
SCI-Logo.png
183 ms
UK-Gov.png
290 ms
v33.2-Summer-2024-cover-400x250.jpg
290 ms
Untitled-design-19-400x250.png
290 ms
apples-1873078_1280-400x250.jpg
370 ms
CIH-Grow-South-2024-SM-Artwork-revised-2.png
1362 ms
1.png
588 ms
CIH-Reversed.svg
366 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
220 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf
263 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf
263 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
262 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
263 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
263 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
229 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf
264 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
265 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
265 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
264 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
264 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
266 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
268 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
269 ms
modules.ttf
394 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
229 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
228 ms
monarch.ttf
349 ms
collect
127 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
116 ms
www.horticulture.org.uk
1851 ms
settings
110 ms
js
78 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
3 ms
CIHort
63 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
4 ms
runtime-b1c52fd0a13ead5fcf6b.js
18 ms
modules-96ebc7ac3ad66d681a3d.js
24 ms
main-babd9234dc048fb47339.js
22 ms
_app-a9c9f1a99e4414675fb1.js
23 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
22 ms
_buildManifest.js
23 ms
_ssgManifest.js
22 ms
8526.0c32a8f0cfc5749221a3.js
13 ms
1755.07a49c40b12af4f75780.js
14 ms
8283.f3e5048cca7cef5eed7f.js
4 ms
3077.44bfeb00af01bc4020f6.js
9 ms
1362.42d432e02f7980bca032.js
7 ms
4956.c4e51ef593974b9db0bb.js
22 ms
5893.d500bd2a89ded806aa73.js
6 ms
woocommerce-smallscreen.css
84 ms
horticulture.org.uk 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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
horticulture.org.uk 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
horticulture.org.uk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Horticulture.org.uk 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 Horticulture.org.uk 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.
horticulture.org.uk
Open Graph data is detected on the main page of Horticulture. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: