5.6 sec in total
664 ms
4.6 sec
336 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 664 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
poir.gov.pl performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value12.4 s
0/100
25%
Value11.2 s
5/100
10%
Value440 ms
64/100
30%
Value0.127
82/100
15%
Value10.7 s
22/100
10%
664 ms
218 ms
218 ms
338 ms
219 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 96% of them (70 requests) were addressed to the original Poir.gov.pl, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Poir.gov.pl.
Page size can be reduced by 177.3 kB (22%)
796.1 kB
618.8 kB
In fact, the total size of Poir.gov.pl main page is 796.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 620.9 kB which makes up the majority of the site volume.
Potential reduce by 42.2 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 15.4 kB, which is 30% 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 42.2 kB or 81% of the original size.
Potential reduce by 44.5 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. Poir images are well optimized though.
Potential reduce by 4.5 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 4.5 kB or 17% of the original size.
Potential reduce by 86.0 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 86.0 kB or 89% of the original size.
Number of requests can be reduced by 41 (60%)
68
27
The browser has sent 68 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 21 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
www.poir.gov.pl
664 ms
afxForm.css
218 ms
normalize.css
218 ms
grid.css
338 ms
ie8-grid.css
219 ms
typography.css
234 ms
navigation.css
536 ms
forms.css
441 ms
buttons.css
431 ms
icons.css
432 ms
flexslider.css
452 ms
style.css
670 ms
content.css
872 ms
media-queries.css
646 ms
content-media-queries.css
662 ms
visibility-classes.css
774 ms
cssmap-poland.css
963 ms
datepicker.css
873 ms
jquery-ui-1.10.4.custom.min.css
877 ms
afxcontent.css
892 ms
afxmultiselect.css
988 ms
custom.modernizr.js
1085 ms
jquery.js
1408 ms
jquery.validate.min.js
1200 ms
jquery.validate.unobtrusive.min.js
1107 ms
validation.js
1178 ms
jquery-ui-1.10.4.custom.min.js
1313 ms
afxInit.js
1311 ms
logo.css
1328 ms
video-js.css
1413 ms
video.js
1582 ms
foundation.min.js
1655 ms
jquery.flexslider.js
1451 ms
foundation.topbar.js
1348 ms
foundation.placeholder.js
1427 ms
jquery.maskedinput.js
1524 ms
js
73 ms
foundation.datepicker.js
1707 ms
jquery.multiselect.js
1745 ms
jquery.cookiebar.js
1667 ms
jquery.cssmap.js
1788 ms
init.js
1827 ms
afxmultiselectinit.js
1742 ms
analytics.js
17 ms
collect
24 ms
logo_ir.jpg
504 ms
ue_flaga_naglowek.png
474 ms
sprite.png
594 ms
sprite.png
635 ms
search_b.png
581 ms
move_b.png
598 ms
list_b.png
662 ms
doc_arrow.png
720 ms
light.png
797 ms
law.png
811 ms
stat.png
815 ms
point.png
852 ms
building.png
884 ms
money.png
937 ms
docs.png
1013 ms
award.png
1027 ms
success.png
1031 ms
21052015_DWTsukces.jpg
1943 ms
ZESTAWIENIE__.jpg
1200 ms
logo_mr_stopka2.png
1153 ms
fb.png
1228 ms
yt.png
1243 ms
gp.png
1246 ms
rss.png
1368 ms
ubuntu-light.woff
1943 ms
ubuntu-regular.woff
1873 ms
ubuntu-medium.woff
1862 ms
ubuntu-bold.woff
1894 ms
poir.gov.pl accessibility score
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
Links do not have a discernible name
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: