Tools & Wizards About Us
izzi.mx screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

izzi.mx

Paquetes de Internet y Llamadas ilimitadas con izzi ¡Aprovecha!

Page Load Speed

2.7 sec in total

First Response

96 ms

Resources Loaded

2.3 sec

Page Rendered

349 ms

izzi.mx screenshot

About Website

Welcome to izzi.mx homepage info - get ready to check Izzi best content for Mexico right away, or after learning these important things about izzi.mx

Navega, trabaja desde casa y llama a todos tus amigos sin interrupciones. Contrata ya mismo tu plan con izzi.

Visit izzi.mx

Key Findings

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

Performance Metrics

izzi.mx performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value23.5 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value6,880 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

izzi.mx

96 ms

izzi.mx

96 ms

www.izzi.mx

39 ms

www.izzi.mx

92 ms

home

221 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 55% of them (29 requests) were addressed to the original Izzi.mx, 15% (8 requests) were made to Web.izzidigital.mx and 6% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (958 ms) belongs to the original domain Izzi.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 325.8 kB (16%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Izzi.mx main page is 2.0 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 823.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 178.6 kB

  • Original 198.9 kB
  • After minification 135.2 kB
  • After compression 20.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 63.6 kB, which is 32% 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 178.6 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 50.0 kB

  • Original 823.5 kB
  • After minification 773.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. Izzi images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 54.0 kB

  • Original 784.7 kB
  • After minification 784.7 kB
  • After compression 730.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-24%

Potential reduce by 43.2 kB

  • Original 178.1 kB
  • After minification 178.0 kB
  • After compression 134.9 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. Izzi.mx needs all CSS files to be minified and compressed as it can save up to 43.2 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (42%)

Requests Now

38

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

izzi.mx

izzi.mx

96 ms

izzi.mx

izzi.mx

96 ms

www.izzi.mx

www.izzi.mx

39 ms

www.izzi.mx

www.izzi.mx

92 ms

home

home

221 ms

style.css

style.css

693 ms

js

js

57 ms

main.min.js

main.min.js

543 ms

api.js

api.js

43 ms

ac.js

ac.js

234 ms

gtm.js

gtm.js

266 ms

stormcaster.js

stormcaster.js

264 ms

,

,

49 ms

izzi-dark-colored.svg

izzi-dark-colored.svg

264 ms

Doodle_INSTITUCIONAL.png

Doodle_INSTITUCIONAL.png

264 ms

heygoogle-large-badge.svg

heygoogle-large-badge.svg

580 ms

chromecast-large-badge.svg

chromecast-large-badge.svg

310 ms

googleplay-large-badge.png

googleplay-large-badge.png

379 ms

youtube-large-badge.svg

youtube-large-badge.svg

554 ms

izzi-kids.svg

izzi-kids.svg

383 ms

izzi-go-app.svg

izzi-go-app.svg

379 ms

linea-izzi.svg

linea-izzi.svg

384 ms

izzi-light.svg

izzi-light.svg

444 ms

whatsapp-icon.svg

whatsapp-icon.svg

443 ms

beacon.js

beacon.js

297 ms

home

home

339 ms

symbol-defs.svg

symbol-defs.svg

420 ms

home-lower-decorator.png

home-lower-decorator.png

793 ms

home-upper-decorator.png

home-upper-decorator.png

509 ms

febrero-nba-stage.jpg

febrero-nba-stage.jpg

958 ms

account-addon-decoration.svg

account-addon-decoration.svg

510 ms

recaptcha__en.js

recaptcha__en.js

70 ms

elqCfg.min.js

elqCfg.min.js

171 ms

Poppins-Light.woff

Poppins-Light.woff

499 ms

Poppins-Regular.woff

Poppins-Regular.woff

326 ms

Poppins-Medium.woff

Poppins-Medium.woff

355 ms

Poppins-SemiBold.woff

Poppins-SemiBold.woff

699 ms

Poppins-Bold.woff

Poppins-Bold.woff

461 ms

global.css

global.css

38 ms

bundle.css

bundle.css

60 ms

index.css

index.css

63 ms

bundle.js

bundle.js

74 ms

main.min.js

main.min.js

128 ms

alasql.min.js

alasql.min.js

73 ms

googleAnalytics4.js

googleAnalytics4.js

117 ms

fallback

fallback

32 ms

fallback

fallback

35 ms

fallback__ltr.css

fallback__ltr.css

7 ms

css

css

41 ms

svrGP

svrGP

131 ms

logo_48.png

logo_48.png

4 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

16 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

20 ms

Accessibility Review

izzi.mx accessibility score

95

Accessibility Issues

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

izzi.mx SEO score

85

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

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

izzi.mx

Open Graph description is not detected on the main page of Izzi. 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: