Analyze

greensave.mx: Do Green & Save

Page load speed analysis

  • 58/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    431 ms

  • Resources loaded

    4.9 sec

  • Page rendered

    245 ms

  • Total page load time

    5.6 sec

Click here to check amazing Green Save content for Mexico. Otherwise, check out these important facts you probably never knew about greensave.mx

We 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.

Page optimization

  • HTML 73.2 kB
    Images 227.0 kB
    Javascripts 658.6 kB
    CSS 1.9 MB

    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. 80% 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.

    • Original 73.2 kB
    • After minification 71.8 kB
    • After compression 21.7 kB

    HTML optimization

    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.

    • Original 227.0 kB
    • After optimization 223.9 kB

    Image optimization

    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.

    • Original 658.6 kB
    • After minification 632.6 kB
    • After compression 190.3 kB

    JavaScript optimization

    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 468.2 kB or 71% of the original size.

    • Original 1.9 MB
    • After minification 1.8 MB
    • After compression 210.1 kB

    CSS optimization

    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.

Network requests diagram

  • www.greensave.mx
  • analytics.js
  • wp-emoji-release.min.js
  • style-frontend.css
  • font-awesome.min.css
  • sky-forms.css
  • sky-forms-color-schemes.css
  • styles.css
  • wp_shopping_cart_style.css
  • main.min.css
  • js_composer.css
  • css
  • main.min.css
  • font-awesome.min.css
  • fontello.css
  • main-e266c63153.css
  • custom-d37b7e7fb3.css
  • media-7680a61e81.css
  • style.css
  • style.min.css
  • hotspot.min.css
  • hotspot-tooltipster.min.css
  • Defaults.css
  • jquery.js
  • jquery-migrate.min.js
  • jquery.cookie.js
  • chimpy-frontend.js
  • jquery.form.min.js
  • jquery.validate.min.js
  • jquery.maskedinput.min.js
  • above-the-fold.min.js
  • jquery.form.min.js
  • scripts.js
  • main.min.js
  • wp-embed.min.js
  • js_composer_front.js
  • widgets.js
  • collect
  • infografico-2.jpg
  • sdk.js
  • zN7GBFwfMP4uA6AR0HCoLQ.ttf
  • RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
  • Defaults.woff
  • xd_arbiter.php
  • xd_arbiter.php
  • logo1.png
  • Logo-hor.png
  • button.0308b81ff1714e446f674b5b9793f2cd.js
  • tweet_button.b9740740e0bcf9b0657c5b11bd4388da.es.html
  • like.php
  • like_box.php
  • qeKvIRsJabD.js
  • LVx-xkvaJ0b.png
  • jot
  • 410ucuAGgaJ.css
  • tSbl8xBI27R.css
  • Czh0gDTFcBt.css
  • Ek6lpayKeeB.css
  • EoarYgA68t4.css
  • q68gy-v_YMF.js
  • FJmpeSpHpjS.js
  • 0wM5s1Khldu.js
  • 1bNoFZUdlYZ.js
  • njO1TPvGzoR.js
  • 1QuX41zDRrx.js
  • Oagsvfb4VWi.js
  • LTv6ZK-5zxz.js
  • 1FCa-btixu2.js
  • 11828827_484183825091845_7112377731321982202_n.jpg
  • 11781871_481189292057965_4299975475513272605_n.jpg
  • 12417671_10206880885273004_2231188562920988858_n.jpg
  • 12274382_10206387147570320_1358158748368505424_n.jpg
  • 12651290_132357030479570_2691959066008495226_n.jpg
  • 10348540_10156320662430366_4297377719283314967_n.jpg
  • 10485995_1573308462897971_4619030916562199895_n.jpg
  • 10371896_561512170692343_4556403698663931316_n.jpg
  • 12798823_555230357987191_4341121965838810479_n.jpg
  • 1918183_552882834888610_6024350657466220843_n.jpg
  • 12733626_547619952081565_4361134952122025268_n.jpg
  • 12654403_545259568984270_7127223391742205158_n.jpg
  • wL6VQj7Ab77.png
  • s7jcwEQH7Sx.png
  • QDwYpIaRyfG.png
  • K00K-UgnsKu.png
  • I6-MnjEovm5.js
  • pQrUxxo5oQp.js

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.

Additional info on greensave.mx

Requests

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.

30

Javascripts

23

Images

25

CSS

5

AJAX

83

All

Possible request optimization

1

Javascripts

18

Images

1

CSS

5

AJAX

58

Optimized

25

All

Normal result

IP address

Greensave.mx uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

greensave.mx

matamoros.gob.mx

mygoodfoods.com.mx

casinobarmovil.com

preuch.cl

163.172.75.8

DNS records

Type Host Target/ip TTL Other
A

greensave.mx

163.172.75.8 60
NS

greensave.mx

ns8.iservidorweb.com 60
NS

greensave.mx

ns7.iservidorweb.com 60
SOA

greensave.mx

60 Mname: ns7.iservidorweb.com
Rname: jcvelafuentes.gmail.com
Serial: 2020040400
Refresh: 3600
Retry: 1800
Expire: 1209600
Minimum-ttl: 86400
MX

greensave.mx

allfb.xpress.com.mx 60 Pri: 20

Language and encoding

Good result

Language

ES es language flag

Detected

ES es language flag

Claimed

Encoding

UTF-8

Claimed

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.

HTTPS certificate

SSL Certificate

Greensave.mx has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 100% of all visits is Mexico. It lies approximately 5650 miles away from the server location (France) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up Greensave.mx page load time for the majority of users is moving the server to Mexico or just closer to the user base.

Poor result

Poor result

Social Sharing Optimization

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:

greensave.mx

Share this report in social media

Analyze another website

Analyze