Tools & Wizards About Us
yahoo.sh screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% 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

  • 85

    SEO

    Google-friendlier than
    55% of websites

yahoo.sh

Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos

Page Load Speed

1.1 sec in total

First Response

50 ms

Resources Loaded

679 ms

Page Rendered

367 ms

yahoo.sh screenshot

About Website

Click here to check amazing Yahoo content. Otherwise, check out these important facts you probably never knew about yahoo.sh

Latest news coverage, email, free stock quotes, live scores and video are just the beginning. Discover more every day at Yahoo!

Visit yahoo.sh

Key Findings

We analyzed Yahoo.sh page load time and found that the first response time was 50 ms and then it took 1 sec 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.sh performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value3,850 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

yahoo.sh

50 ms

www.yahoo.com

393 ms

cmp.js

382 ms

tdv2-wafer-utils.customErrorHandler.bcda778b736c3a054af62f437b536e78.js

94 ms

fpDesktop.fe9b7e76f465982f4c53fa4f1153ad7f.js

104 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yahoo.sh, 91% (61 requests) were made to S.yimg.com and 3% (2 requests) were made to Yahoo.com. The less responsive or slowest element that took the longest time to load (393 ms) relates to the external source Yahoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 995.3 kB (48%)

Content Size

2.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yahoo.sh main page is 2.1 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. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 989.6 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 242.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 989.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

  • Original 462.5 kB
  • After minification 460.9 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.1 kB

  • Original 381.2 kB
  • After minification 381.1 kB
  • After compression 377.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 2.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. Yahoo.sh has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (57%)

Requests Now

60

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yahoo.sh

yahoo.sh

50 ms

www.yahoo.com

www.yahoo.com

393 ms

cmp.js

cmp.js

382 ms

tdv2-wafer-utils.customErrorHandler.bcda778b736c3a054af62f437b536e78.js

tdv2-wafer-utils.customErrorHandler.bcda778b736c3a054af62f437b536e78.js

94 ms

fpDesktop.fe9b7e76f465982f4c53fa4f1153ad7f.js

fpDesktop.fe9b7e76f465982f4c53fa4f1153ad7f.js

104 ms

benji-2.1.78.js

benji-2.1.78.js

106 ms

wf-caas-1.36.6.js

wf-caas-1.36.6.js

103 ms

wf-toggle-1.15.4.js

wf-toggle-1.15.4.js

102 ms

react-wafer-featurebar.custom.default.95a7979b4c06295e22960043d003fb49.js

react-wafer-featurebar.custom.default.95a7979b4c06295e22960043d003fb49.js

102 ms

wf-clipboard-copy-1.0.2.js

wf-clipboard-copy-1.0.2.js

106 ms

wf-video-3.1.2.js

wf-video-3.1.2.js

106 ms

wf-bind-1.1.3.js

wf-bind-1.1.3.js

105 ms

wf-text-1.2.0.js

wf-text-1.2.0.js

105 ms

wf-benji-1.2.0.js

wf-benji-1.2.0.js

105 ms

wf-action-1.8.1.js

wf-action-1.8.1.js

108 ms

wf-template-1.4.3.js

wf-template-1.4.3.js

105 ms

wf-menu-1.3.5.js

wf-menu-1.3.5.js

107 ms

wf-fetch-1.19.1.js

wf-fetch-1.19.1.js

107 ms

wf-scrollview-2.23.3.js

wf-scrollview-2.23.3.js

107 ms

wf-beacon-1.3.4.js

wf-beacon-1.3.4.js

107 ms

wf-countdown-1.2.5.js

wf-countdown-1.2.5.js

107 ms

wf-form-1.34.5.js

wf-form-1.34.5.js

110 ms

wf-lightbox-1.10.6.js

wf-lightbox-1.10.6.js

108 ms

wf-native-da-1.0.5.js

wf-native-da-1.0.5.js

107 ms

wf-image-1.4.0.js

wf-image-1.4.0.js

108 ms

wf-rapid-1.10.9.js

wf-rapid-1.10.9.js

108 ms

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

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

107 ms

05784f0.caas-news_web.min.js

05784f0.caas-news_web.min.js

112 ms

cerebro_min.js

cerebro_min.js

37 ms

privacy-choice-control.png

privacy-choice-control.png

42 ms

Regular.woff

Regular.woff

50 ms

Medium.woff

Medium.woff

49 ms

Light.woff

Light.woff

48 ms

ExtraLight.woff

ExtraLight.woff

61 ms

Semibold.woff

Semibold.woff

43 ms

5b42ae20-4b9d-11ef-b6df-deb4691a124d.cf.jpg

5b42ae20-4b9d-11ef-b6df-deb4691a124d.cf.jpg

42 ms

40bb0f60-4bcb-11ef-96ef-3f74d19df1dd.cf.jpg

40bb0f60-4bcb-11ef-96ef-3f74d19df1dd.cf.jpg

39 ms

0fa38dd0-4bb7-11ef-bf5d-6730ca8a80e5.cf.jpg

0fa38dd0-4bb7-11ef-bf5d-6730ca8a80e5.cf.jpg

39 ms

d83d1950-4ba3-11ef-b6f9-b3776dc7cff5.cf.jpg

d83d1950-4ba3-11ef-b6f9-b3776dc7cff5.cf.jpg

40 ms

7b5e4940-4be7-11ef-bff7-5f13ad43b719.cf.jpg

7b5e4940-4be7-11ef-bff7-5f13ad43b719.cf.jpg

49 ms

b726c750-4b55-11ef-935d-4a74396f3b8e.cf.jpg

b726c750-4b55-11ef-935d-4a74396f3b8e.cf.jpg

40 ms

63e5036a0dcbb9b164ad19b3deb7b2b0.cf.jpg

63e5036a0dcbb9b164ad19b3deb7b2b0.cf.jpg

15 ms

trendingNow.yhome-atomic.c9493b0439b3a8ef64a3f6b7f532117c.min.css

trendingNow.yhome-atomic.c9493b0439b3a8ef64a3f6b7f532117c.min.css

7 ms

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

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

6 ms

7e0d244d476695aae2f94fed8e447212.cf.jpg

7e0d244d476695aae2f94fed8e447212.cf.jpg

26 ms

409de3a04ad1c22a7c341ed28ea0663d.cf.jpg

409de3a04ad1c22a7c341ed28ea0663d.cf.jpg

26 ms

61a8ad0d29bc58008cbf6c0971ff8358.cf.jpg

61a8ad0d29bc58008cbf6c0971ff8358.cf.jpg

28 ms

caa8398e265ebbad4fc191ee4f1564d6.cf.jpg

caa8398e265ebbad4fc191ee4f1564d6.cf.jpg

27 ms

d32d8c5cb6ad4fdf1177f706a9f1a6c6.cf.jpg

d32d8c5cb6ad4fdf1177f706a9f1a6c6.cf.jpg

28 ms

fe36cf44a7b14859d15b3f4fcd1371d8.cf.jpg

fe36cf44a7b14859d15b3f4fcd1371d8.cf.jpg

28 ms

2958519b5c7db80a631d56f30dfb95e8.cf.jpg

2958519b5c7db80a631d56f30dfb95e8.cf.jpg

30 ms

8b9988db4e4c3dbb87c6c60ca81c468a.cf.jpg

8b9988db4e4c3dbb87c6c60ca81c468a.cf.jpg

29 ms

5ec31f1023cf4a81cdf2fa9bf8bd5c8c.cf.jpg

5ec31f1023cf4a81cdf2fa9bf8bd5c8c.cf.jpg

30 ms

25f93e50-4b6b-11ef-b9f8-b9ffeac35fdf.cf.jpg

25f93e50-4b6b-11ef-b9f8-b9ffeac35fdf.cf.jpg

29 ms

ba0fea4ddcb9fc9ac569cf2255ce528b.cf.jpg

ba0fea4ddcb9fc9ac569cf2255ce528b.cf.jpg

30 ms

b55f1e924b5900b95185da94f3651f72.cf.jpg

b55f1e924b5900b95185da94f3651f72.cf.jpg

31 ms

170f40e79de4bb37eef98a14a502db49.cf.jpg

170f40e79de4bb37eef98a14a502db49.cf.jpg

33 ms

0a8b3e3e9e6bd3fd8162df95cb2a442a.cf.jpg

0a8b3e3e9e6bd3fd8162df95cb2a442a.cf.jpg

33 ms

analytics-3.54.3.js

analytics-3.54.3.js

30 ms

wf-core-1.65.1.js

wf-core-1.65.1.js

32 ms

homepage-pwa-defer-1.1.6.js

homepage-pwa-defer-1.1.6.js

31 ms

safe.min.js

safe.min.js

31 ms

advertisement_0.0.19.js

advertisement_0.0.19.js

32 ms

cs_1.6.2.js

cs_1.6.2.js

99 ms

evplayer.js

evplayer.js

65 ms

exp.json

exp.json

23 ms

perf-vitals_3.3.0.js

perf-vitals_3.3.0.js

19 ms

Accessibility Review

yahoo.sh accessibility score

85

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.

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

Image elements do not have [alt] attributes

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.sh 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.sh SEO score

85

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yahoo.sh can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Yahoo.sh 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.sh

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: