Access edigar.com.mx. Edigar | Venta de Material de curación y Ortopédicos

name

value

score

weighting

FCP (First Contentful Paint)

Value15.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.2 s

0/100

25%

SI (Speed Index)

Value37.4 s

0/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value25.8 s

0/100

10%

www.edigar.com.mx

1090 ms

layerslider.css

25 ms

css

41 ms

style.min.css

52 ms

styles.css

66 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 73% of them (65 requests) were addressed to the original Edigar.com.mx, 7% (6 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Bloweek.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Bloweek.com.

Content Size

2.7 MB

After Optimization

2.3 MB

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

HTML Optimization

-79%

Potential reduce by 90.2 kB

Original 114.0 kB
After minification 111.6 kB
After compression 23.8 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 90.2 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 204.0 kB

Original 1.9 MB
After minification 1.7 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. Obviously, Edigar needs image optimization as it can save up to 204.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 132.1 kB

Original 586.6 kB
After minification 586.6 kB
After compression 454.4 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 132.1 kB or 23% of the original size.

CSS Optimization

-9%

Potential reduce by 9.9 kB

Original 105.7 kB
After minification 105.7 kB
After compression 95.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. Edigar.com.mx has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edigar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 22 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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ES
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edigar.com.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Edigar.com.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

edigar.com.mx

Open Graph data is detected on the main page of Edigar. 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

Edigar | Venta de Material de curación y Ortopédicos

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

www.edigar.com.mx

layerslider.css

css

style.min.css

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

www.edigar.com.mx

layerslider.css

css

style.min.css

styles.css

cresta-whatsapp-chat-front-css.min.css

front.css

woocommerce-layout.css

woocommerce.css

slick.css

wcpscwc-public.css

mmenu.css

bootstrap.min.css

prettyPhoto.css

animate.css

font-awesome.min.css

tw_woocommerce.css

style.css

responsive.css

css

jquery.min.js

jquery-migrate.min.js

layerslider.utils.js

layerslider.kreaturamedia.jquery.js

layerslider.transitions.js

front.js

jquery.blockUI.min.js

add-to-cart.min.js

js.cookie.min.js

woocommerce.min.js

js

adsbygoogle.js

wc-blocks.css

index.js

index.js

sourcebuster.min.js

order-attribution.min.js

scripts.js

waves-script.js

themewaves.js

deprecation-notice.js

slick.min.js

wcpscwc-public.js