5.5 sec in total
1.5 sec
3.4 sec
514 ms
Click here to check amazing Liegnitz content for Poland. Otherwise, check out these important facts you probably never knew about liegnitz.pl
Przedwojennej Legnicy już nie ma. Tu odbudowujemy ją wirtualnie. Chodzimy jej ulicami, poznajemy ludzi, ich codzienność, pracę i pasje. Bez polityki, bez uprzedzeń. Z miłości do miasta.
Visit liegnitz.plWe analyzed Liegnitz.pl page load time and found that the first response time was 1.5 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
liegnitz.pl performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value3.6 s
61/100
25%
Value3.5 s
88/100
10%
Value550 ms
54/100
30%
Value0.015
100/100
15%
Value3.5 s
92/100
10%
1517 ms
246 ms
453 ms
450 ms
451 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 98% of them (65 requests) were addressed to the original Liegnitz.pl, 2% (1 request) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Liegnitz.pl.
Page size can be reduced by 124.1 kB (22%)
564.4 kB
440.3 kB
In fact, the total size of Liegnitz.pl main page is 564.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 409.2 kB which makes up the majority of the site volume.
Potential reduce by 33.7 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.5 kB, which is 15% 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 33.7 kB or 80% of the original size.
Potential reduce by 13.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. Liegnitz images are well optimized though.
Potential reduce by 63.2 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 63.2 kB or 66% of the original size.
Potential reduce by 13.8 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. Liegnitz.pl needs all CSS files to be minified and compressed as it can save up to 13.8 kB or 80% of the original size.
Number of requests can be reduced by 20 (31%)
65
45
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Liegnitz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
liegnitz.pl
1517 ms
jquery.min.js
246 ms
jquery.fancybox-1.3.4.pack.js
453 ms
jquery.fancybox-1.3.4.css
450 ms
liegnitz.css
451 ms
mt_parts.js
440 ms
corner_tl.gif
128 ms
flag_DE.gif
124 ms
corner_tr.gif
126 ms
h1.gif
126 ms
h2.gif
356 ms
h3.gif
244 ms
0.gif
238 ms
hlogo.gif
239 ms
vt_n_0.gif
240 ms
vt_mline.gif
240 ms
vt_s0.gif
356 ms
vt_s1.gif
355 ms
vt_l_0.gif
358 ms
vt_0.gif
359 ms
legnica.gif
357 ms
wuppertal.gif
470 ms
muzeum_miedzi.gif
473 ms
archiwum.gif
472 ms
sklep_kolekcjoner.gif
476 ms
lck.gif
476 ms
lpgk.gif
476 ms
vitro.gif
587 ms
qubus.gif
591 ms
P.gif
591 ms
m%200347%20a.jpg
839 ms
rd%200033%20a.jpg
945 ms
cranz02.jpg
710 ms
ak%200068%20a.jpg
706 ms
lm%200779%20a.jpg
707 ms
lm%200751%20a.jpg
708 ms
zg%200977%20a.jpg
821 ms
kirst%20jungmann%20002.jpg
826 ms
kirst%20jungmann%20001.jpg
826 ms
box_orn.gif
834 ms
corner_bl.gif
939 ms
edge_pbaron.gif
942 ms
contact.php
855 ms
hbe.gif
854 ms
corner_br.gif
856 ms
edge_ht.gif
946 ms
edge_vl.gif
837 ms
map3.jpg
1070 ms
mnico.gif
848 ms
ico_seek.gif
838 ms
butt_go.gif
846 ms
unsupportedbrowser
96 ms
old_paper_bg.jpg
836 ms
box_orn_bg_lite.gif
838 ms
m%201246%20a.jpg
842 ms
m%200273%20a.jpg
847 ms
zg%200238%20a.jpg
844 ms
harrach%20004%20franz%20krueger%20ausritt%20der%20fuerstin%20liegnitz.jpg
945 ms
m%202421%20a.jpg
840 ms
edge_vr.gif
844 ms
edge_vls_b.gif
844 ms
map1_bs.jpg
847 ms
edge_vr1.gif
948 ms
edge_hb1.gif
947 ms
l_foot_db.gif
842 ms
contact_up.css
468 ms
liegnitz.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.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
liegnitz.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
liegnitz.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
N/A
ISO-8859-2
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liegnitz.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Liegnitz.pl main page’s claimed encoding is iso-8859-2. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
liegnitz.pl
Open Graph description is not detected on the main page of Liegnitz. 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: