4.3 sec in total
1.2 sec
2.9 sec
205 ms
Visit store.yellowkorner.com now to see the best up-to-date Store Yellow Korner content for Germany and also check out these interesting facts you probably never knew about store.yellowkorner.com
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 store.yellowkorner.comWe analyzed Store.yellowkorner.com page load time and found that the first response time was 1.2 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
store.yellowkorner.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value9.2 s
1/100
25%
Value9.1 s
13/100
10%
Value6,290 ms
0/100
30%
Value0.148
76/100
15%
Value16.0 s
6/100
10%
1244 ms
161 ms
167 ms
247 ms
240 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 28% of them (33 requests) were addressed to the original Store.yellowkorner.com, 29% (34 requests) were made to Yellowkorner.com and 17% (20 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Store.yellowkorner.com.
Page size can be reduced by 1.4 MB (64%)
2.2 MB
777.3 kB
In fact, the total size of Store.yellowkorner.com main page is 2.2 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. 70% of websites need less resources to load. Javascripts take 907.2 kB which makes up the majority of the site volume.
Potential reduce by 293.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 92.6 kB, which is 29% 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 293.2 kB or 91% of the original size.
Potential reduce by 18.5 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. Store Yellow Korner images are well optimized though.
Potential reduce by 623.7 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 623.7 kB or 69% of the original size.
Potential reduce by 468.4 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. Store.yellowkorner.com needs all CSS files to be minified and compressed as it can save up to 468.4 kB or 85% of the original size.
Number of requests can be reduced by 75 (71%)
106
31
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Store 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 35 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
store.yellowkorner.com
1244 ms
main.css
161 ms
normalize.min.css
167 ms
main_yk.css
247 ms
bootstrap_yk.css
240 ms
jquery-ui_yk.min.css
170 ms
override_yk.css
233 ms
owl.carousel_yk.css
320 ms
main.css
343 ms
bootstrap.css
351 ms
override.css
261 ms
modernizr-2.6.2.min.js
262 ms
jquery-1.9.1.min.js
379 ms
bootstrap.min.js
287 ms
main.js
377 ms
jquery-migrate-1.2.1.min.js
6 ms
js
33 ms
markerclustererv1.1.js
348 ms
markerwithlabel_packed.js
421 ms
jquery-ui.min.js
424 ms
jquery.ui.touch-punch.min.js
430 ms
jquery.easing.js
481 ms
jquery.ui.totop.js
482 ms
jquery.mousewheel.js
489 ms
deBouncer.js
558 ms
owl.carousel_yk.min.js
639 ms
bootstrap-transition.js
559 ms
bootstrap-tab.js
636 ms
bootstrap-button.js
644 ms
bootstrap-typeahead.js
651 ms
jquery.blockUI.js
717 ms
gtm.js
52 ms
logo.png
112 ms
icon-phone-black.png
103 ms
icon-mail-black.png
103 ms
be.png
102 ms
icon-cart.png
111 ms
menu-button@2x.png
128 ms
icon-menu-horizontal.png
159 ms
icon-menu-square.png
177 ms
icon-menu-vertical.png
177 ms
icon-menu-panoramic.png
212 ms
10.png
202 ms
1.png
211 ms
2.png
236 ms
3.png
255 ms
6.png
258 ms
11.png
288 ms
collection-yk.png
311 ms
icon-phone.png
298 ms
icon-mail.png
313 ms
icon-mail-white.png
334 ms
icon-locator@2x.png
343 ms
Marker.png
422 ms
en_GB.png
488 ms
fr_FR.png
488 ms
de_DE.png
489 ms
es_ES.png
489 ms
nl_NL.png
576 ms
sv_SE.png
576 ms
icon-search.png
314 ms
icon-locator-sprite.png
364 ms
conversion_async.js
18 ms
analytics.js
6 ms
collect
26 ms
48 ms
collect
67 ms
47 ms
ga-audiences
24 ms
btn-arrow.png
259 ms
common.js
26 ms
util.js
28 ms
controls.js
26 ms
places_impl.js
26 ms
fago-webfont.woff
351 ms
collect
38 ms
powered-by-google-on-white3.png
31 ms
autocomplete-icons.png
27 ms
collect
14 ms
twitter.png
136 ms
facebook.png
132 ms
map.js
29 ms
drag_cross_67_16.png
29 ms
marker.js
27 ms
overlay.js
28 ms
FagoCorrSerifWeb-Bold.woff
308 ms
FagoCorrSerifWeb-Bold.woff
306 ms
FagoCorrSerifWeb-Bold.woff
192 ms
StaticMapService.GetMapImage
230 ms
onion.js
32 ms
openhand_8_8.cur
24 ms
ViewportInfoService.GetViewportInfo
119 ms
stats.js
116 ms
transparent.png
61 ms
css
32 ms
StaticMapService.GetMapImage
174 ms
google4.png
57 ms
mapcnt6.png
111 ms
tmapctrl.png
33 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
27 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
28 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
28 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
29 ms
cb_scout5.png
31 ms
tmapctrl4.png
31 ms
imgs8.png
31 ms
vt
22 ms
vt
104 ms
vt
104 ms
vt
104 ms
vt
105 ms
vt
105 ms
vt
106 ms
vt
105 ms
vt
106 ms
Marker-shadow.png
82 ms
vt
35 ms
AuthenticationService.Authenticate
198 ms
store.yellowkorner.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
store.yellowkorner.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
store.yellowkorner.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Store.yellowkorner.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Store.yellowkorner.com 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.
store.yellowkorner.com
Open Graph description is not detected on the main page of Store 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: