5.4 sec in total
716 ms
4.5 sec
112 ms
Click here to check amazing GEOPOZ content for Poland. Otherwise, check out these important facts you probably never knew about geopoz.pl
Realizowanie zadań służby geodezyjnej miasta oraz prowadzenie gospodarki gruntami i nieruchomościami na terenie Poznania.
Visit geopoz.plWe analyzed Geopoz.pl page load time and found that the first response time was 716 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
geopoz.pl performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value6.7 s
8/100
25%
Value7.5 s
26/100
10%
Value40 ms
100/100
30%
Value0.006
100/100
15%
Value7.5 s
47/100
10%
716 ms
449 ms
233 ms
347 ms
462 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that all of those requests were addressed to Geopoz.pl and no external sources were called. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Geopoz.pl.
Page size can be reduced by 255.3 kB (71%)
361.5 kB
106.2 kB
In fact, the total size of Geopoz.pl main page is 361.5 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. 20% of websites need less resources to load. Javascripts take 246.8 kB which makes up the majority of the site volume.
Potential reduce by 13.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. 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 13.7 kB or 77% of the original size.
Potential reduce by 8.6 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, GEOPOZ needs image optimization as it can save up to 8.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 205.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 205.8 kB or 83% of the original size.
Potential reduce by 27.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. Geopoz.pl needs all CSS files to be minified and compressed as it can save up to 27.2 kB or 86% of the original size.
Number of requests can be reduced by 18 (41%)
44
26
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GEOPOZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
geopoz.pl
716 ms
index.php
449 ms
geopoz.css
233 ms
utils.js
347 ms
CalendarPopup2.js
462 ms
bipUtils.js
236 ms
calendar-win2k-1.css
119 ms
calendar.js
472 ms
calendar-pl-utf8.js
239 ms
calendar-setup.js
239 ms
prototype.js
475 ms
ajax.js
351 ms
js_utils.js
355 ms
position.js
480 ms
combobox_utilities.js
481 ms
combobox.js
586 ms
autofill.js
588 ms
logo_ost_01.gif
354 ms
mid.jpg
706 ms
logo_poznan.gif
238 ms
gmenu3.png
238 ms
t5cc.gif
239 ms
pgr5.gif
239 ms
lgr5.gif
475 ms
t7.gif
485 ms
index.php
675 ms
pasek.gif
483 ms
index.php
665 ms
next.gif
704 ms
pdr5.gif
713 ms
ldr5.gif
718 ms
t5aa.gif
904 ms
iko_sprawa.gif
905 ms
iko_godziny.gif
939 ms
iko_esp.gif
942 ms
bip_mini.gif
947 ms
iip_mini.png
955 ms
sip%20nw%20maly.gif
1141 ms
modgik%20maly.gif
1144 ms
stopka.gif
1175 ms
kontrast_mini.PNG
1171 ms
gluchoniemi_mini.jpg
1178 ms
ISO_mini.PNG
1193 ms
inwalid_mini.PNG
1374 ms
dog_mini.PNG
1379 ms
geopoz0.css
118 ms
geopoz.pl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
geopoz.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
geopoz.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 uses legible font sizes
Tap targets are not sized appropriately
PL
PL
ISO-8859-2
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geopoz.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 Geopoz.pl main page’s claimed encoding is iso-8859-2. 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.
geopoz.pl
Open Graph description is not detected on the main page of GEOPOZ. 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: