12 sec in total
586 ms
10.4 sec
1.1 sec
Click here to check amazing Yellow content for Bulgaria. Otherwise, check out these important facts you probably never knew about yellow.bg
Магазин за обувки Zebra-online - онлайн дамски, немски, мъжки, детски обувки и чанти. Предлагаме ежедневни и официални боти, ботуши, сандали и чехли.
Visit yellow.bgWe analyzed Yellow.bg page load time and found that the first response time was 586 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yellow.bg performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value17.1 s
0/100
25%
Value13.8 s
1/100
10%
Value5,310 ms
0/100
30%
Value1
2/100
15%
Value18.8 s
3/100
10%
586 ms
615 ms
1750 ms
112 ms
230 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Yellow.bg, 73% (93 requests) were made to Zebra-online.com and 11% (14 requests) were made to Demo.zebra-online.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Zebra-online.com.
Page size can be reduced by 228.8 kB (8%)
2.9 MB
2.7 MB
In fact, the total size of Yellow.bg 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. 55% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 97.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 97.2 kB or 83% of the original size.
Potential reduce by 120.0 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 images are well optimized though.
Potential reduce by 11.4 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 11.4 kB or 14% of the original size.
Potential reduce by 143 B
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. Yellow.bg has all CSS files already compressed.
Number of requests can be reduced by 35 (28%)
124
89
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yellow. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
yellow.bg
586 ms
www.yellow.bg
615 ms
www.zebra-online.com
1750 ms
analytics.js
112 ms
api.js
230 ms
sdk.js
190 ms
fbevents.js
226 ms
zebra.gif
669 ms
women.png
648 ms
sub-women.png
647 ms
paint-bucket.png
672 ms
men.png
618 ms
sub-men.png
626 ms
kids.png
854 ms
sub-kids.png
877 ms
chanti.png
873 ms
sub-chanti.png
872 ms
stelki.png
878 ms
sub-stelki.png
886 ms
poddrujka.png
1394 ms
sub-poddrujka.png
1394 ms
sale.png
1397 ms
sub-sale.png
1394 ms
menu-fb.png
1382 ms
menu-insta.png
1389 ms
heart.png
1724 ms
2fbcffbb5d42584b0969ebe661a1d0febe8c807c.jpg
2282 ms
a9c7ed04168ad47df773b9ef6ce968bbd06abaeb.jpg
2169 ms
new.png
1740 ms
8cfad93378e573f5019ecd36c2ee84d14bdd3d84.jpg
2060 ms
3ec2cf452780f79244e1e829def23d1ee293bab4.jpg
2060 ms
e149645dcb68d3d34f7cd1ac009991e704768f10.jpg
2411 ms
b005527bb56993302ca9a0dcf8aa37c907db3c42.jpg
2413 ms
51d4387a91b106069e7f97d36a5ed57ef6281874.jpg
2623 ms
0851395f55c1309d45e42c4ad37d48bed2974073.jpg
2647 ms
df2b04c4a72a8ea2466ce8be6177f1e9953a69ff.jpg
2624 ms
2caa6a8cfafcf362404cf6001c2dc4b6769e3231.jpg
2842 ms
promo-home.png
2767 ms
84e2febf1bf8eec0f2b58ba05940236f33d69e6c.jpg
3004 ms
collect
76 ms
m8872sch-1-160971.JPG
854 ms
jquery-1.11.2.min.js
3024 ms
slick.min.js
2922 ms
webfont.js
214 ms
minified.js
3075 ms
92d63014b6dcdc8af0cb88158a8268ed091cb51e.png
748 ms
cm6534ch-1-161130.JPG
1131 ms
cm6534z-1-161134.JPG
1130 ms
cm6534tbj-1-161136.JPG
1131 ms
cm6534k-1-161140.JPG
1131 ms
23f4a4311d45ce7d5e876ca97ecc6f0b49f80627.png
1304 ms
cm6534chv-1-161138.JPG
1432 ms
ch6801-5ch-1-161108.JPG
1534 ms
ch6801-5z-1-161110.JPG
1535 ms
ch6801-5sv-1-161112.JPG
1534 ms
ch6801-5bj-1-161114.JPG
1554 ms
ch6808-2ch-1-161084.JPG
1977 ms
ch6808-2sr-1-161086.JPG
1987 ms
scripts.js
3063 ms
sdk.js
116 ms
asset_composer.js
371 ms
collect
370 ms
recaptcha__en.js
369 ms
1562080237340357
218 ms
334 ms
ga-audiences
116 ms
jquery.ui.touch-punch.min.js
2592 ms
0a81472634b385f2c24490fc069911dcfe09d763.jpg
2987 ms
172b4f694268d5e50c1881f49d241486512e02a8.jpg
3089 ms
5abee7ef61085f2853b8ee54bb3be9b29c3b0353.png
3495 ms
8336c28ad12dd97fa8d7ad3211d8f141b8ad77d9.jpg
3111 ms
8326c0506fe1eb9e78a583f55b5cdc118e39e8c5.jpg
3005 ms
4uiqgsFRqqdVb08PIShXNLEYdx31rJtN
150 ms
a9ed53490cf91e0f58af7d57df8466f37229f7c9.jpg
2704 ms
56736b19826397eb566b3aece59b82697c8e7e9e.png
3162 ms
9bb24f7b857fa01d9023385d82e1c247e11214dd.png
3182 ms
d5ff565e3e7c7142bb585e1008be049a29a4152d.png
3116 ms
de3b65e4a3696ab89eec983972b178e5bb135451.png
3168 ms
bbd9e94b27e80203b98e62df39bae1d8d3a79736.png
3326 ms
widget_v2.334.js
31 ms
__$$__stringtable_lang_bg.js
160 ms
cc20615f4257879c4801d229e6f6ce74df30e484.png
2961 ms
64e7772a272cb21cba457411a73b22883ffa25ce.png
3091 ms
c6a631d825a5aba9b841f776b574213385effe00.png
3124 ms
68303ad258642911f0f8e365123831649166feaa.png
3118 ms
6c8efb0660edd4bbee83581d306f2e88eaf3d655.png
3167 ms
fd7a9313500e85ebca76e69efe1983edb43953d3.png
3296 ms
52d20be29aae59804138f9649c41c1e429e04f7b.png
2976 ms
cdc49fb3fa93bc89aa7ed83f59d97b6785409e67.png
3093 ms
avatar_simple_visitor.png
155 ms
hbABjQBLsAhQWLEBAY5ZsUYGK1ghsBBZS7AUUlghsIBZHbAGK1xYWbAUKwAAAAFcPYvrAAA=
4 ms
1bed5dc27698113c0c522d50f70d526fe32d668c.gif
2789 ms
f9b547682ab6c85c46d51f1fb3a702a0a90111a9.png
3162 ms
46da063217b9a8fd2173cd1c2953e1cab90f8a11.png
2949 ms
71f987ca817c155ffda2532c39ffe1f42ed1f3af.png
2861 ms
1bbbfa13a96156191f2a7d88218ec9aa08f1bf49.png
2767 ms
197f44bf8451f5831b8c7795cc0249c3429326f3.png
2874 ms
45a19e82820840c6627b8698c6d9b969875ee27d.png
2698 ms
5e2646021c88317e5948f1c74f6d9259ff26ac5d.png
3060 ms
2169199ed73ff697663e17a6b1d148c3e139e219.png
2972 ms
5f01798cf2f2799c4790b47ab44777b390792f1c.png
2751 ms
72b6bacc0140143d835e6c410c5db7b001099635.jpg
2722 ms
c14bb273c6df270b1febcbab2274e4580269028e.png
2659 ms
36e22e1b30f7d169b28dde2ddab1f533b605ec26.png
2654 ms
f8451b1483a2092eb0ceb2fc144054c527cb2189.png
2865 ms
1eda5153cfcfea3d9766b91b28e1c88df94fc459.png
2768 ms
a85c9bfa33633fbb183c29d38ca207e54ed1cab6.png
2785 ms
minified.css
2780 ms
slick.css
2454 ms
minified_style.css
2552 ms
c2daeef291d4bda1e86797d185dd51906abfcf72.png
2645 ms
8fb36c2dfa547514b5bcfe50b40bb7136e3040f1.png
2748 ms
5e353498121eb4a1864c795ef2c0453a74bb3915.jpg
2615 ms
a9fa288ea86014f7f4bc4ec3eca8c7c1232aecf9.png
2580 ms
32a9e4d1cc1747a6e2a51ceb5884339ce769bb3e.png
2582 ms
truck.png
2467 ms
loader2.gif
2699 ms
tick.jpg
2593 ms
cross.jpg
2598 ms
zebra-f.png
2503 ms
round-btn-red-menu.png
760 ms
basket.png
805 ms
round-btn-red-close.png
897 ms
search.png
924 ms
chevron-forward.png
997 ms
rtr-bg.png
1044 ms
round-btn-red-up.png
1119 ms
css
177 ms
yellow.bg 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
Form elements do not have associated labels
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yellow.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
yellow.bg SEO score
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
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yellow.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Yellow.bg 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.
yellow.bg
Open Graph description is not detected on the main page of Yellow. 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: