8.2 sec in total
479 ms
7.4 sec
392 ms
Visit poir.gov.pl now to see the best up-to-date Poir content for Poland and also check out these interesting facts you probably never knew about poir.gov.pl
Witamy na stronach poświęconych Programowi Inteligentny Rozwój. Znajdą tutaj Państwo informacje i dokumenty pomocne w ubieganiu się o środki unijne
Visit poir.gov.plWe analyzed Poir.gov.pl page load time and found that the first response time was 479 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.
poir.gov.pl performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value13.0 s
0/100
25%
Value11.9 s
4/100
10%
Value1,110 ms
23/100
30%
Value0.182
67/100
15%
Value19.5 s
2/100
10%
479 ms
2245 ms
253 ms
366 ms
364 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 96% of them (119 requests) were addressed to the original Poir.gov.pl, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Poir.gov.pl.
Page size can be reduced by 393.1 kB (12%)
3.2 MB
2.8 MB
In fact, the total size of Poir.gov.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. 55% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 66.4 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. This page needs HTML code to be minified as it can gain 21.6 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.4 kB or 82% of the original size.
Potential reduce by 308.3 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, Poir needs image optimization as it can save up to 308.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 11.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 7.2 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. Poir.gov.pl needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 12% of the original size.
Number of requests can be reduced by 50 (42%)
118
68
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poir. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
poir.gov.pl
479 ms
www.poir.gov.pl
2245 ms
afxForm.css
253 ms
normalize.css
366 ms
grid.css
364 ms
ie8-grid.css
370 ms
typography.css
367 ms
navigation.css
371 ms
forms.css
380 ms
buttons.css
486 ms
icons.css
487 ms
flexslider.css
490 ms
style.css
491 ms
content.css
613 ms
media-queries.css
509 ms
content-media-queries.css
609 ms
visibility-classes.css
611 ms
cssmap-poland.css
732 ms
datepicker.css
618 ms
jquery-ui-1.10.4.custom.min.css
638 ms
afxcontent.css
731 ms
afxmultiselect.css
736 ms
leaflet.css
736 ms
leaflet.js
858 ms
Leaflet.fullscreen.min.js
768 ms
leaflet.fullscreen.css
851 ms
calendarLangs.js
854 ms
custom.modernizr.js
856 ms
jquery.js
980 ms
jquery.validate.min.js
898 ms
jquery.validate.unobtrusive.min.js
974 ms
validation.js
975 ms
jquery-ui-1.10.4.custom.min.js
993 ms
afxInit.js
978 ms
bootstrap-popover.js
1027 ms
bootstrap-popover.min.css
1099 ms
logo.css
1096 ms
js
63 ms
api.js
36 ms
video-js.css
990 ms
video.js
867 ms
foundation.min.js
812 ms
jquery.flexslider.js
859 ms
foundation.topbar.js
875 ms
foundation.placeholder.js
874 ms
jquery.maskedinput.js
874 ms
foundation.datepicker.js
867 ms
jquery.multiselect.js
759 ms
jquery.cookiebar.js
819 ms
jquery.cssmap.js
860 ms
init.js
862 ms
afxmultiselectinit.js
847 ms
analytics.js
117 ms
logo_ir.jpg
350 ms
logo_PL_UE_zm.jpg
350 ms
ue_flaga_naglowek.png
353 ms
sprite.png
353 ms
sprite.png
356 ms
search_b.png
439 ms
move_b.png
440 ms
list_b.png
439 ms
doc_arrow.png
500 ms
Fundusze_UE.png
497 ms
pozyczki_wsparcie.jpg
498 ms
light.png
501 ms
law.png
529 ms
iko_koronawirus2.png
529 ms
point.png
653 ms
stat.png
650 ms
building.png
1960 ms
money.png
648 ms
docs.png
697 ms
Ikona_system_info3.png
709 ms
award.png
795 ms
success.png
799 ms
rzecznikFE5.jpg
796 ms
STEP_logotyp_mono_9.jpg
1200 ms
BK.png
812 ms
ubuntu-light.woff
994 ms
ubuntu-regular.woff
949 ms
collect
18 ms
ubuntu-medium.woff
957 ms
ubuntu-bold.woff
988 ms
logo_STEP_slider_2022_po.png
1075 ms
logotypy_FE_2014_2020_.jpg
1053 ms
logo_MFiPR_2022.png
1052 ms
rss.png
1051 ms
f_logo_RGB-Blue_1024.png
1078 ms
youtube_social_circle_red.png
1070 ms
recaptcha__en.js
133 ms
IG_Glyph_Fill.png
1100 ms
projekt_POIR.jpg
1009 ms
IG_Glyph_Fill.png
1256 ms
youtube_social_circle_red.png
1130 ms
f_logo_RGB-Blue_1024.png
2758 ms
rss.png
1148 ms
logo_MFiPR_2022.png
1160 ms
logotypy_FE_2014_2020_.jpg
1191 ms
logo_STEP_slider_2022_po.png
1214 ms
BK.png
1244 ms
STEP_logotyp_mono_9.jpg
1308 ms
rzecznikFE5.jpg
1270 ms
success.png
1295 ms
award.png
1347 ms
Ikona_system_info3.png
1373 ms
docs.png
1282 ms
money.png
1292 ms
building.png
1358 ms
stat.png
1341 ms
point.png
1354 ms
iko_koronawirus2.png
1290 ms
law.png
1304 ms
light.png
1353 ms
pozyczki_wsparcie.jpg
1316 ms
Fundusze_UE.png
1157 ms
doc_arrow.png
1155 ms
list_b.png
1165 ms
move_b.png
1183 ms
search_b.png
1134 ms
ue_flaga_naglowek.png
1174 ms
logo_PL_UE_zm.jpg
1176 ms
logo_ir.jpg
1314 ms
flex-prev.png
1192 ms
flex-next.png
1135 ms
poir.gov.pl accessibility score
poir.gov.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
Page has valid source maps
poir.gov.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use 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 Poir.gov.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 Poir.gov.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.
poir.gov.pl
Open Graph description is not detected on the main page of Poir. 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: