4.4 sec in total
397 ms
3.4 sec
641 ms
Click here to check amazing Leipzig content for Germany. Otherwise, check out these important facts you probably never knew about leipzig.de
Das offizielle Internet-Portal für Leipziger Bürger, Touristen und Unternehmen. Ein Service der Stadt Leipzig.
Visit leipzig.deWe analyzed Leipzig.de page load time and found that the first response time was 397 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
leipzig.de performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value11.9 s
0/100
25%
Value8.6 s
17/100
10%
Value1,050 ms
25/100
30%
Value0.008
100/100
15%
Value11.8 s
17/100
10%
397 ms
523 ms
429 ms
345 ms
448 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 24% of them (25 requests) were addressed to the original Leipzig.de, 69% (71 requests) were made to Cdn.leipzig.de and 3% (3 requests) were made to Oxa.lvz-service.de. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cdn.leipzig.de.
Page size can be reduced by 915.1 kB (17%)
5.5 MB
4.6 MB
In fact, the total size of Leipzig.de main page is 5.5 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 4.4 MB which makes up the majority of the site volume.
Potential reduce by 120.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 120.4 kB or 82% of the original size.
Potential reduce by 86.2 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. Leipzig images are well optimized though.
Potential reduce by 435.1 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 435.1 kB or 72% of the original size.
Potential reduce by 273.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. Leipzig.de needs all CSS files to be minified and compressed as it can save up to 273.4 kB or 85% of the original size.
Number of requests can be reduced by 32 (33%)
98
66
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leipzig. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
leipzig.de
397 ms
www.leipzig.de
523 ms
stylesheet_2ea8fa9da3.css
429 ms
jqfancybox.css
345 ms
site.css
448 ms
opera.css
354 ms
chrome.css
343 ms
style.css
225 ms
spcjs.php
460 ms
jquery-1.7.2.min.js
490 ms
jquery-ui-1.10.3.custom.min.js
648 ms
jquery.roundabout.min.js
442 ms
mapper.js
442 ms
custom-form-elements.js
456 ms
jquery.fancybox-1.3.3.min.js
543 ms
custom.js
544 ms
ajaxcontent.js
543 ms
iam.js
396 ms
jquery.uncomment.js
219 ms
jquery.socialmediaprivacy.js
219 ms
javascript_a708894199.js
218 ms
safari.css
547 ms
webtrekk_v3.js
107 ms
multisearch.js
121 ms
spc.php
569 ms
fl.js
239 ms
print.css
104 ms
bg_layer.png
104 ms
dummy_twitter.png
106 ms
bg_header.png
104 ms
dummy_facebook.png
107 ms
dummy_gplus.png
109 ms
socialmediaprivacy.css
109 ms
PT_Sans.woff
265 ms
logo.png
110 ms
79677f12e7.jpg
511 ms
cff1943b81.jpg
511 ms
f0e5e44410.jpg
497 ms
6f8d0e01a8.jpg
600 ms
cd41b705a4.jpg
614 ms
1b93250b88.jpg
507 ms
74306f3c88.jpg
802 ms
35060e09a4.jpg
611 ms
9ec0c2352b.jpg
613 ms
fb5fd188c3.jpg
719 ms
9ae56475bd.jpg
802 ms
b328ab23e9.jpg
712 ms
telefon_sidebar.png
713 ms
a6573a3330.jpg
717 ms
ed7ca8e094.jpg
814 ms
053ff9f2a8.jpg
814 ms
e27dc3f981.jpg
815 ms
f4fa7cd70e.jpg
917 ms
9446f9a633.jpg
902 ms
46d4c91071.jpg
903 ms
13549bcdd3.jpg
1015 ms
f4c81e3c3e.jpg
1015 ms
pdf.png
916 ms
a0fe4b4e29.jpg
1003 ms
d9393d88a9.jpg
1004 ms
06e4f53e32.jpg
1118 ms
9d648c62d1.jpg
1018 ms
telefon_footer.png
1105 ms
Behoerdenwegweiser_05.png
1105 ms
buergeraemter_05.png
1115 ms
formulare_05.png
1116 ms
eris_05.png
1118 ms
79111a78c6.jpg
256 ms
26ce1978a8.jpg
257 ms
1ea1c5f0db.jpg
492 ms
c529fc542e.jpg
254 ms
d05eb4176b.jpg
292 ms
34ff197e32.jpg
300 ms
07d032b7d6.jpg
293 ms
009e579329.jpg
314 ms
2e07346472.jpg
417 ms
5eb6e29f4f.jpg
595 ms
1fa305c540.jpg
596 ms
3742b60ec3.jpg
610 ms
facebook.png
1130 ms
twitter.png
1127 ms
rss.png
1106 ms
wt
239 ms
tx.io
190 ms
PT_Sans_Bold.woff
1061 ms
tx.io
95 ms
instagram.jpg
730 ms
cb0d570821.jpg
718 ms
select_language.png
805 ms
search.png
804 ms
anzeige.gif
739 ms
link_intern.png
728 ms
bg_footer.png
726 ms
print.png
803 ms
mail_new.png
703 ms
arrow_up.png
710 ms
link_intern_grey.png
706 ms
btnPrev.png
709 ms
btnNext.png
630 ms
btnToggleAutoplay.png
718 ms
tab.png
704 ms
bg_coverflow_navigation.png
713 ms
tab_active.png
712 ms
leipzig.de 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-hidden="true"] elements contain focusable descendents
leipzig.de 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
Missing source maps for large first-party JavaScript
leipzig.de 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leipzig.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Leipzig.de 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.
leipzig.de
Open Graph description is not detected on the main page of Leipzig. 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: