15.4 sec in total
6 sec
9.2 sec
247 ms
Visit intgardencentre.org now to see the best up-to-date Int Garden Centre content and also check out these interesting facts you probably never knew about intgardencentre.org
Visit intgardencentre.orgWe analyzed Intgardencentre.org page load time and found that the first response time was 6 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
intgardencentre.org performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value14.5 s
0/100
25%
Value14.2 s
1/100
10%
Value10 ms
100/100
30%
Value0.006
100/100
15%
Value7.7 s
45/100
10%
6039 ms
184 ms
185 ms
543 ms
271 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 65% of them (50 requests) were addressed to the original Intgardencentre.org, 13% (10 requests) were made to Static.xx.fbcdn.net and 8% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Intgardencentre.org.
Page size can be reduced by 909.6 kB (42%)
2.2 MB
1.3 MB
In fact, the total size of Intgardencentre.org main page is 2.2 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. 45% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 36.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 36.5 kB or 80% of the original size.
Potential reduce by 26.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. Int Garden Centre images are well optimized though.
Potential reduce by 377.0 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 377.0 kB or 70% of the original size.
Potential reduce by 470.0 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. Intgardencentre.org needs all CSS files to be minified and compressed as it can save up to 470.0 kB or 86% of the original size.
Number of requests can be reduced by 48 (67%)
72
24
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Int Garden Centre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
intgardencentre.org
6039 ms
general.css
184 ms
system.css
185 ms
bootstrap.css
543 ms
font-awesome.css
271 ms
font-socialico.css
186 ms
template-cyan.css
695 ms
bonus-page.css
272 ms
pattern.css
268 ms
responsive.css
438 ms
responsive.css
445 ms
css
22 ms
font-awesome.css
360 ms
glyphicon.css
362 ms
shortcodes.css
621 ms
styles.css
452 ms
styles.css
527 ms
jquery.min.js
855 ms
jquery-noconflict.js
546 ms
jquery.min.js
935 ms
jquery-noconflict.js
625 ms
jquery-migrate.min.js
634 ms
caption.js
705 ms
bootstrap.min.js
717 ms
keepmenu.js
724 ms
yt-script.js
780 ms
prettify.js
816 ms
yt-extend.js
806 ms
jquery.easing.1.3.js
850 ms
jquery.megamenu.js
894 ms
gooeymenu.js
898 ms
jquery.prettyPhoto.js
1117 ms
prettify.js
1121 ms
shortcodes.js
947 ms
jcarousel.js
1019 ms
jquery.cj-swipe.js
992 ms
widgets.js
80 ms
raphael-min.js
1149 ms
system.css
869 ms
jquery.easing.js
947 ms
iview.js
1116 ms
jquery.min.php
520 ms
logo.png
306 ms
2d041a2f0e19c7a8b6fc8426fb1e5ee3_normal.jpeg
28 ms
international-congresses.jpg
292 ms
past-congresses.jpg
291 ms
study-tour.jpg
130 ms
igca-main-aims.jpg
132 ms
igca-gardening-news.jpg
132 ms
photo-galleries.jpg
289 ms
analytics.js
18 ms
collect
37 ms
OttjxgcoEsufOGSINYBGLZ0EAVxt0G0biEntp43Qt6E.ttf
37 ms
fontawesome-webfont.woff
336 ms
twitter_logo.png
1122 ms
likebox.php
274 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
127 ms
c74adeef89273d8514128b926313c4c7.jpg
1139 ms
sl4.jpg
1022 ms
410ucuAGgaJ.css
177 ms
tSbl8xBI27R.css
219 ms
q68gy-v_YMF.js
298 ms
FJmpeSpHpjS.js
379 ms
0wM5s1Khldu.js
321 ms
1bNoFZUdlYZ.js
324 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en-gb.html
63 ms
jot
110 ms
10891880_892789300761112_1898868288748987653_n.jpg
210 ms
602687_604984149541630_1851862745_n.jpg
244 ms
1426285_1412754725624490_1873114551_n.jpg
284 ms
1379841_10150004552801901_469209496895221757_n.jpg
323 ms
11146544_1420395618279167_2612375412231151677_n.jpg
322 ms
167260_102640176478989_2006863_n.jpg
320 ms
wL6VQj7Ab77.png
61 ms
s7jcwEQH7Sx.png
61 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
81 ms
intgardencentre.org 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
[aria-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
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
intgardencentre.org 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
intgardencentre.org 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
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
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 Intgardencentre.org 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 Intgardencentre.org 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.
intgardencentre.org
Open Graph description is not detected on the main page of Int Garden Centre. 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: