Access ecard.mx. ecard.mx | Tarjetas Comerciales Digitales para networking y presentación

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

ecard.mx

145 ms

ecard.mx

1879 ms

js

68 ms

bootstrap.min.css

246 ms

font-awesome.min.css

242 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 81% of them (105 requests) were addressed to the original Ecard.mx, 5% (6 requests) were made to Youtube.com and 2% (2 requests) were made to Css.zohocdn.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Ecard.mx.

Content Size

5.8 MB

After Optimization

5.3 MB

In fact, the total size of Ecard.mx main page is 5.8 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. Images take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 83.8 kB

Original 97.1 kB
After minification 61.1 kB
After compression 13.3 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. This page needs HTML code to be minified as it can gain 36.0 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 83.8 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 134.2 kB

Original 5.0 MB
After minification 4.9 MB

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.

JavaScript Optimization

-47%

Potential reduce by 257.0 kB

Original 545.9 kB
After minification 545.9 kB
After compression 288.9 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 257.0 kB or 47% of the original size.

CSS Optimization

-24%

Potential reduce by 41.0 kB

Original 167.8 kB
After minification 167.8 kB
After compression 126.8 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 41.0 kB or 24% of the original size.

Requests Now

121

After Optimization

The browser has sent 121 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 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

High

robots.txt is not valid

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

ES
Language Claimed

EN
Encoding

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 does not match the claimed English 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.

Social Sharing Optimization

ecard.mx

Open Graph data is detected on the main page of Ecard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

ecard.mx | Tarjetas Comerciales Digitales para networking y presentación

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

ecard.mx

ecard.mx

js

bootstrap.min.css

font-awesome.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

ecard.mx

ecard.mx

js

bootstrap.min.css

font-awesome.min.css

animate.min.css

magnific-popup.css

slick.css

custom-animation.css

default.css

style.css

sweetalert2.min.css

sweetalert2.min.js

element.js

modernizr-3.6.0.min.js

jquery.2.2.3.min.js

popper.min.js

bootstrap.min.js

wow.js

jquery.counterup.min.js

waypoints.min.js

TweenMax.min.js

slick.min.js

jquery.magnific-popup.min.js

main.js

css2

fbevents.js

events.js

videoseries

logo-ecard.mx-b.png

icon-tiktok.png

shape-1.png

shape-2.png

shape-3.png

shape-4.png

ecard-cover-isma.png

approved_check_icon.png

hero-line.png

thumb-video-queesecard.jpg

shape-8.png

shape-9.png

shape-10.png

img-soluciones-ventas.jpg