Tools & Wizards About Us
imexpress.com.mx screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

imexpress.com.mx

compramos su Auto o le Prestamos Dinero por su Auto

Page Load Speed

5.9 sec in total

First Response

1.2 sec

Resources Loaded

4.1 sec

Page Rendered

565 ms

imexpress.com.mx screenshot

About Website

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

Vende tu auto en 59 minutos https://www.youtube.com/watch?v=O9iuZlGFC4o Te explico por qué somos tu mejor opción: Los precios que damos superan los precios de Cualquier Competencia.Te lo Pagamos de ma...

Visit imexpress.com.mx

Key Findings

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

Performance Metrics

imexpress.com.mx performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

26/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value1,990 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.16

73/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

imexpress.com.mx

1246 ms

js

92 ms

mediaelementplayer-legacy.min.css

72 ms

wp-mediaelement.min.css

143 ms

style.min.css

207 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 53% of them (31 requests) were addressed to the original Imexpress.com.mx, 38% (22 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Imexpress.com.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (43%)

Content Size

2.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imexpress.com.mx main page is 2.9 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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 84.5 kB

  • Original 105.9 kB
  • After minification 105.8 kB
  • After compression 21.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 84.5 kB or 80% of the original size.

Image Optimization

-48%

Potential reduce by 1.1 MB

  • Original 2.3 MB
  • After minification 1.2 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, Imexpress needs image optimization as it can save up to 1.1 MB or 48% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 60.2 kB

  • Original 470.2 kB
  • After minification 470.2 kB
  • After compression 410.0 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 60.2 kB or 13% of the original size.

CSS Optimization

-12%

Potential reduce by 4.2 kB

  • Original 36.6 kB
  • After minification 36.6 kB
  • After compression 32.4 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. Imexpress.com.mx needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (71%)

Requests Now

35

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imexpress.com.mx

imexpress.com.mx

1246 ms

js

js

92 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

72 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

143 ms

style.min.css

style.min.css

207 ms

theme.min.css

theme.min.css

205 ms

header-footer.min.css

header-footer.min.css

205 ms

frontend-lite.min.css

frontend-lite.min.css

214 ms

post-6.css

post-6.css

213 ms

swiper.min.css

swiper.min.css

213 ms

post-248.css

post-248.css

274 ms

css

css

57 ms

embed

embed

198 ms

bnxov.css

bnxov.css

268 ms

jquery.min.js

jquery.min.js

409 ms

jquery-migrate.min.js

jquery-migrate.min.js

310 ms

frontend-gtag.min.js

frontend-gtag.min.js

309 ms

2he0l.js

2he0l.js

763 ms

2he0l.js

2he0l.js

692 ms

2he0l.js

2he0l.js

364 ms

m596.js

m596.js

367 ms

hello-frontend.min.js

hello-frontend.min.js

367 ms

e-202419.js

e-202419.js

29 ms

webpack.runtime.min.js

webpack.runtime.min.js

445 ms

frontend-modules.min.js

frontend-modules.min.js

507 ms

waypoints.min.js

waypoints.min.js

444 ms

core.min.js

core.min.js

472 ms

frontend.min.js

frontend.min.js

507 ms

LOGOTIPO-IMEXPRESS.png

LOGOTIPO-IMEXPRESS.png

769 ms

3-1024x640.png

3-1024x640.png

1135 ms

CEL1.png

CEL1.png

1038 ms

1-1024x657.jpeg

1-1024x657.jpeg

774 ms

22.png

22.png

1153 ms

9-1024x653.png

9-1024x653.png

1287 ms

LOGO3.png

LOGO3.png

1103 ms

js

js

61 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

61 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

77 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

78 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

77 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

78 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

77 ms

5aUu9_-1phKLFgshYDvh6Vwt5alOqEp2jg.ttf

5aUu9_-1phKLFgshYDvh6Vwt5alOqEp2jg.ttf

72 ms

5aUz9_-1phKLFgshYDvh6Vwt7VptuA.ttf

5aUz9_-1phKLFgshYDvh6Vwt7VptuA.ttf

89 ms

5aUu9_-1phKLFgshYDvh6Vwt5fFPqEp2jg.ttf

5aUu9_-1phKLFgshYDvh6Vwt5fFPqEp2jg.ttf

90 ms

5aUt9_-1phKLFgshYDvh6Vwt5Tldv21W.ttf

5aUt9_-1phKLFgshYDvh6Vwt5Tldv21W.ttf

89 ms

5aUu9_-1phKLFgshYDvh6Vwt5eFIqEp2jg.ttf

5aUu9_-1phKLFgshYDvh6Vwt5eFIqEp2jg.ttf

89 ms

5aUu9_-1phKLFgshYDvh6Vwt5f1LqEp2jg.ttf

5aUu9_-1phKLFgshYDvh6Vwt5f1LqEp2jg.ttf

90 ms

5aUu9_-1phKLFgshYDvh6Vwt5dlKqEp2jg.ttf

5aUu9_-1phKLFgshYDvh6Vwt5dlKqEp2jg.ttf

89 ms

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHmZPPq4fy.ttf

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHmZPPq4fy.ttf

96 ms

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHq5PPq4fy.ttf

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHq5PPq4fy.ttf

96 ms

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSH9ZPPq4fy.ttf

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSH9ZPPq4fy.ttf

96 ms

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHK5PPq4fy.ttf

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHK5PPq4fy.ttf

96 ms

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHq5LPq4fy.ttf

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHq5LPq4fy.ttf

96 ms

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHdZTPq4fy.ttf

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHdZTPq4fy.ttf

96 ms

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHTJTPq4fy.ttf

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHTJTPq4fy.ttf

121 ms

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHK5TPq4fy.ttf

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHK5TPq4fy.ttf

120 ms

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHApTPq4fy.ttf

i7dZIFdwYjGaAMFtZd_QA3xXSKZqhr-TenSHApTPq4fy.ttf

120 ms

Accessibility Review

imexpress.com.mx accessibility score

85

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

imexpress.com.mx best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

imexpress.com.mx SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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

imexpress.com.mx

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