5.6 sec in total
431 ms
4.9 sec
245 ms
Click here to check amazing GREEN SAVE content for Mexico. Otherwise, check out these important facts you probably never knew about greensave.mx
En DO GREEN & SAVE buscamos ofrecer soluciones atractivas de inversión para casa, negocio e industria en beneficio al medio ambiente. Así como contribuir al uso de energías renovables y promover su ap...
Visit greensave.mxWe analyzed Greensave.mx page load time and found that the first response time was 431 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
greensave.mx performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value15.0 s
0/100
25%
Value5.3 s
57/100
10%
Value90 ms
99/100
30%
Value0.001
100/100
15%
Value10.5 s
23/100
10%
431 ms
22 ms
140 ms
135 ms
143 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 44% of them (38 requests) were addressed to the original Greensave.mx, 25% (22 requests) were made to Static.xx.fbcdn.net and 14% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Greensave.mx.
Page size can be reduced by 2.2 MB (77%)
2.9 MB
656.0 kB
In fact, the total size of Greensave.mx main page is 2.9 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. CSS take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 51.6 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 51.6 kB or 70% of the original size.
Potential reduce by 3.1 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. GREEN SAVE images are well optimized though.
Potential reduce by 484.8 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 484.8 kB or 71% of the original size.
Potential reduce by 1.7 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. Greensave.mx needs all CSS files to be minified and compressed as it can save up to 1.7 MB or 89% of the original size.
Number of requests can be reduced by 58 (70%)
83
25
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GREEN SAVE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
www.greensave.mx
431 ms
analytics.js
22 ms
wp-emoji-release.min.js
140 ms
style-frontend.css
135 ms
font-awesome.min.css
143 ms
sky-forms.css
145 ms
sky-forms-color-schemes.css
148 ms
styles.css
147 ms
wp_shopping_cart_style.css
270 ms
main.min.css
283 ms
js_composer.css
457 ms
css
21 ms
main.min.css
432 ms
font-awesome.min.css
285 ms
fontello.css
288 ms
main-e266c63153.css
400 ms
custom-d37b7e7fb3.css
589 ms
media-7680a61e81.css
416 ms
style.css
425 ms
style.min.css
531 ms
hotspot.min.css
553 ms
hotspot-tooltipster.min.css
559 ms
Defaults.css
565 ms
jquery.js
685 ms
jquery-migrate.min.js
660 ms
jquery.cookie.js
705 ms
chimpy-frontend.js
707 ms
jquery.form.min.js
708 ms
jquery.validate.min.js
724 ms
jquery.maskedinput.min.js
798 ms
above-the-fold.min.js
823 ms
jquery.form.min.js
853 ms
scripts.js
852 ms
main.min.js
1087 ms
wp-embed.min.js
869 ms
js_composer_front.js
955 ms
widgets.js
128 ms
collect
13 ms
infografico-2.jpg
451 ms
sdk.js
15 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
15 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
16 ms
Defaults.woff
389 ms
144 ms
xd_arbiter.php
33 ms
xd_arbiter.php
41 ms
logo1.png
69 ms
Logo-hor.png
140 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
29 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.es.html
75 ms
like.php
94 ms
like_box.php
234 ms
qeKvIRsJabD.js
37 ms
LVx-xkvaJ0b.png
24 ms
jot
85 ms
410ucuAGgaJ.css
10 ms
tSbl8xBI27R.css
12 ms
Czh0gDTFcBt.css
28 ms
Ek6lpayKeeB.css
19 ms
EoarYgA68t4.css
32 ms
q68gy-v_YMF.js
48 ms
FJmpeSpHpjS.js
47 ms
0wM5s1Khldu.js
31 ms
1bNoFZUdlYZ.js
31 ms
njO1TPvGzoR.js
27 ms
1QuX41zDRrx.js
46 ms
Oagsvfb4VWi.js
88 ms
LTv6ZK-5zxz.js
93 ms
1FCa-btixu2.js
85 ms
11828827_484183825091845_7112377731321982202_n.jpg
605 ms
11781871_481189292057965_4299975475513272605_n.jpg
44 ms
12417671_10206880885273004_2231188562920988858_n.jpg
47 ms
12274382_10206387147570320_1358158748368505424_n.jpg
44 ms
12651290_132357030479570_2691959066008495226_n.jpg
47 ms
10348540_10156320662430366_4297377719283314967_n.jpg
44 ms
10485995_1573308462897971_4619030916562199895_n.jpg
46 ms
10371896_561512170692343_4556403698663931316_n.jpg
127 ms
12798823_555230357987191_4341121965838810479_n.jpg
91 ms
1918183_552882834888610_6024350657466220843_n.jpg
109 ms
12733626_547619952081565_4361134952122025268_n.jpg
59 ms
12654403_545259568984270_7127223391742205158_n.jpg
57 ms
wL6VQj7Ab77.png
37 ms
s7jcwEQH7Sx.png
36 ms
QDwYpIaRyfG.png
37 ms
K00K-UgnsKu.png
38 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
5 ms
greensave.mx accessibility score
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-*] attributes do not match their roles
[role] values are not valid
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
greensave.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
greensave.mx 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
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greensave.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Greensave.mx 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.
greensave.mx
Open Graph description is not detected on the main page of GREEN SAVE. 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: