3.6 sec in total
277 ms
3.1 sec
151 ms
Welcome to mpk.gniezno.pl homepage info - get ready to check MPK Gniezno best content for Poland right away, or after learning these important things about mpk.gniezno.pl
Informacje ogólne, system zarządzania, układ komunikacyjny miasta, taryfa opłat, system kontroli biletów.
Visit mpk.gniezno.plWe analyzed Mpk.gniezno.pl page load time and found that the first response time was 277 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
mpk.gniezno.pl performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value11.6 s
0/100
25%
Value5.7 s
51/100
10%
Value170 ms
93/100
30%
Value0.021
100/100
15%
Value8.6 s
37/100
10%
277 ms
709 ms
34 ms
51 ms
230 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 47% of them (61 requests) were addressed to the original Mpk.gniezno.pl, 43% (56 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Mpk.gniezno.pl.
Page size can be reduced by 351.5 kB (16%)
2.2 MB
1.8 MB
In fact, the total size of Mpk.gniezno.pl main page is 2.2 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.6 MB which makes up the majority of the site volume.
Potential reduce by 118.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. This page needs HTML code to be minified as it can gain 36.5 kB, which is 27% 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 118.0 kB or 86% of the original size.
Potential reduce by 18.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. MPK Gniezno images are well optimized though.
Potential reduce by 91.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 91.6 kB or 31% of the original size.
Potential reduce by 123.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. Mpk.gniezno.pl needs all CSS files to be minified and compressed as it can save up to 123.2 kB or 72% of the original size.
Number of requests can be reduced by 48 (70%)
69
21
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MPK Gniezno. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
mpk.gniezno.pl
277 ms
www.mpk.gniezno.pl
709 ms
css
34 ms
css
51 ms
jquery.bxslider.css
230 ms
prettyPhoto.css
348 ms
fm.checkator.jquery.css
349 ms
jquery-ui.css
352 ms
slick.css
34 ms
slick-theme.css
55 ms
bootstrap.min.css
471 ms
default.css
360 ms
mpk.css
450 ms
mpk_responsive.css
464 ms
default_responsive.css
466 ms
jquery.ui.timepicker.css
468 ms
jquery-ui-1.10.0.custom.min.css
479 ms
respond.js
567 ms
html5shiv.js
580 ms
jsapi
15 ms
jquery-1.11.3.min.js
701 ms
jquery.touchwipe.min.js
586 ms
jquery.prettyPhoto.js
587 ms
jquery.bxslider.js
596 ms
fm.checkator.jquery.js
683 ms
jquery-ui.js
931 ms
inputmask.js
711 ms
jquery.inputmask.js
747 ms
jquery.ui.core.min.js
748 ms
jquery.ui.widget.min.js
800 ms
jquery.ui.tabs.min.js
816 ms
jquery.ui.position.min.js
826 ms
jquery.ui.timepicker.js
869 ms
slick.min.js
48 ms
app.js
869 ms
shop.js
917 ms
responsive.js
949 ms
loader.js
14 ms
print.css
144 ms
analytics.js
147 ms
topbgpattern.png
145 ms
mpklogo.png
143 ms
f.png
144 ms
t.png
144 ms
g.png
144 ms
14490403581565e99e662960270161076.png
1191 ms
14490402851565e999da6028352298596.png
959 ms
14490403201565e99c02caf6367157600.png
1298 ms
streets2.png
286 ms
ajax-loader.gif
68 ms
arrows.png
158 ms
spin.png
173 ms
calendar.png
247 ms
redtime.png
247 ms
JD.png
291 ms
pin.png
363 ms
burger.png
363 ms
timer.png
406 ms
14466466601563a13846f2cf805961493.png
479 ms
14466466791563a1397580aa977400881.png
481 ms
151021656215a041372d849c359073305.png
524 ms
pin2.png
595 ms
ui-bg_gloss-wave_35_f6a828_500x100.png
597 ms
ui-bg_glass_65_ffffff_1x400.png
640 ms
ui-bg_glass_100_f6f6f6_1x400.png
712 ms
laquo.png
715 ms
mapbg.png
759 ms
raquo.png
829 ms
laquo2.png
830 ms
raquo2.png
875 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
46 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
55 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
54 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
52 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
53 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
55 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
55 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
56 ms
KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff
58 ms
KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff
57 ms
KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff
56 ms
KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff
58 ms
KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff
78 ms
KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff
79 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
80 ms
KFOlCnqEu92Fr1MmSU5fChc-AMP6lbBP.woff
81 ms
KFOlCnqEu92Fr1MmSU5fCxc-AMP6lbBP.woff
79 ms
KFOlCnqEu92Fr1MmSU5fBxc-AMP6lbBP.woff
81 ms
KFOlCnqEu92Fr1MmSU5fCBc-AMP6lbBP.woff
80 ms
KFOlCnqEu92Fr1MmSU5fABc-AMP6lbBP.woff
83 ms
KFOlCnqEu92Fr1MmSU5fCRc-AMP6lbBP.woff
85 ms
KFOkCnqEu92Fr1MmgVxIIzQXKMny.woff
84 ms
KFOkCnqEu92Fr1MmgVxGIzQXKMnyrYk.woff
87 ms
KFOkCnqEu92Fr1MmgVxHIzQXKMnyrYk.woff
86 ms
KFOkCnqEu92Fr1MmgVxLIzQXKMnyrYk.woff
85 ms
KFOkCnqEu92Fr1MmgVxEIzQXKMnyrYk.woff
86 ms
KFOkCnqEu92Fr1MmgVxMIzQXKMnyrYk.woff
87 ms
KFOkCnqEu92Fr1MmgVxFIzQXKMnyrYk.woff
88 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
86 ms
KFOlCnqEu92Fr1MmWUlfChc-AMP6lbBP.woff
88 ms
KFOlCnqEu92Fr1MmWUlfCxc-AMP6lbBP.woff
87 ms
KFOlCnqEu92Fr1MmWUlfBxc-AMP6lbBP.woff
88 ms
KFOlCnqEu92Fr1MmWUlfCBc-AMP6lbBP.woff
88 ms
KFOlCnqEu92Fr1MmWUlfABc-AMP6lbBP.woff
90 ms
KFOlCnqEu92Fr1MmWUlfCRc-AMP6lbBP.woff
90 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5XpjLdSL57k.woff
89 ms
slick.woff
23 ms
collect
58 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBA5XpjLdSL57k24Q.woff
71 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBB5XpjLdSL57k24Q.woff
42 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBN5XpjLdSL57k24Q.woff
43 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBC5XpjLdSL57k24Q.woff
44 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBK5XpjLdSL57k24Q.woff
42 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBD5XpjLdSL57k24Q.woff
41 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5XpjLdSL57k.woff
42 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBA5XpjLdSL57k24Q.woff
40 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBB5XpjLdSL57k24Q.woff
41 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBN5XpjLdSL57k24Q.woff
41 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBC5XpjLdSL57k24Q.woff
41 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBK5XpjLdSL57k24Q.woff
39 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBD5XpjLdSL57k24Q.woff
39 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5XpjLdSL57k.woff
38 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBA5XpjLdSL57k24Q.woff
39 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBB5XpjLdSL57k24Q.woff
38 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBN5XpjLdSL57k24Q.woff
38 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBC5XpjLdSL57k24Q.woff
38 ms
js
84 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBK5XpjLdSL57k24Q.woff
37 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBD5XpjLdSL57k24Q.woff
35 ms
mpk.gniezno.pl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
mpk.gniezno.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
mpk.gniezno.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mpk.gniezno.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 Mpk.gniezno.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.
mpk.gniezno.pl
Open Graph description is not detected on the main page of MPK Gniezno. 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: