Tools & Wizards About Us
korki.epoznan.pl screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

korki.epoznan.pl

epoznan.pl - Pierwszy Portal Poznania

Page Load Speed

14.6 sec in total

First Response

671 ms

Resources Loaded

13.7 sec

Page Rendered

297 ms

korki.epoznan.pl screenshot

About Website

Welcome to korki.epoznan.pl homepage info - get ready to check Korki Epoznan best content for Poland right away, or after learning these important things about korki.epoznan.pl

epoznan.pl - Pierwszy Portal Poznania

Visit korki.epoznan.pl

Key Findings

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

Performance Metrics

korki.epoznan.pl performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value1,320 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

korki.epoznan.pl

671 ms

jquery-latest.pack.js

396 ms

thickbox.js

200 ms

thickbox.css

201 ms

lightbox.css

204 ms

Our browser made a total of 181 requests to load all elements on the main page. We found that 22% of them (40 requests) were addressed to the original Korki.epoznan.pl, 20% (36 requests) were made to Map3.korkowo.pl and 16% (29 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (7.2 sec) relates to the external source Map3.korkowo.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 875.3 kB (47%)

Content Size

1.8 MB

After Optimization

971.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Korki.epoznan.pl main page is 1.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 935.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 131.2 kB

  • Original 159.1 kB
  • After minification 157.4 kB
  • After compression 27.8 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 131.2 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 33.6 kB

  • Original 672.4 kB
  • After minification 638.9 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. Korki Epoznan images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 645.3 kB

  • Original 935.7 kB
  • After minification 870.2 kB
  • After compression 290.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 645.3 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 65.2 kB

  • Original 79.9 kB
  • After minification 76.4 kB
  • After compression 14.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. Korki.epoznan.pl needs all CSS files to be minified and compressed as it can save up to 65.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (52%)

Requests Now

134

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

korki.epoznan.pl

korki.epoznan.pl

671 ms

jquery-latest.pack.js

jquery-latest.pack.js

396 ms

thickbox.js

thickbox.js

200 ms

thickbox.css

thickbox.css

201 ms

lightbox.css

lightbox.css

204 ms

prototype.js

prototype.js

614 ms

scriptaculous.js

scriptaculous.js

206 ms

lightbox.js

lightbox.js

403 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

598 ms

jquery.autocomplete.js

jquery.autocomplete.js

304 ms

main.min.css

main.min.css

408 ms

komunikacja.min.css

komunikacja.min.css

506 ms

index_new.min.js

index_new.min.js

493 ms

forum.min.js

forum.min.js

496 ms

brand

brand

14 ms

korki.min.js

korki.min.js

510 ms

swfobject.js

swfobject.js

590 ms

js

js

34 ms

brand

brand

30 ms

effects.js

effects.js

200 ms

builder.js

builder.js

101 ms

175 ms

983 ms

ga.js

ga.js

14 ms

logo.png

logo.png

106 ms

epoznan_logmenu.png

epoznan_logmenu.png

3804 ms

4110.png

4110.png

3747 ms

yanosik_sklep.png

yanosik_sklep.png

3804 ms

6610.png

6610.png

3746 ms

arrow.jpg

arrow.jpg

105 ms

6610.png

6610.png

130 ms

search_new_off.png

search_new_off.png

129 ms

map_legend.png

map_legend.png

104 ms

radar.png

radar.png

131 ms

yanosik_dlugi.png

yanosik_dlugi.png

3743 ms

388.png

388.png

4125 ms

vote_red.png

vote_red.png

3744 ms

vote_blue.png

vote_blue.png

3744 ms

send_photo_new.png

send_photo_new.png

3743 ms

zakladka_duza.png

zakladka_duza.png

3742 ms

epoznan_infobox.png

epoznan_infobox.png

4013 ms

sdk.js

sdk.js

39 ms

cien_l.png

cien_l.png

4003 ms

google_site_search_watermark.gif

google_site_search_watermark.gif

56 ms

__utm.gif

__utm.gif

43 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

22 ms

collect

collect

3598 ms

3704 ms

xd_arbiter.php

xd_arbiter.php

3552 ms

xd_arbiter.php

xd_arbiter.php

3621 ms

apl_komu_rozklad.png

apl_komu_rozklad.png

3869 ms

apl_komu_03.png

apl_komu_03.png

3858 ms

adsys2.php

adsys2.php

3231 ms

cien_pr.png

cien_pr.png

334 ms

cien_dol.png

cien_dol.png

447 ms

sm.js

sm.js

424 ms

common.js

common.js

35 ms

map.js

map.js

46 ms

util.js

util.js

46 ms

marker.js

marker.js

45 ms

loadingAnimation.gif

loadingAnimation.gif

384 ms

loading.gif

loading.gif

384 ms

closelabel.gif

closelabel.gif

383 ms

shadow.png

shadow.png

383 ms

likebox.php

likebox.php

275 ms

onion.js

onion.js

22 ms

openhand_8_8.cur

openhand_8_8.cur

19 ms

like.php

like.php

196 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

114 ms

stats.js

stats.js

39 ms

controls.js

controls.js

38 ms

like.php

like.php

211 ms

transparent.png

transparent.png

72 ms

1345.png

1345.png

6640 ms

1345.png

1345.png

6635 ms

1344.png

1344.png

6635 ms

1346.png

1346.png

6635 ms

1344.png

1344.png

6635 ms

1346.png

1346.png

6636 ms

1345.png

1345.png

6644 ms

1345.png

1345.png

6648 ms

1344.png

1344.png

6648 ms

1346.png

1346.png

6647 ms

1344.png

1344.png

6646 ms

1346.png

1346.png

6642 ms

1345.png

1345.png

6863 ms

1345.png

1345.png

6859 ms

1344.png

1344.png

6858 ms

1346.png

1346.png

6860 ms

1344.png

1344.png

6858 ms

1346.png

1346.png

6860 ms

1345.png

1345.png

6965 ms

1345.png

1345.png

6965 ms

1344.png

1344.png

6966 ms

1346.png

1346.png

6966 ms

1344.png

1344.png

6966 ms

1346.png

1346.png

6967 ms

1345.png

1345.png

7072 ms

1345.png

1345.png

7073 ms

1344.png

1344.png

7073 ms

1346.png

1346.png

7074 ms

1344.png

1344.png

7074 ms

1346.png

1346.png

7074 ms

1345.png

1345.png

7179 ms

1345.png

1345.png

7180 ms

1344.png

1344.png

7180 ms

1346.png

1346.png

7180 ms

1344.png

1344.png

7180 ms

1346.png

1346.png

7181 ms

infowindow.js

infowindow.js

53 ms

css

css

98 ms

spotlight-poi.png

spotlight-poi.png

68 ms

bwv9tmT3jXD.js

bwv9tmT3jXD.js

184 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

152 ms

google4.png

google4.png

127 ms

mapcnt6.png

mapcnt6.png

127 ms

sv5.png

sv5.png

128 ms

main.css

main.css

6487 ms

css

css

125 ms

s3zcspk6rx.jpg

s3zcspk6rx.jpg

6484 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

149 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

123 ms

k5BhlqovqZn.css

k5BhlqovqZn.css

150 ms

TKuNj0xVh4A.js

TKuNj0xVh4A.js

152 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

165 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

182 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

180 ms

OloiM1PZafe.js

OloiM1PZafe.js

180 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

189 ms

1FCa-btixu2.js

1FCa-btixu2.js

184 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

185 ms

pObvZSrFc_4.js

pObvZSrFc_4.js

189 ms

Kt4tkgSRvHH.js

Kt4tkgSRvHH.js

186 ms

H3EKDTObx05.js

H3EKDTObx05.js

214 ms

eR-qA8bp1RM.js

eR-qA8bp1RM.js

188 ms

vt

vt

141 ms

vt

vt

90 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

55 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

99 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

114 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

115 ms

vt

vt

34 ms

vt

vt

115 ms

vt

vt

6333 ms

vt

vt

33 ms

vt

vt

45 ms

vt

vt

6332 ms

vt

vt

74 ms

vt

vt

6335 ms

vt

vt

6336 ms

vt

vt

6330 ms

vt

vt

6331 ms

vt

vt

6393 ms

vt

vt

6332 ms

vt

vt

6393 ms

vt

vt

6334 ms

vt

vt

6332 ms

vt

vt

6332 ms

tmapctrl.png

tmapctrl.png

44 ms

cb_scout5.png

cb_scout5.png

49 ms

tmapctrl4.png

tmapctrl4.png

43 ms

imgs8.png

imgs8.png

43 ms

r.gif

r.gif

6375 ms

bwv9tmT3jXD.js

bwv9tmT3jXD.js

6263 ms

421045_10151373861714379_1476682315_n.jpg

421045_10151373861714379_1476682315_n.jpg

6272 ms

946099_10152139634309379_1865666984_n.jpg

946099_10152139634309379_1865666984_n.jpg

102 ms

1379841_10150004552801901_469209496895221757_n.jpg

1379841_10150004552801901_469209496895221757_n.jpg

100 ms

12314138_1223793160968829_7090166695694624988_n.jpg

12314138_1223793160968829_7090166695694624988_n.jpg

101 ms

12107836_1153129614715322_2318252376340492349_n.jpg

12107836_1153129614715322_2318252376340492349_n.jpg

100 ms

10583840_1539953542986105_778413103741418461_n.jpg

10583840_1539953542986105_778413103741418461_n.jpg

137 ms

10522561_342445892572802_6620564872261523782_n.jpg

10522561_342445892572802_6620564872261523782_n.jpg

100 ms

10354686_10150004552801856_220367501106153455_n.jpg

10354686_10150004552801856_220367501106153455_n.jpg

101 ms

11403103_835831379819195_2344129490046794509_n.jpg

11403103_835831379819195_2344129490046794509_n.jpg

102 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

97 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

98 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

195 ms

gxbPuQdXIZP.png

gxbPuQdXIZP.png

47 ms

__utm.gif

__utm.gif

19 ms

collect

collect

12 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

10 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

3 ms

Accessibility Review

korki.epoznan.pl accessibility score

86

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

korki.epoznan.pl best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Requests the notification permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

korki.epoznan.pl SEO score

86

Search Engine Optimization Advices

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

    EN

  • Encoding

    ISO-8859-2

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Korki.epoznan.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it does not match the claimed English language. Our system also found out that Korki.epoznan.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.

Social Sharing Optimization

korki.epoznan.pl

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