4 sec in total
303 ms
3.3 sec
381 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 303 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.
lazarz.pl performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value1.9 s
98/100
25%
Value7.6 s
25/100
10%
Value4,530 ms
0/100
30%
Value0.242
51/100
15%
Value21.2 s
1/100
10%
303 ms
694 ms
304 ms
484 ms
62 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 45% of them (53 requests) were addressed to the original Lazarz.pl, 15% (18 requests) were made to Platform.twitter.com and 8% (10 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Lazarz.pl.
Page size can be reduced by 163.5 kB (8%)
2.0 MB
1.8 MB
In fact, the total size of Lazarz.pl main page is 2.0 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 1.4 MB which makes up the majority of the site volume.
Potential reduce by 47.2 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 6.8 kB, which is 11% 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 47.2 kB or 76% of the original size.
Potential reduce by 106.4 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 8.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 1.6 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 1.6 kB or 28% of the original size.
Number of requests can be reduced by 60 (55%)
110
50
The browser has sent 110 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 41 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lazarz.pl
303 ms
lazarz.pl
694 ms
lazarz.css
304 ms
jquery-1.9.1.min.js
484 ms
js
62 ms
aktu.css
323 ms
glowna.css
324 ms
slimbox2.js
333 ms
slimbox2.css
337 ms
swfobject.js
425 ms
funkcje.js
428 ms
script1.js
431 ms
zgoda.png
441 ms
logo_34dl.png
618 ms
simg.php
689 ms
simg.php
622 ms
simg.php
692 ms
pizzeriasangiovanni.jpg
731 ms
simg.php
621 ms
simg.php
772 ms
simg.php
834 ms
simg.php
862 ms
simg.php
867 ms
simg.php
885 ms
simg.php
908 ms
planmini.png
927 ms
herb_lazarza.jpg
900 ms
simg.php
1047 ms
simg.php
1138 ms
simg.php
1121 ms
simg.php
1100 ms
simg.php
1063 ms
simg.php
1120 ms
simg.php
1270 ms
simg.php
1240 ms
simg.php
1311 ms
infokostrzyn.png
1218 ms
youtube.gif
1240 ms
adsbygoogle.js
162 ms
facebook.gif
1158 ms
twitter.gif
1117 ms
kubala-poduszki_bok.png
1270 ms
24.gif
1142 ms
lazarzpl-ft.png
1129 ms
lazarzpl.png
968 ms
glowna.jpg
1401 ms
lslide.png
1009 ms
zz.png
1075 ms
_sg.jpg
1062 ms
tab1a.png
1062 ms
show_ads_impl.js
243 ms
all.js
22 ms
tab2p.png
1042 ms
widgets.js
98 ms
all.js
12 ms
tabh1a.png
1227 ms
tabcon.png
1223 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
57 ms
tabft.png
1161 ms
kal.png
1156 ms
settings
138 ms
zrt_lookup.html
47 ms
ads
367 ms
ads
476 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
22 ms
lazarzpl
90 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
23 ms
runtime-b1c52fd0a13ead5fcf6b.js
50 ms
modules-96ebc7ac3ad66d681a3d.js
72 ms
main-babd9234dc048fb47339.js
82 ms
_app-a9c9f1a99e4414675fb1.js
100 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
104 ms
_buildManifest.js
116 ms
_ssgManifest.js
117 ms
8526.0c32a8f0cfc5749221a3.js
25 ms
1755.07a49c40b12af4f75780.js
22 ms
8283.f3e5048cca7cef5eed7f.js
25 ms
3077.44bfeb00af01bc4020f6.js
48 ms
1362.42d432e02f7980bca032.js
42 ms
4956.c4e51ef593974b9db0bb.js
80 ms
5893.d500bd2a89ded806aa73.js
27 ms
reactive_library.js
151 ms
load_preloaded_resource.js
55 ms
icon.png
25 ms
abg_lite.js
54 ms
s
30 ms
window_focus.js
53 ms
qs_click_protection.js
53 ms
ufs_web_display.js
30 ms
e92e9b19fdbae9b3a3ef41360efccaf5.js
277 ms
fullscreen_api_adapter.js
262 ms
interstitial_ad_frame.js
283 ms
pixel
266 ms
6094436044053429679
281 ms
abg_lite.js
31 ms
omrhp.js
263 ms
Q12zgMmT.js
268 ms
gen_204
255 ms
feedback_grey600_24dp.png
272 ms
settings_grey600_24dp.png
274 ms
css
234 ms
pixel
147 ms
pixel
145 ms
62bHydCX.html
40 ms
activeview
103 ms
VKtwqYIMw_jEtcsYEdk2t0uWx1X5nCbHNvrRSJpikmk.js
8 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
113 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
115 ms
bounce
17 ms
rum
37 ms
pixel
20 ms
pixel
19 ms
rum
24 ms
sodar
97 ms
108 ms
sodar2.js
13 ms
runner.html
17 ms
aframe
25 ms
lazarz.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.
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
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
Links do not have a discernible name
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
Displays images with incorrect aspect ratio
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
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
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: