4.3 sec in total
622 ms
3.1 sec
605 ms
Click here to check amazing Aptekarz Polski content for Poland. Otherwise, check out these important facts you probably never knew about aptekarzpolski.pl
Visit aptekarzpolski.plWe analyzed Aptekarzpolski.pl page load time and found that the first response time was 622 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
aptekarzpolski.pl performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value22.0 s
0/100
25%
Value13.1 s
2/100
10%
Value1,070 ms
25/100
30%
Value0.444
21/100
15%
Value15.9 s
6/100
10%
622 ms
944 ms
22 ms
424 ms
511 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 97% of them (119 requests) were addressed to the original Aptekarzpolski.pl, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (944 ms) belongs to the original domain Aptekarzpolski.pl.
Page size can be reduced by 1.1 MB (35%)
3.2 MB
2.1 MB
In fact, the total size of Aptekarzpolski.pl main page is 3.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. 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 87.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 87.5 kB or 82% of the original size.
Potential reduce by 57.1 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. Aptekarz Polski images are well optimized though.
Potential reduce by 500.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 500.4 kB or 75% of the original size.
Potential reduce by 464.5 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. Aptekarzpolski.pl needs all CSS files to be minified and compressed as it can save up to 464.5 kB or 86% of the original size.
Number of requests can be reduced by 74 (63%)
118
44
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aptekarz Polski. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
aptekarzpolski.pl
622 ms
www.aptekarzpolski.pl
944 ms
css
22 ms
font-awesome.min.css
424 ms
h5ab-print.css
511 ms
validationEngine.jquery.css
623 ms
implied-cookie-consent.css
588 ms
swipebox.min.css
458 ms
wpctc.min.css
114 ms
public.css
124 ms
style.css
134 ms
responsive.css
142 ms
font-awesome.min.css
152 ms
www.aptekarzpolski.pl
807 ms
jquery.js
438 ms
jquery-migrate.min.js
448 ms
jquery.cookie.js
456 ms
implied-cookie-consent.js
465 ms
jquery.swipebox.min.js
466 ms
front.js
475 ms
jquery.flexslider.min.js
474 ms
grid-gallery.galleries.frontend.css
482 ms
grid-gallery.galleries.effects.css
485 ms
jquery.flex-images.css
491 ms
lightSlider.css
492 ms
prettyPhoto.css
500 ms
photobox.css
501 ms
gridgallerypro-embedded.css
512 ms
icons-effects.css
510 ms
loaders.css
516 ms
widgets.min.css
518 ms
nextgen_basic_thumbnails.min.css
520 ms
trigger_buttons.min.css
524 ms
jquery.fancybox-1.3.4.min.css
526 ms
font-awesome.min.css
529 ms
style.min.css
532 ms
nggallery.css
535 ms
wp-emoji-release.min.js
518 ms
webfont.js
18 ms
h5ab-print.js
450 ms
jquery.tagcanvas.min.js
443 ms
wpctc.tagcanvas.min.js
437 ms
jquery.style.min.js
422 ms
wp-category-tag-cloud.min.js
423 ms
jquery.colorbox-min.js
416 ms
jquery.colorbox-pl.js
148 ms
public-min.js
134 ms
jquery.jplayer.min.js
129 ms
scripts.js
123 ms
jquery.sharrre.min.js
126 ms
wp-embed.min.js
122 ms
imagesLoaded.min.js
122 ms
jquery.easing.js
117 ms
jquery.prettyphoto.js
119 ms
jquery.quicksand.js
114 ms
jquery.wookmark.js
110 ms
jquery.slimscroll.js
110 ms
jquery.photobox.js
109 ms
jquery.sliphover.js
105 ms
frontend.js
109 ms
jquery.validationEngine-pl.js
108 ms
jquery.validationEngine.js
102 ms
front-subscribers.js
105 ms
ajax.min.js
103 ms
common.min.js
99 ms
nextgen_basic_thumbnails.min.js
102 ms
lightbox_context.min.js
97 ms
jquery.easing-1.3.pack.js
102 ms
jquery.fancybox-1.3.4.pack.js
95 ms
nextgen_fancybox_init.min.js
95 ms
APLOGO-1.jpg
65 ms
recepturowe-150x150.jpg
58 ms
tlenekazotuii-150x150.jpg
59 ms
uprawnieniazwaodowe-150x150.jpg
58 ms
nano-150x150.jpg
59 ms
bodzce-150x150.jpg
61 ms
kalendarzm.jpg
64 ms
testwiedzy.jpg
66 ms
022016.jpg
69 ms
bepp.jpg
71 ms
plakat3.jpg
114 ms
rafting.jpg
109 ms
strategia-200x140.jpg
67 ms
wydawnictwo-200x140.jpg
68 ms
kodeks-200x140.jpg
68 ms
kwasliponowy1-160x160.jpg
69 ms
nuzyca1-160x160.jpg
70 ms
pleurotus.jpg
109 ms
Fotolia_51010376_XS-160x160.jpg
104 ms
pilka-160x160.jpg
104 ms
XAlkxBmd-160x160.png
104 ms
thumbs_DSC_0180.jpg
105 ms
thumbs_IMGP4711.jpg
106 ms
thumbs_IMGP4695.jpg
107 ms
thumbs_DSC_0047.jpg
109 ms
thumbs_IMGP4691.jpg
107 ms
thumbs_IMGP4700.jpg
107 ms
thumbs_DSC_0119.jpg
110 ms
thumbs_kza12.jpg
115 ms
thumbs_kza11.jpg
111 ms
thumbs_kza10.jpg
109 ms
thumbs_kza9.jpg
110 ms
thumbs_kza8.jpg
111 ms
thumbs_kza7.jpg
111 ms
thumbs_kza6.jpg
112 ms
thumbs_kza5.jpg
68 ms
thumbs_kza4.jpg
64 ms
thumbs_kza3.jpg
66 ms
thumbs_kza2.jpg
437 ms
thumbs_kza1.jpg
435 ms
s-right-s2.png
430 ms
s-left.png
432 ms
fontawesome-webfont.woff
576 ms
fontawesome-webfont.woff
636 ms
fontawesome-webfont.woff
605 ms
analytics.js
301 ms
colorbox.css
23 ms
fancybox-x.png
97 ms
fancybox.png
97 ms
fancybox-y.png
95 ms
blank.gif
98 ms
overlay.png
75 ms
collect
62 ms
aptekarzpolski.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-*] attributes do not match their roles
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
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.
aptekarzpolski.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Page has valid source maps
aptekarzpolski.pl 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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aptekarzpolski.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 Aptekarzpolski.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.
aptekarzpolski.pl
Open Graph description is not detected on the main page of Aptekarz Polski. 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: