Report Summary

  • 22

    Performance

    Renders faster than
    41% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

yellowkorner.de

YellowKorner : Photographie d’art · Galerie Art · Achat Photo en ligne

Page Load Speed

4.1 sec in total

First Response

19 ms

Resources Loaded

2.3 sec

Page Rendered

1.8 sec

yellowkorner.de screenshot

About Website

Welcome to yellowkorner.de homepage info - get ready to check Yellow Korner best content right away, or after learning these important things about yellowkorner.de

Des photos exclusives en tirages limités et numérotés aux galeries et photographies d'art, découvrez tout l'univers artistique de YellowKorner !

Visit yellowkorner.de

Key Findings

We analyzed Yellowkorner.de page load time and found that the first response time was 19 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

yellowkorner.de performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value3,330 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.148

76/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

home

19 ms

polyfill.min.js

101 ms

lazyload.js

10 ms

lib.js

31 ms

main.js

41 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yellowkorner.de, 7% (5 requests) were made to Google-analytics.com and 4% (3 requests) were made to Storage.googleapis.com. The less responsive or slowest element that took the longest time to load (692 ms) relates to the external source Tau.collect.igodigital.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.1 kB (14%)

Content Size

1.1 MB

After Optimization

931.1 kB

In fact, the total size of Yellowkorner.de main page is 1.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. Images take 809.0 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 150.9 kB

  • Original 176.6 kB
  • After minification 150.2 kB
  • After compression 25.7 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 26.4 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 150.9 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 2.4 kB

  • Original 809.0 kB
  • After minification 806.7 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. Yellow Korner images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 593 B

  • Original 48.7 kB
  • After minification 48.7 kB
  • After compression 48.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 295 B

  • Original 50.9 kB
  • After minification 50.9 kB
  • After compression 50.6 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. Yellowkorner.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (48%)

Requests Now

63

After Optimization

33

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

Accessibility Review

yellowkorner.de accessibility score

76

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

Some elements have a [tabindex] value greater than 0

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

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

SEO Factors

yellowkorner.de SEO score

77

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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