2.7 sec in total
471 ms
1.9 sec
351 ms
Click here to check amazing LAZARZ content for Poland. Otherwise, check out these important facts you probably never knew about lazarz.pl
.:LAZARZ.PL-/poznański portal dzielnicowy:. - e-Ł@zarz, czyli Twoja dzielnica, Łazarz w zasięgu myszki. Zapomniałeś wysłać list? Nie wykupiłeś leku w aptece? Nie wiesz jak sprawowane są msze święte w ...
Visit lazarz.plWe analyzed Lazarz.pl page load time and found that the first response time was 471 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
lazarz.pl performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value1.2 s
100/100
25%
Value8.2 s
20/100
10%
Value1,520 ms
13/100
30%
Value0.242
51/100
15%
Value16.1 s
6/100
10%
471 ms
237 ms
240 ms
241 ms
243 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 52% of them (52 requests) were addressed to the original Lazarz.pl, 20% (20 requests) were made to O.twimg.com and 8% (8 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Lazarz.pl.
Page size can be reduced by 149.7 kB (14%)
1.1 MB
937.9 kB
In fact, the total size of Lazarz.pl main page is 1.1 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. 60% of websites need less resources to load. Images take 881.8 kB which makes up the majority of the site volume.
Potential reduce by 31.4 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 31.4 kB or 73% of the original size.
Potential reduce by 21.1 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. LAZARZ images are well optimized though.
Potential reduce by 55.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 55.8 kB or 50% of the original size.
Potential reduce by 41.4 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. Lazarz.pl needs all CSS files to be minified and compressed as it can save up to 41.4 kB or 83% of the original size.
Number of requests can be reduced by 29 (29%)
99
70
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LAZARZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
lazarz.pl
471 ms
lazarz.css
237 ms
aktu.css
240 ms
glowna.css
241 ms
slimbox.css
243 ms
mootools.js
362 ms
slimbox.js
244 ms
swfobject.js
353 ms
funkcje.js
353 ms
script1.js
356 ms
show_ads.js
7 ms
ga.js
8 ms
__utm.gif
15 ms
lazarzpl.png
273 ms
glowna.jpg
268 ms
lslide.png
175 ms
zz.png
140 ms
live.gif
176 ms
aimg.php
222 ms
aimg.php
326 ms
aimg.php
308 ms
aimg.php
326 ms
aimg.php
386 ms
aimg.php
438 ms
aimg.php
448 ms
aimg.php
491 ms
aimg.php
508 ms
aimg.php
488 ms
aimg.php
566 ms
aimg.php
608 ms
planmini.png
572 ms
herb_lazarza.jpg
609 ms
aimg.php
665 ms
aimg.php
677 ms
aimg.php
702 ms
aimg.php
739 ms
aimg.php
772 ms
aimg.php
772 ms
aimg.php
830 ms
youtube.gif
795 ms
periscope.gif
816 ms
facebook.gif
857 ms
twitter.gif
892 ms
osiedlelazarz.png
1011 ms
krag.jpg
913 ms
kubala_ksero-bok.gif
935 ms
24.gif
948 ms
lazarzpl-ft.png
973 ms
_sg.jpg
1113 ms
ca-pub-0601544420292928.js
70 ms
zrt_lookup.html
83 ms
show_ads_impl.js
83 ms
all.js
180 ms
widgets.js
37 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
62 ms
ads
277 ms
tab1a.png
865 ms
tab2p.png
885 ms
osd.js
13 ms
tabh1a.png
896 ms
syndication
111 ms
686341415903825920
227 ms
tabcon.png
878 ms
68 ms
tabft.png
866 ms
xd_arbiter.php
131 ms
xd_arbiter.php
293 ms
kal.png
886 ms
proxy.jpg
97 ms
proxy.jpg
85 ms
proxy.jpg
126 ms
proxy.jpg
132 ms
proxy.jpg
83 ms
proxy.jpg
73 ms
proxy.jpg
81 ms
proxy.jpg
124 ms
proxy.jpg
92 ms
proxy.jpg
91 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
19 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
45 ms
7PDBCTVe_normal.png
138 ms
Cd4UNniXEAAsUTJ.jpg:small
209 ms
Cd4JQPWXEAAeEp8.jpg:small
237 ms
Cd4BdjdVAAAV7ci.jpg:small
292 ms
Cd2jUaKWIAE_T4k.jpg:small
379 ms
Cd1l4d2XIAAr06H.jpg:small
283 ms
CdzHvRdXEAEjUJf.jpg:small
299 ms
Cdy3lxlXIAAvdfb.jpg:small
297 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
57 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
84 ms
proxy.jpg
43 ms
proxy.jpg
33 ms
proxy.jpg
28 ms
proxy.jpg
29 ms
proxy.jpg
3 ms
proxy.jpg
5 ms
proxy.jpg
7 ms
proxy.jpg
7 ms
proxy.jpg
48 ms
proxy.jpg
5 ms
lazarz.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-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
lazarz.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
Page has valid source maps
lazarz.pl SEO score
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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lazarz.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 Lazarz.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.
lazarz.pl
Open Graph description is not detected on the main page of LAZARZ. 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: