Tools & Wizards About Us
geogis.pl screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

geogis.pl

GEOGIS - Strony Internetowe Kraków

Page Load Speed

3.4 sec in total

First Response

420 ms

Resources Loaded

2.6 sec

Page Rendered

327 ms

geogis.pl screenshot

About Website

Click here to check amazing GEOGIS content. Otherwise, check out these important facts you probably never knew about geogis.pl

Projektujemy strony internetowe w mieście Kraków oraz na terenie Małopolski. Profesjonalne strony www. Zdecyduje sie na strony WWW Krakow. Grafika też.

Visit geogis.pl

Key Findings

We analyzed Geogis.pl page load time and found that the first response time was 420 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

geogis.pl performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.8 s

83/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.288

42/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

geogis.pl

420 ms

corbert.css

116 ms

geogis.css

222 ms

style.css

227 ms

jquery.js

448 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 97% of them (62 requests) were addressed to the original Geogis.pl, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Geogis.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.7 kB (8%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Geogis.pl main page is 1.6 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 32.7 kB

  • Original 37.3 kB
  • After minification 28.8 kB
  • After compression 4.6 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 8.5 kB, which is 23% 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 32.7 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.4 MB
  • After minification 1.4 MB

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. GEOGIS images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 80.2 kB

  • Original 139.4 kB
  • After minification 138.3 kB
  • After compression 59.2 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 80.2 kB or 58% of the original size.

CSS Optimization

-84%

Potential reduce by 17.8 kB

  • Original 21.2 kB
  • After minification 15.4 kB
  • After compression 3.4 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. Geogis.pl needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (18%)

Requests Now

61

After Optimization

50

  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GEOGIS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

geogis.pl

geogis.pl

420 ms

corbert.css

corbert.css

116 ms

geogis.css

geogis.css

222 ms

style.css

style.css

227 ms

jquery.js

jquery.js

448 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

228 ms

scripts.js

scripts.js

230 ms

whcookies.js

whcookies.js

234 ms

google_analyzer.js

google_analyzer.js

333 ms

ga.js

ga.js

126 ms

logo-full-black.png

logo-full-black.png

118 ms

laf0.jpg

laf0.jpg

232 ms

laf1.jpg

laf1.jpg

230 ms

icon-1.png

icon-1.png

117 ms

orlovsky0.jpg

orlovsky0.jpg

232 ms

orlovsky1.jpg

orlovsky1.jpg

233 ms

senek0.jpg

senek0.jpg

226 ms

senek1.jpg

senek1.jpg

440 ms

icon-2.png

icon-2.png

340 ms

asic0.jpg

asic0.jpg

450 ms

asic1.jpg

asic1.jpg

458 ms

icon-3.png

icon-3.png

342 ms

mpk0.jpg

mpk0.jpg

346 ms

mpk1.jpg

mpk1.jpg

678 ms

gehanowska0.jpg

gehanowska0.jpg

456 ms

gehanowska1.jpg

gehanowska1.jpg

688 ms

trustcare0.jpg

trustcare0.jpg

548 ms

trustcare1.jpg

trustcare1.jpg

561 ms

twojabizuteria0.jpg

twojabizuteria0.jpg

569 ms

twojabizuteria1.jpg

twojabizuteria1.jpg

566 ms

tomekpikula0.jpg

tomekpikula0.jpg

654 ms

tomekpikula1.jpg

tomekpikula1.jpg

667 ms

tyrybon0.jpg

tyrybon0.jpg

675 ms

tyrybon1.jpg

tyrybon1.jpg

794 ms

hod0.jpg

hod0.jpg

897 ms

hod1.jpg

hod1.jpg

790 ms

swiatkwiatow0.jpg

swiatkwiatow0.jpg

1014 ms

swiatkwiatow1.jpg

swiatkwiatow1.jpg

1128 ms

mennica0.jpg

mennica0.jpg

912 ms

mennica1.jpg

mennica1.jpg

1011 ms

portretybiznesowe0.jpg

portretybiznesowe0.jpg

909 ms

portretybiznesowe1.jpg

portretybiznesowe1.jpg

1005 ms

idream0.jpg

idream0.jpg

1024 ms

idream1.jpg

idream1.jpg

1028 ms

explorecracow0.jpg

explorecracow0.jpg

1138 ms

CorbertCondensed-Regular-webfont.woff

CorbertCondensed-Regular-webfont.woff

1138 ms

__utm.gif

__utm.gif

11 ms

geogis.woff

geogis.woff

1041 ms

explorecracow1.jpg

explorecracow1.jpg

1157 ms

marcincienski0.jpg

marcincienski0.jpg

939 ms

marcincienski1.jpg

marcincienski1.jpg

1032 ms

cukiernialubaczow0.jpg

cukiernialubaczow0.jpg

1044 ms

cukiernialubaczow1.jpg

cukiernialubaczow1.jpg

1153 ms

smalej0.jpg

smalej0.jpg

1142 ms

smalej1.jpg

smalej1.jpg

938 ms

sensorykids0.jpg

sensorykids0.jpg

1029 ms

sensorykids1.jpg

sensorykids1.jpg

1157 ms

ekowsparcie0.jpg

ekowsparcie0.jpg

949 ms

ekowsparcie1.jpg

ekowsparcie1.jpg

1057 ms

turniejsmoka0.jpg

turniejsmoka0.jpg

1083 ms

turniejsmoka1.jpg

turniejsmoka1.jpg

1187 ms

icon-devil.png

icon-devil.png

988 ms

icon-angel.png

icon-angel.png

976 ms

logo.png

logo.png

1049 ms

Accessibility Review

geogis.pl accessibility score

63

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

geogis.pl best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

geogis.pl SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geogis.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Geogis.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.

Social Sharing Optimization

geogis.pl

Open Graph description is not detected on the main page of GEOGIS. 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: