8 sec in total
1.7 sec
6.2 sec
93 ms
Click here to check amazing Ecard content. Otherwise, check out these important facts you probably never knew about ecard.mx
La mejor plataforma para comunicar con relevancia tu marca es ecard.mx Te conecta a un mundo de posibilidades, captura la esencia de tu oferta y lo más importante, ¡vende! Conoce de nuestros planes, c...
Visit ecard.mxWe analyzed Ecard.mx page load time and found that the first response time was 1.7 sec and then it took 6.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.
ecard.mx performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value4.1 s
48/100
25%
Value4.8 s
67/100
10%
Value510 ms
57/100
30%
Value0.029
100/100
15%
Value8.8 s
35/100
10%
1683 ms
150 ms
168 ms
143 ms
24 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 82% of them (59 requests) were addressed to the original Ecard.mx, 6% (4 requests) were made to Maps.googleapis.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Ecard.mx.
Page size can be reduced by 1.9 MB (77%)
2.5 MB
573.0 kB
In fact, the total size of Ecard.mx main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 18.4 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 18.4 kB or 76% of the original size.
Potential reduce by 815 B
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. Ecard images are well optimized though.
Potential reduce by 881.2 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 881.2 kB or 69% of the original size.
Potential reduce by 981.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. Ecard.mx needs all CSS files to be minified and compressed as it can save up to 981.0 kB or 87% of the original size.
Number of requests can be reduced by 58 (87%)
67
9
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
www.ecard.mx
1683 ms
language-selector.css
150 ms
cache.skin.css
168 ms
layerslider.css
143 ms
css
24 ms
styles.css
166 ms
settings.css
124 ms
tweets.css
195 ms
navigation.css
220 ms
cms-navigation-base.css
258 ms
cms-navigation.css
221 ms
bootstrap.css
315 ms
flexslider.css
279 ms
prettyPhoto.css
280 ms
owl.carousel.css
294 ms
hover_pack.css
309 ms
settings.css
365 ms
style.css
384 ms
color.php
1197 ms
royalslider.css
377 ms
rs-default-inverted.css
382 ms
icomoon.css
443 ms
font-awesome.css
458 ms
js_composer.css
450 ms
css
23 ms
greensock.js
558 ms
jquery.js
556 ms
jquery-migrate.min.js
508 ms
layerslider.kreaturamedia.jquery.js
540 ms
layerslider.transitions.js
551 ms
jquery.themepunch.tools.min.js
608 ms
jquery.themepunch.revolution.min.js
652 ms
menu_functions.js
615 ms
wp-emoji-release.min.js
477 ms
jquery.form.min.js
148 ms
scripts.js
207 ms
bootstrap.js
212 ms
hovermenu.js
214 ms
jquery.fitvids.js
220 ms
jquery.unveilEffects.js
251 ms
retina-1.1.0.js
258 ms
jquery.flexslider-min.js
283 ms
isotope.pkgd.min.js
274 ms
jquery.isotope.center.js
268 ms
jquery.prettyPhoto.js
331 ms
js
40 ms
jquery.gmap.min.js
323 ms
owl.carousel.js
331 ms
jquery.royalslider.min.js
380 ms
jquery.animate-enhanced.min.js
335 ms
jquery.easypiechart.min.js
371 ms
application.js
386 ms
sitepress.js
387 ms
js_composer_front.js
394 ms
logofinal.jpg
85 ms
mx.png
66 ms
us.png
65 ms
H-7iKvDu378
114 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
55 ms
fontawesome-webfont.svg
376 ms
fontawesome-webfont.woff
139 ms
common.js
38 ms
util.js
59 ms
geocoder.js
52 ms
skin.css
75 ms
www-embed-player-vflfNyN_r.css
34 ms
www-embed-player.js
48 ms
base.js
73 ms
H-7iKvDu378
61 ms
maxresdefault.jpg
994 ms
skin.png
59 ms
loading.gif
84 ms
ecard.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
[aria-*] attributes do not have valid values
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
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
ecard.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
Page has valid source maps
ecard.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 Ecard.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 Ecard.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.
ecard.mx
Open Graph description is not detected on the main page of Ecard. 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: