3.4 sec in total
255 ms
2.9 sec
198 ms
Click here to check amazing Capital Growth content. Otherwise, check out these important facts you probably never knew about capitalgrowth.org
We support people to grow food in London, whether at home, on allotments or as part of a community group, and to learn about urban food growing.
Visit capitalgrowth.orgWe analyzed Capitalgrowth.org page load time and found that the first response time was 255 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
capitalgrowth.org performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value10.7 s
0/100
25%
Value6.7 s
36/100
10%
Value310 ms
77/100
30%
Value0.001
100/100
15%
Value9.0 s
34/100
10%
255 ms
524 ms
372 ms
307 ms
302 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 77% of them (40 requests) were addressed to the original Capitalgrowth.org, 19% (10 requests) were made to Sustainweb.org and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Capitalgrowth.org.
Page size can be reduced by 82.7 kB (10%)
810.0 kB
727.4 kB
In fact, the total size of Capitalgrowth.org main page is 810.0 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. 20% of websites need less resources to load. Images take 722.4 kB which makes up the majority of the site volume.
Potential reduce by 16.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 16.3 kB or 74% of the original size.
Potential reduce by 27.3 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. Capital Growth images are well optimized though.
Potential reduce by 16.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 16.2 kB or 43% of the original size.
Potential reduce by 22.9 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. Capitalgrowth.org needs all CSS files to be minified and compressed as it can save up to 22.9 kB or 82% of the original size.
Number of requests can be reduced by 10 (20%)
50
40
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capital Growth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
capitalgrowth.org
255 ms
www.capitalgrowth.org
524 ms
style.css
372 ms
homeslider.js
307 ms
anylinkcssmenu.js
302 ms
LondonsPollinators.jpg
493 ms
FutureFarmers.jpg
492 ms
reaping_rewards_thumbnail.jpg
496 ms
MonitoringReport2013.jpg
494 ms
GrowMoreFoodTopTips.jpg
595 ms
EdibleEstates.jpg
510 ms
PlanningSustainableCities.jpg
884 ms
GrowingHealth_BenefitsReport.jpg
887 ms
good_food_for_london_2013.jpg
788 ms
WhatWeLearned_sm.jpg
903 ms
frame_top.png
190 ms
frame_bottom.png
210 ms
frame_middle.png
191 ms
background_solid.gif
474 ms
BigDigTicker.jpg
610 ms
2015-05-13%2018_12_50.jpg
983 ms
South%20Haringey%20Infant%20School%20-%20climate%20cool1.jpg
590 ms
networking_event_14.jpg
490 ms
alert_small_lock_sm.png
397 ms
alert_small_magni_sm.png
584 ms
go-button.png
677 ms
alert_small_heart_sm.png
692 ms
bee_cg_homepage.jpg
863 ms
hp_training14.jpg
873 ms
london_map.gif
1010 ms
form_green_magni.png
893 ms
hp_twitter.png
895 ms
hp_fbook.png
1080 ms
hp_flicker.png
1078 ms
mayor_london_logo.gif
1083 ms
city_bridge.png
1174 ms
sustain_logo.gif
1200 ms
lfl_logo.gif
1237 ms
alert_small_darrow.png
1263 ms
drop_box_multiline.png
1298 ms
drop_box_bot.png
1300 ms
hp_mission_counter.png
1451 ms
hpbee_mainpic_bg.png
1385 ms
hpbee_mainpic_foot.png
1412 ms
hp_logo.png
1785 ms
drop_box_1line.png
1458 ms
hpbee_contentframe_top.png
1464 ms
hpbee_contentframe_bg.png
1576 ms
hpbee_contentframe_foot.png
1613 ms
ga.js
9 ms
__utm.gif
13 ms
print.css
125 ms
capitalgrowth.org accessibility score
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
Image elements do not have [alt] attributes
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
capitalgrowth.org 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
capitalgrowth.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capitalgrowth.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 Capitalgrowth.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
capitalgrowth.org
Open Graph description is not detected on the main page of Capital Growth. 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: