Tools & Wizards About Us
ecodena.com.mx screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

ecodena.com.mx

Ecodena México | aguas residuales

Page Load Speed

3.3 sec in total

First Response

255 ms

Resources Loaded

2.5 sec

Page Rendered

572 ms

ecodena.com.mx screenshot

About Website

Click here to check amazing Ecodena content for Mexico. Otherwise, check out these important facts you probably never knew about ecodena.com.mx

Somos fabricantes y distribuidores de equipos y sistemas para el tratamiento de aguas residuales. Contamos con asistencia técnica.

Visit ecodena.com.mx

Key Findings

We analyzed Ecodena.com.mx page load time and found that the first response time was 255 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ecodena.com.mx performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.684

7/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

ecodena.com.mx

255 ms

ecodena.com.mx

748 ms

main.css

240 ms

woocommerce-layout.css

174 ms

woocommerce.css

249 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 67% of them (56 requests) were addressed to the original Ecodena.com.mx, 29% (24 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (748 ms) belongs to the original domain Ecodena.com.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 300.3 kB (25%)

Content Size

1.2 MB

After Optimization

912.7 kB

  • HTML
  • Images

In fact, the total size of Ecodena.com.mx main page is 1.2 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 880.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 280.1 kB

  • Original 332.3 kB
  • After minification 327.1 kB
  • After compression 52.2 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 280.1 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 20.2 kB

  • Original 880.6 kB
  • After minification 860.5 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. Ecodena images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 36 (65%)

Requests Now

55

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecodena. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ecodena.com.mx

ecodena.com.mx

255 ms

ecodena.com.mx

ecodena.com.mx

748 ms

main.css

main.css

240 ms

woocommerce-layout.css

woocommerce-layout.css

174 ms

woocommerce.css

woocommerce.css

249 ms

front.min.css

front.min.css

253 ms

formreset.min.css

formreset.min.css

245 ms

formsmain.min.css

formsmain.min.css

331 ms

readyclass.min.css

readyclass.min.css

255 ms

browsers.min.css

browsers.min.css

251 ms

style.css

style.css

315 ms

csshero-static-style-ecodena2022.css

csshero-static-style-ecodena2022.css

315 ms

add-to-cart.min.js

add-to-cart.min.js

324 ms

js.cookie.min.js

js.cookie.min.js

345 ms

woocommerce.min.js

woocommerce.min.js

346 ms

ie-compat.min.js

ie-compat.min.js

395 ms

jquery.json.min.js

jquery.json.min.js

394 ms

gravityforms.min.js

gravityforms.min.js

492 ms

js

js

82 ms

et-core-unified-38.min.css

et-core-unified-38.min.css

351 ms

js

js

41 ms

wc-blocks.css

wc-blocks.css

486 ms

app.js

app.js

486 ms

sourcebuster.min.js

sourcebuster.min.js

486 ms

order-attribution.min.js

order-attribution.min.js

486 ms

front.min.js

front.min.js

530 ms

scripts.min.js

scripts.min.js

690 ms

jquery.fitvids.js

jquery.fitvids.js

488 ms

jquery.mobile.js

jquery.mobile.js

502 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

511 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

528 ms

wp-polyfill.min.js

wp-polyfill.min.js

730 ms

dom-ready.min.js

dom-ready.min.js

603 ms

hooks.min.js

hooks.min.js

612 ms

i18n.min.js

i18n.min.js

650 ms

a11y.min.js

a11y.min.js

651 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

653 ms

common.js

common.js

678 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

696 ms

lazyload.min.js

lazyload.min.js

703 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZkO4ljQ.woff

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZkO4ljQ.woff

49 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZkO4ljg.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZkO4ljg.ttf

57 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZou4ljQ.woff

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZou4ljQ.woff

59 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZou4ljg.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZou4ljg.ttf

58 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZ_O4ljQ.woff

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZ_O4ljQ.woff

57 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZ_O4ljg.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZ_O4ljg.ttf

59 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZfOkljQ.woff

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZfOkljQ.woff

57 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZfOkljg.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZfOkljg.ttf

97 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZRekljQ.woff

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZRekljQ.woff

97 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZRekljg.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZRekljg.ttf

96 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZIukljQ.woff

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZIukljQ.woff

161 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZIukljg.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZIukljg.ttf

96 ms

modules.woff

modules.woff

399 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvgUI.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvgUI.woff

97 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvgUE.ttf

98 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUI.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUI.woff

95 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf

97 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vgUI.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs169vgUI.woff

102 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vgUE.ttf

102 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvgUI.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvgUI.woff

101 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvgUE.ttf

101 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9ogUI.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9ogUI.woff

96 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9ogUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9ogUE.ttf

102 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUI.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUI.woff

103 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUE.ttf

103 ms

Logo-Ecodena.jpg

Logo-Ecodena.jpg

85 ms

youtube.png

youtube.png

85 ms

hqdefault.jpg

hqdefault.jpg

39 ms

HPIM2679.webp

HPIM2679.webp

255 ms

Ptar_aguas_residuales.jpg

Ptar_aguas_residuales.jpg

665 ms

Plastticos.jpg

Plastticos.jpg

219 ms

Separador-vertical.jpg

Separador-vertical.jpg

162 ms

Grasas_home.jpg

Grasas_home.jpg

244 ms

Aguas-grises.jpg

Aguas-grises.jpg

327 ms

Fitodepuracion_inicio.jpg

Fitodepuracion_inicio.jpg

420 ms

Sin-titulo-1.png

Sin-titulo-1.png

379 ms

Sin-titulo-2-1.png

Sin-titulo-2-1.png

416 ms

Sin-titulo-3.png

Sin-titulo-3.png

421 ms

Sin-titulo-4.png

Sin-titulo-4.png

411 ms

Sin-titulo-5.png

Sin-titulo-5.png

555 ms

Sin-titulo-6.png

Sin-titulo-6.png

575 ms

logo-footer.png

logo-footer.png

500 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

84 ms

Accessibility Review

ecodena.com.mx accessibility score

86

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

ecodena.com.mx best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ecodena.com.mx SEO score

84

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecodena.com.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 Ecodena.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

ecodena.com.mx

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