7.5 sec in total
1.3 sec
5.7 sec
549 ms
Welcome to azs.pl homepage info - get ready to check Azs best content for Poland right away, or after learning these important things about azs.pl
Akademicki Związek Sportowy | Projekty i programy
Visit azs.plWe analyzed Azs.pl page load time and found that the first response time was 1.3 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
azs.pl performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value11.7 s
0/100
25%
Value9.4 s
12/100
10%
Value810 ms
36/100
30%
Value0.247
50/100
15%
Value22.8 s
1/100
10%
1324 ms
238 ms
243 ms
441 ms
612 ms
Our browser made a total of 179 requests to load all elements on the main page. We found that 72% of them (129 requests) were addressed to the original Azs.pl, 11% (20 requests) were made to Static.xx.fbcdn.net and 4% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Azs.pl.
Page size can be reduced by 1.6 MB (39%)
4.1 MB
2.5 MB
In fact, the total size of Azs.pl main page is 4.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 226.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 226.5 kB or 82% of the original size.
Potential reduce by 106.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. Azs images are well optimized though.
Potential reduce by 835.2 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 835.2 kB or 69% of the original size.
Potential reduce by 442.7 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. Azs.pl needs all CSS files to be minified and compressed as it can save up to 442.7 kB or 84% of the original size.
Number of requests can be reduced by 86 (51%)
169
83
The browser has sent 169 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Azs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
azs.pl
1324 ms
cssmap-poland.css
238 ms
bootstrap.css
243 ms
index.php
441 ms
index.php
612 ms
style.css
232 ms
sigplus.min.css
239 ms
boxplus.transition.css
348 ms
style.css
349 ms
ic_rounded_module.css
358 ms
style.css
357 ms
tipTip.css
625 ms
default_style.css
404 ms
slideshow.min.css
465 ms
module_default.css
473 ms
jcemediabox.css
625 ms
style.css
621 ms
style3.css
618 ms
system.css
630 ms
legacy-grid.css
722 ms
font-awesome.min.css
743 ms
template.css
967 ms
megamenu.css
740 ms
off-canvas.css
746 ms
font-awesome.min.css
754 ms
custom.css
835 ms
modal.css
854 ms
jquery.min.js
34 ms
jquery-migrate.min.js
855 ms
jquerynoconflict.js
861 ms
mootools-core.js
885 ms
core.js
950 ms
mootools-more.js
1329 ms
modal.js
976 ms
bootstrap.js
1104 ms
script.js
1001 ms
boxplus.transition.min.js
1064 ms
boxplus.lang.min.js
1079 ms
css
25 ms
css
36 ms
css
46 ms
jquery.cssmap.js
165 ms
addthis_widget.js
11 ms
script.js
993 ms
jquery.cssmap.js
428 ms
jQuery.highlightToday.min.js
902 ms
jquery.tipTip.js
957 ms
slideshow.min.js
971 ms
acymailing_module.js
972 ms
jcemediabox.js
981 ms
jquery.tap.min.js
901 ms
off-canvas.js
956 ms
script.js
964 ms
menu.js
894 ms
jquery.ckie.js
900 ms
script.js
954 ms
mootools-more-light.js
826 ms
modal.image2.js
826 ms
crawler.js
908 ms
system.css
822 ms
analytics.js
24 ms
unionjack.png
152 ms
logo.png
482 ms
logo_small.png
153 ms
AMS-lyzwy-1.jpg
572 ms
amp-snowboard1.jpg
649 ms
amp-narty.jpg
545 ms
zalobnie.jpg
482 ms
torun-konferencja.jpg
481 ms
haber_roman.jpg
529 ms
amp-futsal.jpg
530 ms
UMCS-PP1.jpg
534 ms
f9fc20db0475c7eea4f55c7dd7c71a56.jpg
647 ms
84c7b65bb35b9eefc60ecbdbb474ddb3.jpg
645 ms
2ab86ccad8b256e188feb1bc4b1b0b28.jpg
758 ms
amp-snowboard1.jpg
775 ms
amp-narty.jpg
701 ms
amp-futsal.jpg
1047 ms
UMCS-PP1.jpg
1046 ms
AMP-szachy1.jpg
802 ms
pierwszacy2015.jpg
832 ms
AMS-lyzwy-1.jpg
1052 ms
eug2016-baner6.jpg
1046 ms
szachistki-erywan.jpg
1048 ms
wiosla-ukw.jpg
1051 ms
ame-badm.jpg
1196 ms
ame-brydz.jpg
1054 ms
zalobnie.jpg
1115 ms
torun-konferencja.jpg
1123 ms
haber_roman.jpg
1219 ms
grafika3.jpg
1192 ms
wosp2016.jpg
1205 ms
dymalski2015-2.jpg
1252 ms
email.png
1314 ms
legitymacje.png
1316 ms
video.png
1321 ms
sdk.js
16 ms
galeria.png
1313 ms
collect
52 ms
collect
108 ms
354 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
55 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
56 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
56 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
57 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
58 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
57 ms
dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf
56 ms
dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf
56 ms
fontawesome-webfont.woff
1442 ms
xd_arbiter.php
77 ms
xd_arbiter.php
283 ms
logowanie.png
1174 ms
popup.html
957 ms
tooltip.html
960 ms
aps_2016_01.jpg
1175 ms
opensans-regular-webfont.woff
1017 ms
isic-azs.jpg
975 ms
legitymacja-azs.jpg
1058 ms
gorki-01.jpg
1112 ms
gorki-02.jpg
1085 ms
page.php
187 ms
gorki-03.jpg
1035 ms
wilkasy-01.jpg
1083 ms
wilkasy-02.jpg
1099 ms
wilkasy-03.jpg
1046 ms
zieleniec-01.jpg
1011 ms
hDvwL1_H7g-.css
44 ms
56WNbrUYLbL.css
51 ms
GN27K_co9Wc.css
105 ms
q68gy-v_YMF.js
56 ms
GIPX3YHTHu1.js
56 ms
0wM5s1Khldu.js
46 ms
1bNoFZUdlYZ.js
55 ms
OloiM1PZafe.js
55 ms
LTv6ZK-5zxz.js
62 ms
1FCa-btixu2.js
54 ms
Oagsvfb4VWi.js
74 ms
pObvZSrFc_4.js
54 ms
HgJbVwzBr8E.js
54 ms
H3EKDTObx05.js
55 ms
OZFAYTv-ZUg.js
57 ms
zieleniec-02.jpg
1116 ms
zieleniec-03.jpg
1005 ms
1-gosport.jpg
1019 ms
11170353_1001233479894290_4193518035491339562_n.jpg
151 ms
1011847_737408399610134_366107515_n.jpg
21 ms
wL6VQj7Ab77.png
17 ms
s7jcwEQH7Sx.png
20 ms
gxbPuQdXIZP.png
19 ms
2-regatta.jpg
819 ms
3-luxmed.jpg
820 ms
eas-logo.jpg
840 ms
eusa.jpg
875 ms
fisu.jpg
919 ms
gothaer-logo.jpg
927 ms
igrzyska24.jpg
999 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
7 ms
is-logo.jpg
938 ms
isic.jpg
884 ms
krasp.jpg
859 ms
krzasp.jpg
894 ms
men.jpg
984 ms
mnisw.jpg
906 ms
msit.jpg
939 ms
perspektywy-logo.jpg
851 ms
line-head.png
871 ms
bg-stripes.png
890 ms
arrow-section.gif
971 ms
close-st1.png
909 ms
441b72752d1dc81a92129bd5ddc8499f.jpg
887 ms
bfebdbb913e48ab77e0cb1ba1cd0ddfe.jpg
878 ms
2d0c0ec75eb6eb8bf5b3b797251b8dc8.jpg
818 ms
300lo.json
80 ms
loader.png
447 ms
sh.8e5f85691f9aaa082472a194.html
67 ms
layers.e5ea973510bf60b3db41.js
13 ms
pl.js
29 ms
azs.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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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.
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.
azs.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
azs.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Azs.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Azs.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.
azs.pl
Open Graph description is not detected on the main page of Azs. 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: