5.3 sec in total
885 ms
4.3 sec
176 ms
Visit leibniz.at now to see the best up-to-date LEIBNIZ content for Austria and also check out these interesting facts you probably never knew about leibniz.at
Willkommen bei LEIBNIZ. Lernt unsere Produkte kennen, erfahrt wo unsere Zutaten herkommen, und taucht ein in über 130 Jahre Keksgeschichte.
Visit leibniz.atWe analyzed Leibniz.at page load time and found that the first response time was 885 ms and then it took 4.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.
leibniz.at performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value11.8 s
0/100
25%
Value10.6 s
7/100
10%
Value8,080 ms
0/100
30%
Value0.084
93/100
15%
Value14.4 s
9/100
10%
885 ms
125 ms
244 ms
248 ms
249 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 96% of them (54 requests) were addressed to the original Leibniz.at, 2% (1 request) were made to Code.etracker.com and 2% (1 request) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Leibniz.at.
Page size can be reduced by 445.4 kB (79%)
566.8 kB
121.4 kB
In fact, the total size of Leibniz.at main page is 566.8 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. Javascripts take 533.8 kB which makes up the majority of the site volume.
Potential reduce by 11.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 3.4 kB, which is 22% 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 11.7 kB or 77% of the original size.
Potential reduce by 420.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 420.6 kB or 79% of the original size.
Potential reduce by 13.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. Leibniz.at needs all CSS files to be minified and compressed as it can save up to 13.1 kB or 74% of the original size.
Number of requests can be reduced by 33 (60%)
55
22
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LEIBNIZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
leibniz.at
885 ms
index.css
125 ms
helper.css
244 ms
typography.css
248 ms
site.css
249 ms
content.css
253 ms
elements.css
248 ms
cms_header.css
257 ms
jquery-1.7.2.min.js
605 ms
soundmanager2.js
619 ms
index.js
372 ms
utzlayer.js
365 ms
etc.js
380 ms
ajax.js
380 ms
class-handler.js
483 ms
layer.js
494 ms
prototype.js
636 ms
scriptaculous.js
501 ms
swfobject.js
615 ms
body_bg.jpg
370 ms
builder.js
126 ms
effects.js
129 ms
dragdrop.js
123 ms
controls.js
126 ms
slider.js
124 ms
sound.js
126 ms
karusellteaser_Snoopy.png
618 ms
karusellteaser_CHOCO_BW.png
379 ms
karusellteaser_MinisBW.png
480 ms
home_teaser_LBPromo2015_FINAL.png
961 ms
karusellteaser_ZooUrzeit_Promo2016_1.png
600 ms
ATT5AH25.png
2453 ms
Button_Startseite_UTZ.png
876 ms
home_promo_ZooUrzeit.png
717 ms
footer_bahlsen.jpg
719 ms
footer_pickup.jpg
742 ms
footer_facebook.jpg
837 ms
footer_print.gif
840 ms
loader.gif
865 ms
logo.gif
946 ms
search_bg.gif
948 ms
search_button.gif
981 ms
sound_on.gif
990 ms
content_bg.gif
1065 ms
home_bg1.jpg
1465 ms
home_caroussel_arrowup.png
1072 ms
home_caroussel_arrowdown.png
1102 ms
footer_bg.gif
1108 ms
main_nav_01.jpg
1184 ms
main_nav_02.jpg
1186 ms
main_nav_03.jpg
1224 ms
main_nav_04.jpg
1234 ms
loader_bg.png
1300 ms
t.js
401 ms
cnt_js.php
264 ms
print_only.css
125 ms
leibniz.at accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
leibniz.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
leibniz.at 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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leibniz.at can be misinterpreted by Google and other search engines. Our service has detected that German 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 Leibniz.at 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.
leibniz.at
Open Graph description is not detected on the main page of LEIBNIZ. 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: