6.6 sec in total
450 ms
5.9 sec
266 ms
Click here to check amazing Pgi content for Poland. Otherwise, check out these important facts you probably never knew about pgi.gov.pl
Prowadzi działalność naukową we wszystkich dziedzinach nowoczesnej geologii, wypełnia również zadania służby geologicznej
Visit pgi.gov.plWe analyzed Pgi.gov.pl page load time and found that the first response time was 450 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
pgi.gov.pl performance score
450 ms
1220 ms
23 ms
215 ms
224 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 97% of them (88 requests) were addressed to the original Pgi.gov.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 (1.9 sec) belongs to the original domain Pgi.gov.pl.
Page size can be reduced by 608.6 kB (36%)
1.7 MB
1.1 MB
In fact, the total size of Pgi.gov.pl main page is 1.7 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. 45% of websites need less resources to load. Images take 943.1 kB which makes up the majority of the site volume.
Potential reduce by 36.7 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 5.9 kB, which is 13% 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 36.7 kB or 80% of the original size.
Potential reduce by 38.8 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. Pgi images are well optimized though.
Potential reduce by 195.6 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 195.6 kB or 66% of the original size.
Potential reduce by 337.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. Pgi.gov.pl needs all CSS files to be minified and compressed as it can save up to 337.5 kB or 85% of the original size.
Number of requests can be reduced by 30 (34%)
88
58
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pgi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
pgi.gov.pl
450 ms
www.pgi.gov.pl
1220 ms
css
23 ms
attachments_hide.css
215 ms
jcemediabox.css
224 ms
style.css
225 ms
style.css
225 ms
template.css
673 ms
override.css
335 ms
modstyle.css
437 ms
bootstrap.css
892 ms
bootstrap-responsive.css
558 ms
jevcustom.css
447 ms
djimageslider.css
546 ms
template.css
648 ms
mootools-core.js
1006 ms
core.js
758 ms
attachments_refresh.js
769 ms
jquery.min.js
1206 ms
jquery-noconflict.js
882 ms
jquery-migrate.min.js
982 ms
caption.js
992 ms
jcemediabox.js
1330 ms
bootstrap.min.js
1219 ms
template.js
1193 ms
jquery.easing.min.js
1204 ms
slider.js
1219 ms
html5fallback.js
1417 ms
analytics.js
82 ms
popup.html
215 ms
tooltip.html
216 ms
logo_pigpib.png
224 ms
searchButton.gif
224 ms
pl.gif
226 ms
en.gif
225 ms
blank_20px.png
435 ms
ecordlogo1.jpg
437 ms
logo_iodp1.jpg
435 ms
icdplogo.png
445 ms
loader.gif
449 ms
emodnet.png
448 ms
cost_new.png
649 ms
IGCP.png
657 ms
project-shaleseq.png
658 ms
eccsel.jpg
656 ms
minerals_4eu.jpg
659 ms
geonet.png
781 ms
eurogeosurce.png
859 ms
Terrafirma.png
868 ms
ace.png
868 ms
onegeology.jpg
870 ms
energnet_logo.png
990 ms
esf_new.png
1004 ms
forum_pomp_2016.jpg
1493 ms
geolog_2015.jpg
1400 ms
mapa_geologiczna_polski.jpg
1536 ms
line2.png
1092 ms
but_ls.png
1201 ms
magdalena-sidorczuk-mn.jpg
1322 ms
a_kabzinski-min.jpg
1427 ms
osuwisko-min.jpg
1519 ms
logo-pig.jpg
1546 ms
gaziropa.jpg
1623 ms
bilans_zas_min.jpg
1639 ms
IcoMoon.woff
1827 ms
collect
12 ms
opensans-regular-webfont.woff
1636 ms
osuwisko1.jpg
1552 ms
modele3d.gif
1555 ms
thumb_56d7fc6a087132.01996732.jpeg
1625 ms
glyphicons-halflings.png
1654 ms
thumb_56b34decec3487.86052454.jpeg
1765 ms
thumb_56e296a1d50f81.90808069.jpeg
1553 ms
thumb_56e9753c81c687.80547956.jpeg
1612 ms
thumb_56e12ceeac4a39.95749985.jpeg
1620 ms
livemarks.png
1623 ms
monit2.jpg
1739 ms
jedna_ziemia1.jpg
1857 ms
jedna_ziemia4.jpg
1676 ms
jedna_ziemia3.jpg
1726 ms
jedna_ziemia2.jpg
1733 ms
ms_logo.png
1633 ms
logo_nfosigw.jpg
1740 ms
mnisw_logo_s.png
1721 ms
bip.png
1660 ms
egs_logo.jpg
1680 ms
logo-pkpolar.png
1736 ms
gq_if.jpg
1743 ms
VJ.png
1632 ms
pg1.jpg
1711 ms
close-st1.png
1636 ms
pgi.gov.pl SEO score
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pgi.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 Pgi.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.
pgi.gov.pl
Open Graph description is not detected on the main page of Pgi. 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: