8.2 sec in total
378 ms
7.8 sec
49 ms
Welcome to pruszynski.com homepage info - get ready to check Pruszynski best content right away, or after learning these important things about pruszynski.com
Visit pruszynski.comWe analyzed Pruszynski.com page load time and found that the first response time was 378 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pruszynski.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.2
62/100
15%
Value0
0/100
10%
378 ms
401 ms
1004 ms
121 ms
156 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pruszynski.com, 83% (86 requests) were made to Pruszynski.com.pl and 6% (6 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Pruszynski.com.pl.
Page size can be reduced by 331.1 kB (23%)
1.4 MB
1.1 MB
In fact, the total size of Pruszynski.com main page is 1.4 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 117 B
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 117 B or 33% of the original size.
Potential reduce by 259.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. Obviously, Pruszynski needs image optimization as it can save up to 259.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 69.8 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 69.8 kB or 36% of the original size.
Potential reduce by 1.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. Pruszynski.com has all CSS files already compressed.
Number of requests can be reduced by 43 (48%)
90
47
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pruszynski. 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 from 9 to 1 for CSS and as a result speed up the page load time.
pruszynski.com
378 ms
www.pruszynski.com.pl
401 ms
pruszynski.com.pl
1004 ms
gtm.js
121 ms
style.css
156 ms
jquery-1.9.1.min.js
406 ms
google_maps.js
561 ms
order_box.js
667 ms
jquery-ui.min.css
965 ms
scripts.js
988 ms
jquery.mmenu.all.css
91 ms
owl.carousel.css
172 ms
owl.carousel.min.js
994 ms
jquery.customSelect.min.js
363 ms
jquery.mmenu.min.js
386 ms
public.js
991 ms
jquery.mousewheel-3.0.6.pack.js
981 ms
text.css
994 ms
jquery.fancybox.css
1012 ms
jquery.fancybox.pack.js
1022 ms
jquery.fancybox-buttons.css
1021 ms
jquery.fancybox-buttons.js
1018 ms
jquery.fancybox-media.js
1029 ms
jquery.fancybox-thumbs.css
1038 ms
jquery.fancybox-thumbs.js
1040 ms
select2.min.css
382 ms
select2.full.min.js
380 ms
conversion.js
90 ms
firma-rodzinna-logo-czarne.svg
899 ms
logo.png
933 ms
icon_social_fb.png
881 ms
icon_social_yt.png
882 ms
b93abb7f.jpg
1007 ms
3931ed30.jpg
986 ms
ba75f3f8.jpg
919 ms
c869b0d6.jpg
1331 ms
6c411904.jpg
998 ms
f2e5c431.jpg
994 ms
cb434d91.jpg
1083 ms
34239c22.jpg
1102 ms
7a73928b.jpg
1333 ms
0a869fef.jpg
1328 ms
66b16af6.jpg
1323 ms
d12cff17.jpg
1329 ms
b1f377cf.jpg
1330 ms
1e97ee74.jpg
1366 ms
0e2cd482.jpg
1369 ms
eebb2af2.jpg
1378 ms
analytics.js
131 ms
conversion_async.js
157 ms
8d938b3f.jpg
1173 ms
collect
6 ms
collect
91 ms
81 ms
390f2c42.jpg
1013 ms
20 ms
7ec92469.jpg
617 ms
f42655b3.jpg
611 ms
departments_img.png
610 ms
bef808ba.jpg
606 ms
b3578e56.jpg
646 ms
881c5d49.jpg
681 ms
1e72ce52.png
628 ms
e3d95406.jpg
621 ms
4d451898.jpg
654 ms
492cae98.jpg
654 ms
e52e9329.jpg
646 ms
6771fea2.jpg
697 ms
60eec66d.jpg
693 ms
box-empty_alt.svg
676 ms
X_alt.svg
741 ms
Coversans-Regular.woff
745 ms
Coversans-Medium.woff
708 ms
Coversans-Light.woff
804 ms
Coversans-SemiBold.woff
763 ms
Coversans-Bold.woff
749 ms
BwQuintaPro-Bold.woff
741 ms
BwQuintaPro-Black.woff
740 ms
BwQuintaPro-Regular.woff
806 ms
BwQuintaPro-Light.woff
787 ms
msg_icon_yellow3.webp
564 ms
order-box.png
558 ms
loading.gif
559 ms
icon_roof.svg
559 ms
icon_cart.svg
722 ms
icon_search.png
719 ms
5a6855f1.jpg
721 ms
arrow-twocol.png
681 ms
d8ee1990.jpg
710 ms
departments_bg.png
666 ms
newsletter_bg.png
3623 ms
checkbox-unchecked.png
863 ms
90 ms
msg_icon_yellow3.webp
2745 ms
cf3c77a9.jpg
817 ms
homeslider-left.png
117 ms
homeslider-right.png
119 ms
homeoffer-left.png
116 ms
homeoffer-right.png
120 ms
brandslider-left.png
118 ms
brandslider-right.png
227 ms
acceptCookieWhite.png
228 ms
36 ms
pruszynski.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
pruszynski.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pruszynski.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Pruszynski.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
pruszynski.com
Open Graph description is not detected on the main page of Pruszynski. 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: