9.5 sec in total
1 sec
8.3 sec
208 ms
Click here to check amazing Sm content for Poland. Otherwise, check out these important facts you probably never knew about sm.poznan.pl
Straż miejska
Visit sm.poznan.plWe analyzed Sm.poznan.pl page load time and found that the first response time was 1 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
sm.poznan.pl performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value11.5 s
0/100
25%
Value13.2 s
2/100
10%
Value450 ms
63/100
30%
Value0.163
72/100
15%
Value7.4 s
48/100
10%
1028 ms
217 ms
219 ms
220 ms
228 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 88% of them (130 requests) were addressed to the original Sm.poznan.pl, 11% (16 requests) were made to Www.poznan.pl and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Www.poznan.pl.
Page size can be reduced by 552.4 kB (34%)
1.6 MB
1.1 MB
In fact, the total size of Sm.poznan.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. 25% of websites need less resources to load. Images take 958.6 kB which makes up the majority of the site volume.
Potential reduce by 39.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 39.0 kB or 80% of the original size.
Potential reduce by 46.7 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. Sm images are well optimized though.
Potential reduce by 372.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 372.6 kB or 74% of the original size.
Potential reduce by 94.1 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. Sm.poznan.pl needs all CSS files to be minified and compressed as it can save up to 94.1 kB or 82% of the original size.
Number of requests can be reduced by 39 (45%)
86
47
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
sm.poznan.pl
1028 ms
normalize.min.css
217 ms
base.css
219 ms
main.css
220 ms
top.css
228 ms
media.query.css
229 ms
helper.css
419 ms
print.css
419 ms
lightbox.css
432 ms
fonts.css
432 ms
pcss.css
440 ms
modernizr-2.6.2-respond-1.1.0.min.js
621 ms
prototype.js
634 ms
scriptaculous.js
643 ms
builder.js
644 ms
effects.js
645 ms
dragdrop.js
653 ms
controls.js
822 ms
slider.js
849 ms
psnc_controls.js
856 ms
normalize.min.css
777 ms
base.css
774 ms
main.css
777 ms
top.css
767 ms
media.query.css
998 ms
helper.css
584 ms
print.css
776 ms
main.js
442 ms
lightbox.css
765 ms
fonts.css
773 ms
pcss.css
980 ms
modernizr-2.6.2-respond-1.1.0.min.js
810 ms
prototype.js
1525 ms
scriptaculous.js
769 ms
builder.js
765 ms
effects.js
1122 ms
dragdrop.js
1293 ms
controls.js
1126 ms
slider.js
878 ms
psnc_controls.js
789 ms
main.js
1217 ms
menu.css
1076 ms
vortal-header.css
993 ms
slider-big.css
1259 ms
bar.css
1172 ms
boxes.css
1398 ms
slider-small.css
1290 ms
footer.css
1299 ms
calendar.css
1369 ms
content-category-header.css
1400 ms
arimo.css
1266 ms
pt-sans-caption.css
1296 ms
wcag.css
1090 ms
search.css
523 ms
contrast.css
541 ms
sound.js
110 ms
close.png
110 ms
loading.gif
357 ms
prev.png
218 ms
next.png
229 ms
sound.js
206 ms
picture,pic1,1002,0,135086,with-ratio,1_1.jpg
217 ms
main-logo.png
228 ms
menu-open.png
225 ms
close.png
222 ms
icon-bip.png
224 ms
icon-high-contrast.png
229 ms
contrast-sprite.png
232 ms
icon-contrast.png
438 ms
icon-search-blue.png
434 ms
slider-left.png
447 ms
social.png
448 ms
chmury.png
456 ms
picture,pic1,1002,0,135081,with-ratio,1_1.jpg
206 ms
picture,pic1,1002,0,135076,with-ratio,1_1.jpg
217 ms
picture,pic1,1002,0,135071,with-ratio,1_1.jpg
218 ms
picture,pic1,1002,0,135062,with-ratio,1_1.jpg
219 ms
picture,pic1,1002,0,134879,with-ratio,1_1.jpg
229 ms
picture,pic1,1002,0,134867,with-ratio,1_1.jpg
420 ms
picture,pic1,1002,0,134859,with-ratio,1_1.jpg
424 ms
picture,pic1,1002,0,134851,with-ratio,1_1.jpg
434 ms
picture,pic1,1002,0,134732,with-ratio,1_1.jpg
430 ms
picture,pic1,1002,0,134723,with-ratio,1_1.jpg
434 ms
picture,pic1,1002,0,134713,with-ratio,1_1.jpg
457 ms
picture,pic1,1002,0,134641,with-ratio,1_1.jpg
638 ms
picture,pic1,1002,0,134519,with-ratio,1_1.jpg
644 ms
picture,pic1,1002,0,134518,with-ratio,1_1.jpg
644 ms
picture,pic1,1002,0,134475,with-ratio,1_1.jpg
655 ms
btn-more-pl.png
662 ms
ajax_indicator.gif
683 ms
mapa.jpg
853 ms
slider-right.png
425 ms
bullet-box.png
604 ms
ptsanscaption-v7-400.woff
1012 ms
ptsanscaption-v7-700.woff
1067 ms
arimo-v6-400.woff
1170 ms
arimo-v6-700.woff
1137 ms
jquery-1.11.2.min.js
812 ms
picture,pic1,1002,0,135081,with-ratio,1_1.jpg
468 ms
picture,pic1,1002,0,135086,with-ratio,1_1.jpg
631 ms
picture,pic1,1002,0,135076,with-ratio,1_1.jpg
672 ms
picture,pic1,1002,0,135071,with-ratio,1_1.jpg
854 ms
picture,pic1,1002,0,135062,with-ratio,1_1.jpg
908 ms
picture,pic1,1002,0,134879,with-ratio,1_1.jpg
1033 ms
picture,pic1,1002,0,134867,with-ratio,1_1.jpg
869 ms
picture,pic1,1002,0,134859,with-ratio,1_1.jpg
896 ms
picture,pic1,1002,0,134732,with-ratio,1_1.jpg
891 ms
picture,pic1,1002,0,134851,with-ratio,1_1.jpg
940 ms
picture,pic1,1002,0,134723,with-ratio,1_1.jpg
988 ms
picture,pic1,1002,0,134713,with-ratio,1_1.jpg
1022 ms
picture,pic1,1002,0,134641,with-ratio,1_1.jpg
879 ms
picture,pic1,1002,0,134519,with-ratio,1_1.jpg
890 ms
picture,pic1,1002,0,134518,with-ratio,1_1.jpg
901 ms
picture,pic1,1002,0,134475,with-ratio,1_1.jpg
932 ms
btn-more-pl.png
976 ms
picture,pic1,1002,0,135081,with-ratio,1_1.jpg
1141 ms
ajax_indicator.gif
1000 ms
picture,pic1,1002,0,135086,with-ratio,1_1.jpg
1257 ms
jquery-1.11.2.min.js
1424 ms
mapa.jpg
1249 ms
picture,pic1,1002,0,135076,with-ratio,1_1.jpg
901 ms
picture,pic1,1002,0,135071,with-ratio,1_1.jpg
1061 ms
picture,pic1,1002,0,135062,with-ratio,1_1.jpg
880 ms
picture,pic1,1002,0,134879,with-ratio,1_1.jpg
975 ms
picture,pic1,1002,0,134867,with-ratio,1_1.jpg
1035 ms
picture,pic1,1002,0,134859,with-ratio,1_1.jpg
1054 ms
picture,pic1,1002,0,134732,with-ratio,1_1.jpg
1455 ms
picture,pic1,1002,0,134851,with-ratio,1_1.jpg
1829 ms
picture,pic1,1002,0,134723,with-ratio,1_1.jpg
1204 ms
picture,pic1,1002,0,134713,with-ratio,1_1.jpg
1630 ms
picture,pic1,1002,0,134641,with-ratio,1_1.jpg
1245 ms
picture,pic1,1002,0,134519,with-ratio,1_1.jpg
1706 ms
picture,pic1,1002,0,134518,with-ratio,1_1.jpg
1973 ms
picture,pic1,1002,0,134475,with-ratio,1_1.jpg
2127 ms
jquery.dotdotdot.min.js
110 ms
jquery.dotdotdot.min.js
310 ms
jquery.touchswipe.min.js
217 ms
jquery.touchswipe.min.js
326 ms
lightbox.min.js
218 ms
lightbox.min.js
432 ms
pl_PL.js
216 ms
pl_PL.js
229 ms
ga.js
34 ms
icon-pcss.png
229 ms
top-new.png
206 ms
icon-contrast_big.png
222 ms
icon-high-contrast_big.png
223 ms
__utm.gif
14 ms
sm.poznan.pl accessibility score
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
sm.poznan.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
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
sm.poznan.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Sm.poznan.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 Sm.poznan.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.
sm.poznan.pl
Open Graph description is not detected on the main page of Sm. 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: