1.1 sec in total
273 ms
683 ms
136 ms
Click here to check amazing Cultivating Healthy Places content. Otherwise, check out these important facts you probably never knew about cultivatinghealthyplaces.com
Cultivating Healthy Places is an international consulting business specializing in social equity, community health and resilient food systems planning. The mission of Cultivating Healthy Places is to ...
Visit cultivatinghealthyplaces.comWe analyzed Cultivatinghealthyplaces.com page load time and found that the first response time was 273 ms and then it took 819 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
cultivatinghealthyplaces.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.5 s
89/100
25%
Value2.3 s
99/100
10%
Value110 ms
98/100
30%
Value0
100/100
15%
Value2.8 s
97/100
10%
273 ms
96 ms
121 ms
131 ms
112 ms
Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Cultivatinghealthyplaces.com, 27% (6 requests) were made to S0.wp.com and 18% (4 requests) were made to S2.wp.com. The less responsive or slowest element that took the longest time to load (273 ms) belongs to the original domain Cultivatinghealthyplaces.com.
Page size can be reduced by 87.7 kB (13%)
687.8 kB
600.1 kB
In fact, the total size of Cultivatinghealthyplaces.com main page is 687.8 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. 35% of websites need less resources to load. Images take 567.7 kB which makes up the majority of the site volume.
Potential reduce by 44.8 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 44.8 kB or 76% of the original size.
Potential reduce by 36.4 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. Cultivating Healthy Places images are well optimized though.
Potential reduce by 6.3 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 6.3 kB or 12% of the original size.
Potential reduce by 116 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. Cultivatinghealthyplaces.com has all CSS files already compressed.
Number of requests can be reduced by 11 (55%)
20
9
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cultivating Healthy Places. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
cultivatinghealthyplaces.com
273 ms
wp-emoji-release.min.js
96 ms
121 ms
css
131 ms
112 ms
118 ms
global.css
110 ms
134 ms
style.css
116 ms
116 ms
116 ms
w.js
70 ms
cropped-cropped-dsc_0159.png
66 ms
ad516503a11cd5ca435acc9bb6523536
65 ms
cropped-chp-square-1.png
107 ms
g.gif
17 ms
remote-login.php
67 ms
g.gif
19 ms
g.gif
19 ms
cropped-cropped-dsc_0159.png
164 ms
actionbar.css
5 ms
actionbar.js
3 ms
cultivatinghealthyplaces.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.
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 IDs are not unique
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
Image elements do not have [alt] attributes
cultivatinghealthyplaces.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
cultivatinghealthyplaces.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cultivatinghealthyplaces.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 Cultivatinghealthyplaces.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.
cultivatinghealthyplaces.com
Open Graph data is detected on the main page of Cultivating Healthy Places. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: