4.3 sec in total
1.3 sec
2.7 sec
216 ms
Visit gea.mx now to see the best up-to-date GEA content and also check out these interesting facts you probably never knew about gea.mx
Business And Ecommerce Wordpress Theme loaded with the latest and newest awesome features! Use Anya for any type of website, business, corporate, portfolio, blog, products, and an endless other websit...
Visit gea.mxWe analyzed Gea.mx page load time and found that the first response time was 1.3 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
gea.mx performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value3.9 s
53/100
25%
Value5.8 s
50/100
10%
Value140 ms
95/100
30%
Value0.073
96/100
15%
Value6.8 s
55/100
10%
1317 ms
235 ms
26 ms
157 ms
84 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 79% of them (57 requests) were addressed to the original Gea.mx, 10% (7 requests) were made to Grupoezetera.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Gea.mx.
Page size can be reduced by 1.4 MB (30%)
4.7 MB
3.3 MB
In fact, the total size of Gea.mx main page is 4.7 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. 65% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 71.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 71.5 kB or 82% of the original size.
Potential reduce by 141.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. GEA images are well optimized though.
Potential reduce by 553.7 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 553.7 kB or 71% of the original size.
Potential reduce by 642.0 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. Gea.mx needs all CSS files to be minified and compressed as it can save up to 642.0 kB or 87% of the original size.
Number of requests can be reduced by 36 (55%)
66
30
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GEA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.gea.mx
1317 ms
style.css
235 ms
css
26 ms
settings.css
157 ms
load-posts.css
84 ms
skeleton.css
87 ms
camera.css
124 ms
skin.css
126 ms
flexslider.css
134 ms
blog.css
169 ms
prettyPhoto.css
243 ms
resize.css
269 ms
font-awesome.min.css
200 ms
retina.css
211 ms
animate.css
281 ms
component.css
255 ms
designare-woo-layout.css
273 ms
designare-woocommerce.css
347 ms
editor-style.css
296 ms
jquery.min.js
7 ms
jquery-migrate.min.js
307 ms
jquery.themepunch.tools.min.js
354 ms
jquery.themepunch.revolution.min.js
353 ms
jquery.easing.1.3.min.js
136 ms
blog.js
153 ms
js_composer_front.css
130 ms
comment-reply.min.js
122 ms
super-simple-jquery-parallax-background.js
132 ms
jQuerytools.js
132 ms
utils.js
174 ms
waypoints.min.js
145 ms
animated-contents.js
166 ms
jquery.fitvids.js
172 ms
jquery.flexslider-min.js
172 ms
anya.js
174 ms
jquery.tweet.js
187 ms
js_composer_front.js
209 ms
shortcodes.css
185 ms
1420498367gea.png
201 ms
sprite.png
51 ms
c2.png
96 ms
b1.png
381 ms
b3.jpg
52 ms
b4.jpg
52 ms
b5.png
197 ms
b6.png
200 ms
b7.png
379 ms
logo_0.png
96 ms
logo_1.png
198 ms
logo_2.png
199 ms
logo_3.png
199 ms
logo_4.png
200 ms
logo_5.png
199 ms
logo_6.png
374 ms
logo_7.png
374 ms
ajx_loading.gif
375 ms
logo@2x.png
190 ms
icn_1.png
190 ms
icn_2.png
191 ms
icn_3.png
191 ms
icn_4.png
191 ms
timer.png
331 ms
OpenSans-Light-webfont.woff
328 ms
1413329577newsletter1.jpg
35 ms
analytics.js
10 ms
collect
99 ms
logo-prado3.png
93 ms
des-arrows.png
47 ms
fontawesome-webfont.woff
49 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
18 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
18 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
18 ms
gea.mx 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
Links do not have a discernible name
gea.mx 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
gea.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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gea.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 Gea.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.
gea.mx
Open Graph description is not detected on the main page of GEA. 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: