Tools & Wizards About Us
izzi.mx screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    31% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 90% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

izzi.mx

Paquetes de Internet y Llamadas ilimitadas con izzi ¡Aprovecha!

Page Load Speed

4.3 sec in total

First Response

277 ms

Resources Loaded

3.4 sec

Page Rendered

652 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 277 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

izzi.mx performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value22.4 s

0/100

10%

TBT (Total Blocking Time)

Value29,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value39.4 s

0/100

10%

Network Requests Diagram

www.izzi.mx

277 ms

home

253 ms

style.css

195 ms

css

74 ms

modernizr.min.js

342 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 58% of them (69 requests) were addressed to the original Izzi.mx, 7% (8 requests) were made to Pixel.mathtag.com and 4% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Izzi.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (29%)

Content Size

3.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 129.1 kB

  • Original 151.2 kB
  • After minification 127.9 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 23.3 kB, which is 15% 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 129.1 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 207.7 kB

  • Original 2.7 MB
  • After minification 2.5 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. Izzi images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 347.3 kB

  • Original 546.6 kB
  • After minification 522.5 kB
  • After compression 199.3 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 347.3 kB or 64% of the original size.

CSS Optimization

-88%

Potential reduce by 409.7 kB

  • Original 463.5 kB
  • After minification 342.9 kB
  • After compression 53.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. Izzi.mx needs all CSS files to be minified and compressed as it can save up to 409.7 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (43%)

Requests Now

106

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 106 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 32 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.izzi.mx

www.izzi.mx

277 ms

home

home

253 ms

style.css

style.css

195 ms

css

css

74 ms

modernizr.min.js

modernizr.min.js

342 ms

jquery.min.js

jquery.min.js

508 ms

placeholder.js

placeholder.js

126 ms

header.js

header.js

299 ms

jquery.cookie.js

jquery.cookie.js

233 ms

underscore-min.js

underscore-min.js

62 ms

api.js

api.js

65 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

92 ms

home.js

home.js

1124 ms

jquery.autocomplete.js

jquery.autocomplete.js

154 ms

popup.js

popup.js

173 ms

footer.js

footer.js

227 ms

loader.js

loader.js

236 ms

gtm.js

gtm.js

244 ms

recaptcha__en.js

recaptcha__en.js

190 ms

Satellite

Satellite

166 ms

Satellite

Satellite

416 ms

Satellite

Satellite

183 ms

Satellite

Satellite

392 ms

Satellite

Satellite

165 ms

Satellite

Satellite

329 ms

Satellite

Satellite

215 ms

Satellite

Satellite

340 ms

Satellite

Satellite

644 ms

Satellite

Satellite

485 ms

Satellite

Satellite

471 ms

Satellite

Satellite

570 ms

Satellite

Satellite

545 ms

banner-app-2.png

banner-app-2.png

586 ms

banner-app-phone-2.png

banner-app-phone-2.png

656 ms

Satellite

Satellite

632 ms

Satellite

Satellite

766 ms

Satellite

Satellite

845 ms

Satellite

Satellite

846 ms

Satellite

Satellite

847 ms

Satellite

Satellite

765 ms

Satellite

Satellite

1272 ms

Satellite

Satellite

904 ms

Satellite

Satellite

947 ms

Satellite

Satellite

894 ms

Satellite

Satellite

969 ms

Satellite

Satellite

981 ms

Satellite

Satellite

1026 ms

Satellite

Satellite

1062 ms

Satellite

Satellite

1114 ms

Satellite

Satellite

1129 ms

Satellite

Satellite

1084 ms

Satellite

Satellite

1193 ms

Satellite

Satellite

1151 ms

i.js

i.js

172 ms

831d7f420b079a7e41295f416c7141393cec4032.2.js

831d7f420b079a7e41295f416c7141393cec4032.2.js

200 ms

Satellite

Satellite

1223 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

184 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

223 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

279 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

333 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

332 ms

ciudadesHeaderGpon

ciudadesHeaderGpon

1378 ms

Satellite

Satellite

1060 ms

Satellite

Satellite

1067 ms

s

s

131 ms

s

s

156 ms

e

e

154 ms

Satellite

Satellite

1063 ms

analytics.js

analytics.js

210 ms

conversion_async.js

conversion_async.js

255 ms

fbds.js

fbds.js

251 ms

sfct.js

sfct.js

414 ms

tm39152.js

tm39152.js

336 ms

activityi;src=4630324;type=homeh0;cat=homey0;ord=4221653129882;~oref=https%3A%2F%2Fwww.izzi.mx%2Fhome

activityi;src=4630324;type=homeh0;cat=homey0;ord=4221653129882;~oref=https%3A%2F%2Fwww.izzi.mx%2Fhome

226 ms

img-pop-estado.jpg

img-pop-estado.jpg

1263 ms

espiral.gif

espiral.gif

994 ms

btn-chat.png

btn-chat.png

937 ms

barraColores.png

barraColores.png

932 ms

pop-canales-pin.png

pop-canales-pin.png

913 ms

sprite.png

sprite.png

917 ms

pixel

pixel

102 ms

86 ms

108 ms

118 ms

87 ms

ciudades-bg.png

ciudades-bg.png

871 ms

collect

collect

90 ms

js

js

78 ms

pixel

pixel

18 ms

js

js

67 ms

match-result

match-result

5 ms

15 ms

ga-audiences

ga-audiences

20 ms

19 ms

i.js

i.js

148 ms

usr

usr

209 ms

icon-plus.png

icon-plus.png

715 ms

icon-facebook.png

icon-facebook.png

742 ms

icon-twitter.png

icon-twitter.png

741 ms

icon-g-plus.png

icon-g-plus.png

783 ms

_Incapsula_Resource

_Incapsula_Resource

732 ms

elqCfg.min.js

elqCfg.min.js

129 ms

bx_loader.gif

bx_loader.gif

748 ms

left-arrow.png

left-arrow.png

747 ms

right-arrow.png

right-arrow.png

779 ms

8593.js

8593.js

120 ms

req

req

165 ms

svrGP

svrGP

111 ms

s

s

60 ms

u

u

70 ms

js

js

81 ms

js

js

279 ms

svrGP.aspx

svrGP.aspx

75 ms

img

img

74 ms

iframe

iframe

60 ms

img

img

68 ms

img

img

60 ms

_Incapsula_Resource

_Incapsula_Resource

35 ms

7 ms

Accessibility Review

izzi.mx accessibility score

96

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

Best Practices

izzi.mx best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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: