Tools & Wizards About Us
yahoo.mx screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

yahoo.mx

Yahoo Español | Últimas noticias, Deportes, Finanzas y Mail

Page Load Speed

1000 ms in total

First Response

110 ms

Resources Loaded

664 ms

Page Rendered

226 ms

yahoo.mx screenshot

About Website

Welcome to yahoo.mx homepage info - get ready to check Yahoo best content right away, or after learning these important things about yahoo.mx

Noticias de última hora, correo electrónico, cotizaciones gratuitas de acciones, resultados en vivo, videos y mucho más. ¡Descubre más cada día en Yahoo!

Visit yahoo.mx

Key Findings

We analyzed Yahoo.mx page load time and found that the first response time was 110 ms and then it took 890 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

yahoo.mx performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value6.2 s

42/100

10%

TBT (Total Blocking Time)

Value2,010 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

yahoo.mx

110 ms

mx.yahoo.com

11 ms

espanol.yahoo.com

313 ms

cmp.js

102 ms

tdv2-wafer-utils.customErrorHandler.bcda778b736c3a054af62f437b536e78.js

65 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Yahoo.mx, 89% (54 requests) were made to S.yimg.com and 3% (2 requests) were made to Edge-mcdn.secure.yahoo.com. The less responsive or slowest element that took the longest time to load (313 ms) relates to the external source Espanol.yahoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 879.6 kB (52%)

Content Size

1.7 MB

After Optimization

823.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yahoo.mx main page is 1.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. 60% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 872.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 227.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 872.0 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 3.5 kB

  • Original 306.3 kB
  • After minification 302.8 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. Yahoo images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.0 kB

  • Original 294.2 kB
  • After minification 294.1 kB
  • After compression 290.1 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

-1%

Potential reduce by 36 B

  • Original 3.0 kB
  • After minification 3.0 kB
  • After compression 3.0 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. Yahoo.mx has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (60%)

Requests Now

53

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yahoo.mx

yahoo.mx

110 ms

mx.yahoo.com

mx.yahoo.com

11 ms

espanol.yahoo.com

espanol.yahoo.com

313 ms

cmp.js

cmp.js

102 ms

tdv2-wafer-utils.customErrorHandler.bcda778b736c3a054af62f437b536e78.js

tdv2-wafer-utils.customErrorHandler.bcda778b736c3a054af62f437b536e78.js

65 ms

fpDesktop.150e5ede0d3993fe18e0a62a289784cd.js

fpDesktop.150e5ede0d3993fe18e0a62a289784cd.js

74 ms

benji-2.1.52.js

benji-2.1.52.js

75 ms

wf-clipboard-copy-1.0.2.js

wf-clipboard-copy-1.0.2.js

75 ms

wf-caas-1.36.5.js

wf-caas-1.36.5.js

75 ms

wf-video-3.1.2.js

wf-video-3.1.2.js

75 ms

wf-bind-1.1.3.js

wf-bind-1.1.3.js

74 ms

wf-text-1.2.0.js

wf-text-1.2.0.js

80 ms

wf-toggle-1.15.4.js

wf-toggle-1.15.4.js

79 ms

wf-fetch-1.19.1.js

wf-fetch-1.19.1.js

80 ms

wf-beacon-1.3.4.js

wf-beacon-1.3.4.js

79 ms

wf-scrollview-2.23.0.js

wf-scrollview-2.23.0.js

78 ms

wf-lightbox-1.10.6.js

wf-lightbox-1.10.6.js

79 ms

wf-countdown-1.2.5.js

wf-countdown-1.2.5.js

83 ms

wf-benji-1.2.0.js

wf-benji-1.2.0.js

82 ms

wf-action-1.8.1.js

wf-action-1.8.1.js

83 ms

wf-template-1.4.3.js

wf-template-1.4.3.js

82 ms

wf-menu-1.3.5.js

wf-menu-1.3.5.js

81 ms

wf-form-1.34.5.js

wf-form-1.34.5.js

80 ms

wf-native-da-1.0.5.js

wf-native-da-1.0.5.js

83 ms

wf-image-1.4.0.js

wf-image-1.4.0.js

84 ms

wf-rapid-1.10.8.js

wf-rapid-1.10.8.js

82 ms

react-wafer-stream.custom.default.34fba140d46159f80d116c63459e57e7.js

react-wafer-stream.custom.default.34fba140d46159f80d116c63459e57e7.js

85 ms

9dd8612.caas-news_web.min.js

9dd8612.caas-news_web.min.js

85 ms

cerebro_min.js

cerebro_min.js

36 ms

yahoo_homepage_en-US_s_f_p_bestfit_homepage.png

yahoo_homepage_en-US_s_f_p_bestfit_homepage.png

36 ms

yahoo_homepage_en-US_s_f_w_bestfit_homepage.png

yahoo_homepage_en-US_s_f_w_bestfit_homepage.png

46 ms

header_1x-1479864976616.min.png

header_1x-1479864976616.min.png

45 ms

spritify-sprite-light-fd484ded-e3dce7a4.png

spritify-sprite-light-fd484ded-e3dce7a4.png

47 ms

Medium.woff

Medium.woff

49 ms

Regular.woff

Regular.woff

47 ms

Light.woff

Light.woff

50 ms

ExtraLight.woff

ExtraLight.woff

227 ms

Semibold.woff

Semibold.woff

49 ms

16857150-276c-11ef-aa7b-0eaf0f1d0c48.cf.jpg

16857150-276c-11ef-aa7b-0eaf0f1d0c48.cf.jpg

43 ms

2d5b02c0-2779-11ef-ab37-aea0dd6cf45c.cf.jpg

2d5b02c0-2779-11ef-ab37-aea0dd6cf45c.cf.jpg

41 ms

bc511bb0-274a-11ef-b5db-411d0076c428.cf.jpg

bc511bb0-274a-11ef-b5db-411d0076c428.cf.jpg

42 ms

ce5d67dc969619df447a99afad23e8a8.cf.jpg

ce5d67dc969619df447a99afad23e8a8.cf.jpg

45 ms

5d44b909bb69684daf72e9b7f0712c60.cf.jpg

5d44b909bb69684daf72e9b7f0712c60.cf.jpg

42 ms

51467590-274a-11ef-bdc9-22bda5155712.cf.jpg

51467590-274a-11ef-bdc9-22bda5155712.cf.jpg

34 ms

trendingNow.yhome-atomic.10fc24b3e2792fab7a8e15a52dfe89a0.min.css

trendingNow.yhome-atomic.10fc24b3e2792fab7a8e15a52dfe89a0.min.css

15 ms

trendingNow-flameIcon.yhome-variable.a2368adb8251677d29ac1399a6f34c43.min.css

trendingNow-flameIcon.yhome-variable.a2368adb8251677d29ac1399a6f34c43.min.css

14 ms

analytics-3.54.3.js

analytics-3.54.3.js

35 ms

wf-core-1.65.1.js

wf-core-1.65.1.js

38 ms

homepage-pwa-defer-1.1.6.js

homepage-pwa-defer-1.1.6.js

34 ms

safe.min.js

safe.min.js

62 ms

advertisement_0.0.19.js

advertisement_0.0.19.js

65 ms

cdd799c9897a0bf46848fd9a53cd753d.cf.jpg

cdd799c9897a0bf46848fd9a53cd753d.cf.jpg

63 ms

12180e70-2753-11ef-9d76-7d79ed9b0b54.cf.jpg

12180e70-2753-11ef-9d76-7d79ed9b0b54.cf.jpg

179 ms

98e23bd484801744a237b541f60b7cd7.cf.jpg

98e23bd484801744a237b541f60b7cd7.cf.jpg

182 ms

0caf7be0-22ca-11ef-bff8-71281462ec11.cf.jpg

0caf7be0-22ca-11ef-bff8-71281462ec11.cf.jpg

179 ms

d118c193e8888bca5dc4b9b63a0d5bea.cf.jpg

d118c193e8888bca5dc4b9b63a0d5bea.cf.jpg

180 ms

9125a560-275d-11ef-bfff-7d01e11450bd.cf.jpg

9125a560-275d-11ef-bfff-7d01e11450bd.cf.jpg

182 ms

bf5d5714b3b1ca315bfd34a4da3471d9.cf.jpg

bf5d5714b3b1ca315bfd34a4da3471d9.cf.jpg

180 ms

cs_1.6.0.js

cs_1.6.0.js

161 ms

exp.json

exp.json

46 ms

perf-vitals_3.2.0.js

perf-vitals_3.2.0.js

44 ms

Accessibility Review

yahoo.mx accessibility score

87

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

Page has valid source maps

SEO Factors

yahoo.mx SEO score

100

Search Engine Optimization Advices

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

yahoo.mx

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