9.2 sec in total
1.9 sec
6.9 sec
470 ms
Click here to check amazing Greensaver content. Otherwise, check out these important facts you probably never knew about greensaver.org
Visit greensaver.orgWe analyzed Greensaver.org page load time and found that the first response time was 1.9 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
greensaver.org performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value7.1 s
5/100
25%
Value6.3 s
42/100
10%
Value780 ms
38/100
30%
Value0.026
100/100
15%
Value9.6 s
29/100
10%
1870 ms
231 ms
2203 ms
44 ms
217 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 52% of them (61 requests) were addressed to the original Greensaver.org, 29% (34 requests) were made to Maps.googleapis.com and 5% (6 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Greensaver.org.
Page size can be reduced by 3.6 MB (40%)
9.0 MB
5.4 MB
In fact, the total size of Greensaver.org main page is 9.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 4.5 MB which makes up the majority of the site volume.
Potential reduce by 59.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 59.9 kB or 81% of the original size.
Potential reduce by 220.2 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. Greensaver images are well optimized though.
Potential reduce by 1.8 MB
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 1.8 MB or 68% of the original size.
Potential reduce by 1.5 MB
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. Greensaver.org needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 88% of the original size.
Number of requests can be reduced by 68 (60%)
114
46
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greensaver. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
www.greensaver.org
1870 ms
style.css
231 ms
layerslider.css
2203 ms
css
44 ms
frontend.css
217 ms
responsive.css
2232 ms
styles.css
279 ms
styles.css
292 ms
magnific-popup.css
396 ms
light_style.css
454 ms
js_composer.min.css
466 ms
tipsy.css
510 ms
retina.css
591 ms
bootstrap.css
660 ms
font-awesome.css
670 ms
prettyPhoto.css
673 ms
woo.css
779 ms
responsive.css
853 ms
css
27 ms
wpgform.css
842 ms
vc_style.css
834 ms
jquery.js
1003 ms
jquery-migrate.min.js
1043 ms
admin.js
1116 ms
greensock.js
952 ms
layerslider.kreaturamedia.jquery.js
1154 ms
layerslider.transitions.js
2794 ms
powered-by.js
1244 ms
magnific-popup.js
1316 ms
collapse.js
1372 ms
frontend-min.js
1376 ms
jquery.form.min.js
1476 ms
scripts.js
1526 ms
plugins.js
1605 ms
jquery.mb.YTPlayer.min.js
1646 ms
custom.js
1729 ms
jquery.hoverdir.js
1814 ms
SmoothScroll.js
1849 ms
js
24 ms
superfish.js
1936 ms
waypoints.min.js
1959 ms
wp-embed.min.js
1867 ms
js_composer_front.min.js
1949 ms
ProgressCircle.min.js
2067 ms
jquery.vc_chart.min.js
1994 ms
wp-emoji-release.min.js
1962 ms
analytics.js
50 ms
Untitled-1.png
205 ms
shutterstock_556469411.jpg
187 ms
Menu1-350x235.png
218 ms
New2-350x220.png
247 ms
Menu2-350x235.png
239 ms
Menu3-350x235.png
205 ms
Finchviewpic-1-236x300.jpg
186 ms
Screen-Shot-2015-04-02-at-8.53.33-AM.png
376 ms
LogoSlider1-copy.jpg
418 ms
LogoSlider2.jpg
418 ms
LogoSlider3-copy.jpg
429 ms
LogoSlider4.jpg
449 ms
LogoSlider5.jpg
448 ms
fontawesome-webfont.woff
722 ms
embed
153 ms
collect
132 ms
skin.css
534 ms
embed
42 ms
embed
224 ms
rs=ABjfnFW3CLCmbM1GUQ1Hz0fodZmx_VOubg
58 ms
css
20 ms
js
49 ms
rs=ABjfnFXbi8BuqLmD_aVpAN9QywVcy0bhtA
92 ms
rs=ABjfnFXbi8BuqLmD_aVpAN9QywVcy0bhtA
58 ms
common.js
73 ms
map.js
74 ms
overlay.js
73 ms
1493-wht-blank_maps-4x.png&filter=ffDB4436
245 ms
util.js
134 ms
marker.js
134 ms
geocoder.js
121 ms
controls.js
121 ms
places_impl.js
121 ms
selection_2x-000.png
118 ms
gen204
153 ms
onion.js
85 ms
openhand_8_8.cur
159 ms
stats.js
62 ms
ViewportInfoService.GetViewportInfo
152 ms
transparent.png
99 ms
mapcnt6.png
57 ms
skin.png
227 ms
blank.gif
212 ms
LogoSlider1-copy.jpg
75 ms
tmapctrl4.png
28 ms
vt
12 ms
vt
5 ms
vt
6 ms
vt
21 ms
vt
5 ms
vt
19 ms
vt
20 ms
vt
22 ms
vt
19 ms
vt
21 ms
vt
22 ms
vt
23 ms
vt
22 ms
vt
24 ms
vt
23 ms
vt
25 ms
vt
26 ms
vt
24 ms
vt
27 ms
vt
26 ms
vt
25 ms
viewer-icons001.png
21 ms
star4.png
22 ms
MyMaps_Icons003.png
6 ms
vt
15 ms
greensaver.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
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
Links do not have a discernible name
greensaver.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
greensaver.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 Greensaver.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 Greensaver.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.
greensaver.org
Open Graph description is not detected on the main page of Greensaver. 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: