Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

yohoo.de

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

Page Load Speed

2.3 sec in total

First Response

121 ms

Resources Loaded

1 sec

Page Rendered

1.2 sec

About Website

Click here to check amazing Yohoo content. Otherwise, check out these important facts you probably never knew about yohoo.de

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

Visit yohoo.de

Key Findings

We analyzed Yohoo.de page load time and found that the first response time was 121 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

yohoo.de performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value4,830 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

yohoo.de

121 ms

www.yahoo.com

770 ms

5dd1a04710639bfe.css

12 ms

9c17b329302ed0d3.css

17 ms

a38112e44947464f.css

21 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yohoo.de, 62% (48 requests) were made to S.yimg.com and 36% (28 requests) were made to Yahoo.com. The less responsive or slowest element that took the longest time to load (770 ms) relates to the external source Yahoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 643.7 kB (22%)

Content Size

2.9 MB

After Optimization

2.3 MB

In fact, the total size of Yohoo.de 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 622.7 kB

  • Original 733.0 kB
  • After minification 732.9 kB
  • After compression 110.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 622.7 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 15 B

  • Original 1.9 MB
  • After minification 1.9 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. Yohoo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 454 B

  • Original 292.3 kB
  • After minification 292.3 kB
  • After compression 291.8 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

-90%

Potential reduce by 20.6 kB

  • Original 22.9 kB
  • After minification 2.4 kB
  • After compression 2.3 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. Yohoo.de needs all CSS files to be minified and compressed as it can save up to 20.6 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (31%)

Requests Now

75

After Optimization

52

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

Accessibility Review

yohoo.de accessibility score

84

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

yohoo.de 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

yohoo.de 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 Yohoo.de 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 Yohoo.de 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

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