4.1 sec in total
442 ms
3.4 sec
211 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 442 ms and then it took 3.6 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.5 s
6/100
10%
Value7.4 s
4/100
25%
Value6.9 s
33/100
10%
Value120 ms
97/100
30%
Value0.034
100/100
15%
Value8.4 s
39/100
10%
442 ms
961 ms
64 ms
79 ms
122 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 72% of them (47 requests) were addressed to the original Mpk.gniezno.pl, 12% (8 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Mpk.gniezno.pl.
Page size can be reduced by 965.3 kB (34%)
2.8 MB
1.8 MB
In fact, the total size of Mpk.gniezno.pl main page is 2.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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 17.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 5.5 kB, which is 26% 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 17.0 kB or 81% of the original size.
Potential reduce by 100.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. MPK Gniezno images are well optimized though.
Potential reduce by 654.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 654.8 kB or 80% of the original size.
Potential reduce by 192.5 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 192.5 kB or 83% of the original size.
Number of requests can be reduced by 38 (70%)
54
16
The browser has sent 54 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 16 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
mpk.gniezno.pl
442 ms
www.mpk.gniezno.pl
961 ms
css
64 ms
css
79 ms
jquery.bxslider.css
122 ms
prettyPhoto.css
240 ms
fm.checkator.jquery.css
243 ms
jquery-ui.css
244 ms
slick.css
10 ms
slick-theme.css
11 ms
bootstrap.min.css
365 ms
default.css
247 ms
mpk.css
247 ms
mpk_responsive.css
356 ms
default_responsive.css
359 ms
respond.js
360 ms
html5shiv.js
362 ms
jsapi
21 ms
jquery-1.11.3.min.js
488 ms
jquery.touchwipe.min.js
505 ms
jquery.prettyPhoto.js
505 ms
jquery.bxslider.js
478 ms
fm.checkator.jquery.js
503 ms
jquery-ui.js
737 ms
inputmask.js
606 ms
jquery.inputmask.js
605 ms
slick.min.js
19 ms
app.js
606 ms
shop.js
625 ms
responsive.js
613 ms
print.css
166 ms
analytics.js
158 ms
ajax-loader.gif
38 ms
topbgpattern.png
135 ms
mpklogo.png
122 ms
f.png
124 ms
t.png
124 ms
g.png
124 ms
14490403581565e99e662960270161076.png
862 ms
14490402851565e999da6028352298596.png
1073 ms
14490403201565e99c02caf6367157600.png
1076 ms
streets2.png
362 ms
search.png
239 ms
pin.png
250 ms
burger.png
361 ms
timer.png
368 ms
14466466601563a13846f2cf805961493.png
478 ms
14466466791563a1397580aa977400881.png
480 ms
14466467041563a13b0b4dc4526185000.png
487 ms
pin2.png
601 ms
laquo.png
598 ms
mapbg.png
849 ms
raquo.png
717 ms
laquo2.png
719 ms
raquo2.png
837 ms
Zd2E9abXLFGSr9G3YK2MsK8NE7_Gi-Xz52ZQ_AwfA78.woff
74 ms
b9QBgL0iMZfDSpmcXcE8nCj3Mi2hOMP9GNHlaDA9WRI.woff
85 ms
b9QBgL0iMZfDSpmcXcE8nJT5GEmoOtNsejy4tIPLwv0.woff
96 ms
97uahxiqZRoncBaCEI3aWz8E0i7KZn-EPnyo3HZu7kw.woff
111 ms
oOeFwZNlrTefzLYmlVV1UD8E0i7KZn-EPnyo3HZu7kw.woff
112 ms
Xyjz-jNkfiYuJf8UC3Lizw.woff
118 ms
Pru33qjShpZSmG3z6VYwnT8E0i7KZn-EPnyo3HZu7kw.woff
117 ms
idLYXfFa1c7oAPILDl4z0fesZW2xOQ-xsNqO47m55DA.woff
136 ms
slick.woff
17 ms
collect
26 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 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
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: