6.4 sec in total
923 ms
4.8 sec
618 ms
Click here to check amazing OBYWATEL content for Poland. Otherwise, check out these important facts you probably never knew about obywatel.gov.pl
Sprawdź jak załatwić sprawę w urzędzie albo załatw ją przez internet
Visit obywatel.gov.plWe analyzed Obywatel.gov.pl page load time and found that the first response time was 923 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
obywatel.gov.pl performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value10.3 s
0/100
25%
Value9.1 s
14/100
10%
Value220 ms
88/100
30%
Value0.001
100/100
15%
Value12.6 s
14/100
10%
923 ms
306 ms
730 ms
317 ms
840 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 88% of them (57 requests) were addressed to the original Obywatel.gov.pl, 5% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Pi.coi.gov.pl. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Obywatel.gov.pl.
Page size can be reduced by 583.4 kB (67%)
866.8 kB
283.5 kB
In fact, the total size of Obywatel.gov.pl main page is 866.8 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. 50% of websites need less resources to load. Javascripts take 484.4 kB which makes up the majority of the site volume.
Potential reduce by 28.3 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 28.3 kB or 74% of the original size.
Potential reduce by 3 B
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. OBYWATEL images are well optimized though.
Potential reduce by 319.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 319.4 kB or 66% of the original size.
Potential reduce by 235.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. Obywatel.gov.pl needs all CSS files to be minified and compressed as it can save up to 235.7 kB or 86% of the original size.
Number of requests can be reduced by 34 (59%)
58
24
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OBYWATEL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
obywatel.gov.pl
923 ms
jquery-ui.min.css
306 ms
style.css
730 ms
style_lr.css
317 ms
general.min.js
840 ms
jquery.ba-hashchange.min.js
323 ms
wizard.js
537 ms
angular.min.js
908 ms
angular-sanitize.min.js
525 ms
ngMask.min.js
536 ms
angular-translate.min.js
764 ms
obywatel-app.min.js
644 ms
directives.min.js
644 ms
filters.min.js
765 ms
angular-route.min.js
764 ms
ui-bootstrap-tpls.min.js
938 ms
angular-locale_pl-pl.js
874 ms
dane-pesel.min.js
882 ms
dane-rdo.min.js
883 ms
sprawdz-wniosek.min.js
957 ms
sprawdzenie-uniewaznienia-dowodu.min.js
956 ms
feedback.min.js
883 ms
widget-najblizszy-urzad.min.js
882 ms
lista-urzedow.min.js
914 ms
esearch.js
950 ms
jquery-ui.min.js
906 ms
session.js
907 ms
related-assets.js
1005 ms
if-show-modal.js
1004 ms
portlet-styles-cleanup.js
1004 ms
no-right-column-fixed.js
1005 ms
wcag.js
1005 ms
utils.js
1005 ms
analytics.js
157 ms
piwik.js
904 ms
logo-mc-header.svg
991 ms
wybory1.png
209 ms
wybory2.png
209 ms
0fdeab57-e5cf-4db1-9782-38b80460b878
342 ms
f3605a14-5ead-4fbd-b858-89e3d03fc2ba
343 ms
0ab24742-5b8a-4208-b0de-61ce4eca7c88
343 ms
ig.svg
353 ms
ig-hc.svg
351 ms
plid.svg
362 ms
plid-hc.svg
518 ms
ue.svg
520 ms
ue-hc.svg
531 ms
mc.svg
658 ms
mc-hc.svg
603 ms
coi.svg
519 ms
coi-hc.svg
518 ms
loader.gif
669 ms
narodziny-dziecka-baner-bg.jpg
666 ms
sprite_all.svg
639 ms
lato-regular.ttf
1524 ms
lato-bold.ttf
1579 ms
bebasneue.woff
543 ms
linkid.js
18 ms
czas_imnazw
209 ms
collect
113 ms
collect
97 ms
ga-audiences
33 ms
piwik.php
160 ms
piwik.php
607 ms
print.css
108 ms
obywatel.gov.pl accessibility score
obywatel.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
obywatel.gov.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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Obywatel.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 Obywatel.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.
obywatel.gov.pl
Open Graph description is not detected on the main page of OBYWATEL. 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: