912 ms in total
77 ms
584 ms
251 ms
Visit gonegreen.org now to see the best up-to-date Gone Green content and also check out these interesting facts you probably never knew about gonegreen.org
Visit gonegreen.orgWe analyzed Gonegreen.org page load time and found that the first response time was 77 ms and then it took 835 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.
gonegreen.org performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value10.0 s
0/100
25%
Value2.7 s
96/100
10%
Value540 ms
55/100
30%
Value0.206
60/100
15%
Value10.2 s
25/100
10%
77 ms
37 ms
378 ms
65 ms
93 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 66% of them (33 requests) were addressed to the original Gonegreen.org, 14% (7 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (435 ms) belongs to the original domain Gonegreen.org.
Page size can be reduced by 658.1 kB (45%)
1.5 MB
814.2 kB
In fact, the total size of Gonegreen.org main page is 1.5 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 677.1 kB which makes up the majority of the site volume.
Potential reduce by 13.9 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 13.9 kB or 76% of the original size.
Potential reduce by 53.0 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. Gone Green images are well optimized though.
Potential reduce by 291.1 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 291.1 kB or 69% of the original size.
Potential reduce by 300.1 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. Gonegreen.org needs all CSS files to be minified and compressed as it can save up to 300.1 kB or 84% of the original size.
Number of requests can be reduced by 21 (51%)
41
20
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gone Green. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
gonegreen.org
77 ms
style.css
37 ms
skeleton-responsive.css
378 ms
layout-responsive.css
65 ms
style-custom.css
93 ms
css
26 ms
superfish.css
169 ms
prettyPhoto.css
66 ms
gdl-custom-slider.css
87 ms
logo1.png
98 ms
facebook.png
91 ms
twitter.png
136 ms
youtube.png
121 ms
google-plus.png
169 ms
Fist.png
120 ms
Bank2.png
162 ms
Merriweather_400.font.js
167 ms
superfish.js
208 ms
supersub.js
212 ms
hoverIntent.js
206 ms
gdl-scripts.js
344 ms
jquery.easing.js
435 ms
jquery.prettyPhoto.js
364 ms
jquery.custom-slider.js
343 ms
jquery.cycle.js
361 ms
Tree.png
361 ms
icon-play.png
361 ms
tGk5ioEXlIM
74 ms
www-embed-player-vflfNyN_r.css
39 ms
www-embed-player.js
63 ms
base.js
113 ms
icon-slider-1.png
229 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
95 ms
ad_status.js
95 ms
default-header.jpg
133 ms
header-background.png
51 ms
sub-nav-bg.png
53 ms
Green_Movement_Activism.png
133 ms
bullet-background.png
48 ms
overlap-social-slider-bg.png
91 ms
main-content-gradient.png
92 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
81 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
81 ms
analytics.js
28 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
19 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
26 ms
cj2hUnSRBhwmSPr9kS589-LrC4Du4e_yfTJ8Ol60xk0.ttf
48 ms
c92rD_x0V1LslSFt3-QEpmsGzsqhEorxQDpu60nfWEc.ttf
41 ms
QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf
40 ms
collect
51 ms
gonegreen.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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.
gonegreen.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
gonegreen.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
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 Gonegreen.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 Gonegreen.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.
gonegreen.org
Open Graph description is not detected on the main page of Gone Green. 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: