6.5 sec in total
571 ms
3.2 sec
2.7 sec
Welcome to yes.pl homepage info - get ready to check YES best content for Poland right away, or after learning these important things about yes.pl
Przeglądaj wyjątkową kolekcję biżuterii ✓ Wyselekcjonowana biżuteria od najlepszych projektantów ✓ YES jubiler z ponad 30 letnią tradycją! ✓ Wejdź teraz!
Visit yes.plWe analyzed Yes.pl page load time and found that the first response time was 571 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
yes.pl performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value12.5 s
0/100
25%
Value12.5 s
3/100
10%
Value3,370 ms
2/100
30%
Value0.338
33/100
15%
Value27.2 s
0/100
10%
571 ms
194 ms
289 ms
575 ms
446 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 29% of them (17 requests) were addressed to the original Yes.pl, 34% (20 requests) were made to Cdn.yes.pl and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cdn.yes.pl.
Page size can be reduced by 1.2 MB (46%)
2.6 MB
1.4 MB
In fact, the total size of Yes.pl main page is 2.6 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 973.3 kB which makes up the majority of the site volume.
Potential reduce by 65.8 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 65.8 kB or 77% of the original size.
Potential reduce by 21.4 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. YES images are well optimized though.
Potential reduce by 633.9 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 633.9 kB or 66% of the original size.
Potential reduce by 454.0 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. Yes.pl needs all CSS files to be minified and compressed as it can save up to 454.0 kB or 86% of the original size.
Number of requests can be reduced by 19 (37%)
51
32
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of YES. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
yes.pl
571 ms
jquery-1.10.2.min.js
194 ms
prototype.min.js
289 ms
base.js
575 ms
styles.css
446 ms
css
23 ms
tracker.js
313 ms
ld.js
24 ms
product.js
232 ms
priceformat.js
210 ms
app.js
299 ms
main.js
310 ms
home.js
331 ms
conversion.js
13 ms
sm.js
346 ms
ns.html
66 ms
bizuteria_o.jpg
343 ms
diamenty_o.jpg
343 ms
zareczyny_o.jpg
342 ms
slub_o.jpg
342 ms
kolekcje_o.jpg
343 ms
zegarki_o.jpg
343 ms
pavoni-srebrny-naszyjnik-komplet-awcl170-ancl238_3.jpg
1341 ms
walentynki-bg01.jpg
1386 ms
yes-banner-home-151220-kk16-mob.jpg
1348 ms
gtm.js
59 ms
sprite.png
204 ms
walentynki-prod01.png
1323 ms
yes-banner-home-150626-kk01-txt.png
1281 ms
yes-home-mozaika-151223-wiktorianska.jpg
1320 ms
walentynki-box.jpg
1321 ms
yes-home-mozaika-151223-zodiak.jpg
1320 ms
yes-home-mozaika-151223-projaktanci.jpg
1321 ms
yes-home-mozaika-151223-zegarek.jpg
1322 ms
galeria-yes-box.jpg
1322 ms
zloto-inwestycyjne-box.jpg
1322 ms
yes-home-mozaika-160106-salonyyes-01.jpg
1322 ms
logo.png
144 ms
151105_baner_yes_buttont.png
144 ms
stars.png
143 ms
fontello.woff
143 ms
andradepro-rg-webfont.woff
201 ms
iframe_api
128 ms
www-widgetapi.js
63 ms
sprite-social-icons.png
104 ms
r.gif
995 ms
event
25 ms
zanox.js
1027 ms
971 ms
event
972 ms
dc.js
962 ms
hotjar-45190.js
962 ms
yes-banner-home-150626-kk01-bg.jpg
374 ms
58 ms
111 ms
__utm.gif
29 ms
070C55CF000A422E0FF8
215 ms
ga-audiences
28 ms
yes.pl 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
Form elements do not have associated labels
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
yes.pl 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
yes.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
PL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yes.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it does not match the claimed English language. Our system also found out that Yes.pl 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.
yes.pl
Open Graph description is not detected on the main page of YES. 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: