3.8 sec in total
57 ms
2.7 sec
1 sec
Click here to check amazing Dcgo content. Otherwise, check out these important facts you probably never knew about dcgo.org
We are the Dunwoody Community Garden and Orchard, a volunteer- run community garden located at Brook Run Park in Dunwoody, Georgia.
Visit dcgo.orgWe analyzed Dcgo.org page load time and found that the first response time was 57 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
dcgo.org performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value39.1 s
0/100
25%
Value17.1 s
0/100
10%
Value670 ms
44/100
30%
Value0.051
99/100
15%
Value19.2 s
2/100
10%
57 ms
1487 ms
22 ms
46 ms
269 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 76% of them (69 requests) were addressed to the original Dcgo.org, 19% (17 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Dcgo.org.
Page size can be reduced by 1.8 MB (18%)
10.0 MB
8.2 MB
In fact, the total size of Dcgo.org main page is 10.0 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. 85% 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 9.0 MB which makes up the majority of the site volume.
Potential reduce by 114.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 114.5 kB or 84% of the original size.
Potential reduce by 1.4 MB
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, Dcgo needs image optimization as it can save up to 1.4 MB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 194.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 194.6 kB or 33% of the original size.
Potential reduce by 97.8 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. Dcgo.org needs all CSS files to be minified and compressed as it can save up to 97.8 kB or 31% of the original size.
Number of requests can be reduced by 60 (87%)
69
9
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dcgo. 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 31 to 1 for CSS and as a result speed up the page load time.
dcgo.org
57 ms
dcgo.org
1487 ms
select2.min.css
22 ms
iconfonts.css
46 ms
frontend.min.css
269 ms
tooltip.css
49 ms
tooltipster-sideTip-shadow.min.css
56 ms
featherlight.css
52 ms
css
61 ms
lity.min.css
51 ms
mec-general-calendar.css
110 ms
style.min.css
165 ms
nectar-slider.css
111 ms
font-awesome-legacy.min.css
116 ms
grid-system.css
91 ms
style.css
392 ms
header-layout-centered-bottom-bar.css
123 ms
element-highlighted-text.css
119 ms
element-fancy-unordered-list.css
121 ms
css
58 ms
responsive.css
170 ms
skin-material.css
187 ms
menu-dynamic.css
141 ms
js_composer.min.css
200 ms
salient-dynamic-styles.css
239 ms
style.css
176 ms
css
56 ms
jquery.min.js
295 ms
jquery-migrate.min.js
195 ms
mec-general-calendar.js
346 ms
tooltip.js
372 ms
frontend.js
360 ms
events.js
284 ms
js
120 ms
css
53 ms
style-non-critical.css
342 ms
jquery.fancybox.css
304 ms
core.css
340 ms
slide-out-right-material.css
351 ms
slide-out-right-hover.css
353 ms
core.min.js
532 ms
datepicker.min.js
522 ms
jquery.typewatch.js
355 ms
featherlight.js
515 ms
select2.full.min.js
492 ms
lity.min.js
486 ms
colorbrightness.min.js
482 ms
owl.carousel.min.js
495 ms
anime.min.js
481 ms
nectar-slider.js
580 ms
jquery.easing.min.js
424 ms
jquery.mousewheel.min.js
423 ms
priority.js
420 ms
nectar-slider-priority.js
418 ms
transit.min.js
419 ms
waypoints.js
414 ms
imagesLoaded.min.js
397 ms
hoverintent.min.js
371 ms
jquery.fancybox.js
497 ms
superfish.js
362 ms
init.js
488 ms
touchswipe.min.js
343 ms
js_composer_front.min.js
338 ms
flipcount.js
298 ms
DunwoodyGarden_logo_small.jpg
91 ms
spring-in-the-hobby-garden-U935Q6U-scaled.jpg
298 ms
vegetables-in-the-hydroponic-farm-PPBWM76-scaled.jpg
148 ms
carrots-and-beets-PW9HJKX-scaled.jpg
143 ms
senior-couple-with-box-of-vegetables-on-farm-PK2XJRT-scaled.jpg
145 ms
dcgo_plots_oblique2.png
304 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
102 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
102 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
193 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
223 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
226 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
228 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf
226 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf
226 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
225 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
227 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
233 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
233 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
230 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
229 ms
fontawesome-webfont.svg
98 ms
fontawesome-webfont.woff
221 ms
icomoon.woff
18 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf
190 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf
187 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf
191 ms
fontawesome-webfont.woff
45 ms
dcgo.org 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
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.
dcgo.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
dcgo.org SEO score
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 Dcgo.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 Dcgo.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.
dcgo.org
Open Graph data is detected on the main page of Dcgo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: