4.9 sec in total
345 ms
4.4 sec
227 ms
Click here to check amazing Yonex content. Otherwise, check out these important facts you probably never knew about yonex.pl
Od ponad 70 lat YONEX jest wiodącą firmą produkującą sprzęt sportowy dla takich dyscyplin jak tenis czy badminton. Oficjalny dystrybutor w Polsce.
Visit yonex.plWe analyzed Yonex.pl page load time and found that the first response time was 345 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
yonex.pl performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value7.5 s
4/100
25%
Value7.5 s
26/100
10%
Value920 ms
30/100
30%
Value0.547
13/100
15%
Value13.9 s
10/100
10%
345 ms
572 ms
851 ms
365 ms
241 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Yonex.pl, 63% (48 requests) were made to Yonex.com.pl and 16% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Yonex.com.pl.
Page size can be reduced by 277.5 kB (10%)
2.7 MB
2.5 MB
In fact, the total size of Yonex.pl main page is 2.7 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. 45% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 19.5 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 19.5 kB or 81% of the original size.
Potential reduce by 110.8 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. Yonex images are well optimized though.
Potential reduce by 128.6 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 128.6 kB or 64% of the original size.
Potential reduce by 18.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. Yonex.pl needs all CSS files to be minified and compressed as it can save up to 18.6 kB or 81% of the original size.
Number of requests can be reduced by 26 (36%)
73
47
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yonex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
yonex.pl
345 ms
www.yonex.pl
572 ms
www.yonex.com.pl
851 ms
jquery.js
365 ms
scripts_const.js
241 ms
scripts.js
239 ms
style.css
242 ms
stat.js.php
240 ms
tlo.jpg
1569 ms
foto.php
1064 ms
foto.php
1097 ms
foto.php
1059 ms
foto.php
1064 ms
foto.php
1062 ms
foto.php
1308 ms
foto.php
1428 ms
foto.php
1430 ms
foto.php
1327 ms
17908_ezonedr_belinda_316x80_banner3.jpg
1216 ms
eng_316_80.jpg
1335 ms
ezonexphomepod1.jpg
1428 ms
foto.php
1467 ms
foto.php
1456 ms
foto.php
1548 ms
shm02lx_co_1,wo_215,ho_200,_small.jpg
1551 ms
shm02mx_bl_1,wo_215,ho_200,_small.jpg
1561 ms
nrgz_1,wo_215,ho_200,_small.jpg
1579 ms
vt80etn_np_1,wo_215,ho_200,_small.jpg
1584 ms
vt70etn_1,wo_215,ho_200,_small.jpg
1669 ms
badmintonstringbg66f,wo_215,ho_200,_small.jpg
1672 ms
vcoretourg_1,wo_215,ho_200,_small.jpg
1681 ms
vctf97_1,wo_215,ho_200,_small.jpg
1682 ms
vcoretourf93,wo_215,ho_200,_small.jpg
1699 ms
ptgg125ex,wo_215,ho_200,_small.jpg
1705 ms
face.png
1785 ms
gtm.js
56 ms
header.gif
1772 ms
logo.gif
1781 ms
input.gif
1782 ms
wysz.gif
1798 ms
nav.gif
1803 ms
sep.gif
1885 ms
h6.gif
1889 ms
h6_face.gif
1897 ms
navl.png
1899 ms
analytics.js
5 ms
like.php
188 ms
collect
16 ms
collect
76 ms
likebox.php
331 ms
CiVxVZUu1dU.js
27 ms
LVx-xkvaJ0b.png
15 ms
V89xIM8XrVh.css
3 ms
mKIPuHvlbBA.css
4 ms
6bIl72b-rkY.js
11 ms
TkV0upu1GVq.js
26 ms
mn6tHWuLI-Y.js
25 ms
x8BMxYCqTb9.js
36 ms
12003025_761162947342474_33890003710419503_n.jpg
49 ms
311158_237858749672899_1091581653_n.jpg
29 ms
310561_187428294666508_1951400099_n.jpg
92 ms
10354686_10150004552801856_220367501106153455_n.jpg
28 ms
1454593_597203303667248_2011398847_n.jpg
31 ms
10313536_418676734996786_5554361137845865810_n.jpg
30 ms
12800197_1119570781410864_2277110155667444948_n.jpg
145 ms
12507699_877015742414619_1471536135489644457_n.jpg
30 ms
wL6VQj7Ab77.png
22 ms
s7jcwEQH7Sx.png
22 ms
VXcANLwwL5J.js
3 ms
50Trs1RKgUY.js
4 ms
navp.png
887 ms
belka_face.gif
885 ms
logost.gif
967 ms
ikns.png
947 ms
ikn.png
826 ms
loading.gif
119 ms
yonex.pl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
yonex.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
yonex.pl SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yonex.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish 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 Yonex.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.
yonex.pl
Open Graph description is not detected on the main page of Yonex. 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: