Tools & Wizards About Us
puck.pl screenshot

Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

puck.pl

Powiat Pucki - Starostwo Powiatowe w Pucku

Page Load Speed

3.1 sec in total

First Response

549 ms

Resources Loaded

2.3 sec

Page Rendered

220 ms

puck.pl screenshot

About Website

Visit puck.pl now to see the best up-to-date Puck content for Poland and also check out these interesting facts you probably never knew about puck.pl

Informacje i wydarzenia z Ziemi Puckiej. Sprawy urzędowe.

Visit puck.pl

Key Findings

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

Performance Metrics

puck.pl performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

puck.pl

549 ms

dnia.js

232 ms

styl.css

238 ms

baner_g.jpg

120 ms

tlo.jpg

120 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 96% of them (68 requests) were addressed to the original Puck.pl, 3% (2 requests) were made to Home.hit.stat24.com and 1% (1 request) were made to St.hit.gemius.pl. The less responsive or slowest element that took the longest time to load (826 ms) belongs to the original domain Puck.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.2 kB (38%)

Content Size

80.2 kB

After Optimization

50.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Puck.pl main page is 80.2 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. 15% of websites need less resources to load. Images take 43.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 21.0 kB

  • Original 25.0 kB
  • After minification 23.0 kB
  • After compression 4.0 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 21.0 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 841 B

  • Original 43.6 kB
  • After minification 42.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. Puck images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 4.9 kB

  • Original 7.3 kB
  • After minification 6.6 kB
  • After compression 2.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 4.9 kB or 67% of the original size.

CSS Optimization

-80%

Potential reduce by 3.5 kB

  • Original 4.3 kB
  • After minification 3.4 kB
  • After compression 853 B

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. Puck.pl needs all CSS files to be minified and compressed as it can save up to 3.5 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (54%)

Requests Now

70

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

puck.pl

puck.pl

549 ms

dnia.js

dnia.js

232 ms

styl.css

styl.css

238 ms

baner_g.jpg

baner_g.jpg

120 ms

tlo.jpg

tlo.jpg

120 ms

tlo_154.jpg

tlo_154.jpg

121 ms

g_154.jpg

g_154.jpg

226 ms

d_154.jpg

d_154.jpg

237 ms

wikipedia.gif

wikipedia.gif

238 ms

logo_tpsa.gif

logo_tpsa.gif

241 ms

logo_netia.gif

logo_netia.gif

238 ms

plus.gif

plus.gif

240 ms

idea.gif

idea.gif

342 ms

era.gif

era.gif

359 ms

home.gif

home.gif

356 ms

internetia.gif

internetia.gif

356 ms

mf.gif

mf.gif

358 ms

zus.jpg

zus.jpg

359 ms

logo_platnik.gif

logo_platnik.gif

460 ms

logopit.jpg

logopit.jpg

475 ms

vat.gif

vat.gif

473 ms

logo_inteligo.gif

logo_inteligo.gif

478 ms

m-bank.gif

m-bank.gif

475 ms

spacer.gif

spacer.gif

476 ms

tlo_450.jpg

tlo_450.jpg

577 ms

g_450.jpg

g_450.jpg

591 ms

herbpu.gif

herbpu.gif

594 ms

spacer.gif

spacer.gif

591 ms

herbstar.gif

herbstar.gif

594 ms

herbgm.gif

herbgm.gif

594 ms

zd.gif

zd.gif

695 ms

pup.gif

pup.gif

708 ms

kppsp.gif

kppsp.gif

711 ms

spzoz.gif

spzoz.gif

713 ms

logo_wtz.gif

logo_wtz.gif

715 ms

fara-c.gif

fara-c.gif

713 ms

mzp.jpg

mzp.jpg

812 ms

ptk.gif

ptk.gif

826 ms

kolekcjonerzy_logo.gif

kolekcjonerzy_logo.gif

808 ms

osirznak.gif

osirznak.gif

728 ms

lks.gif

lks.gif

715 ms

hom.gif

hom.gif

716 ms

kibol.gif

kibol.gif

713 ms

zatoka.jpg

zatoka.jpg

714 ms

grot.png

grot.png

714 ms

d_450.jpg

d_450.jpg

713 ms

google.gif

google.gif

716 ms

netsprint.gif

netsprint.gif

711 ms

yahoo.gif

yahoo.gif

713 ms

excite.gif

excite.gif

712 ms

lycos.gif

lycos.gif

712 ms

totu.gif

totu.gif

713 ms

wp.gif

wp.gif

717 ms

onet.gif

onet.gif

714 ms

script.js

script.js

550 ms

interia.gif

interia.gif

712 ms

hoga.gif

hoga.gif

712 ms

of.gif

of.gif

711 ms

mozilla.gif

mozilla.gif

712 ms

firefox.gif

firefox.gif

714 ms

thunderbid.jpg

thunderbid.jpg

715 ms

certum.gif

certum.gif

712 ms

biblioteka.gif

biblioteka.gif

712 ms

imgw.gif

imgw.gif

711 ms

nfz.gif

nfz.gif

710 ms

discovery.gif

discovery.gif

713 ms

counter

counter

721 ms

top.gif

top.gif

711 ms

edmar.jpg

edmar.jpg

709 ms

cachedscriptxy.js

cachedscriptxy.js

230 ms

rexdot.gif

rexdot.gif

116 ms

Accessibility Review

puck.pl accessibility score

63

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best Practices

puck.pl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

puck.pl SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-2

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puck.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 Puck.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

puck.pl

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