6.8 sec in total
1.6 sec
4.9 sec
263 ms
Welcome to tobiaslindner.eu homepage info - get ready to check Tobias Lindner best content right away, or after learning these important things about tobiaslindner.eu
Hier finden Sie dieses und jenes zum Thema Wirtschaftsinformatik und meiner Leidenschaft, dem Reisen und der Fotografie.
Visit tobiaslindner.euWe analyzed Tobiaslindner.eu page load time and found that the first response time was 1.6 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tobiaslindner.eu performance score
name
value
score
weighting
Value2.7 s
58/100
10%
Value2.7 s
84/100
25%
Value6.4 s
40/100
10%
Value1,070 ms
25/100
30%
Value0
100/100
15%
Value10.4 s
24/100
10%
1643 ms
221 ms
221 ms
218 ms
222 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 97% of them (61 requests) were addressed to the original Tobiaslindner.eu, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Tobiaslindner.eu.
Page size can be reduced by 324.6 kB (21%)
1.5 MB
1.2 MB
In fact, the total size of Tobiaslindner.eu main page is 1.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. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 19.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. 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 19.7 kB or 80% of the original size.
Potential reduce by 30.3 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. Tobias Lindner images are well optimized though.
Potential reduce by 189.0 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 189.0 kB or 67% of the original size.
Potential reduce by 85.7 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. Tobiaslindner.eu needs all CSS files to be minified and compressed as it can save up to 85.7 kB or 85% of the original size.
Number of requests can be reduced by 37 (60%)
62
25
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tobias Lindner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
tobiaslindner.eu
1643 ms
superfish.css
221 ms
tipTip.css
221 ms
prettyPhoto.css
218 ms
normalize.css
222 ms
boxes.css
219 ms
lists.css
224 ms
social.css
437 ms
slider.css
436 ms
viewers.css
435 ms
tabs.css
433 ms
toggles.css
441 ms
buttons.css
441 ms
columns.css
651 ms
nggallery.css
652 ms
colorbox.css
653 ms
jquery-1.7.1.min.js
765 ms
modernizr.full.min.js
657 ms
selectivizr-min.js
659 ms
superfish.js
873 ms
jquery.prettyPhoto.js
868 ms
jquery.tipTip.js
874 ms
buttons.js
876 ms
jquery.quovolver.js
879 ms
jquery.cycle.all.min.js
985 ms
jquery.cycle.all.min.js
1085 ms
ngg.slideshow.min.js
1091 ms
style.css
1095 ms
nivo-slider.css
1115 ms
jquery.nivo.slider.pack.js
1118 ms
scripts.js
1201 ms
behaviours.js
1310 ms
jquery.colorbox.js
1313 ms
ga.js
19 ms
Background.v1.jpg
1204 ms
pattern1.png
241 ms
Logo.v1.png
241 ms
bk_topmenu.png
315 ms
top_menu_separator.png
424 ms
shadow_slider.png
445 ms
loading.gif
451 ms
timthumb.php
945 ms
timthumb.php
952 ms
timthumb.php
1018 ms
timthumb.php
1040 ms
timthumb.php
1058 ms
timthumb.php
1533 ms
timthumb.php
1595 ms
timthumb.php
1599 ms
timthumb.php
1722 ms
timthumb.php
1575 ms
Fotografie.png
1430 ms
Publikationen.png
1646 ms
Projekte.png
1757 ms
hr_thick.png
1780 ms
__utm.gif
13 ms
ico_arrow.png
1768 ms
overlay.png
1583 ms
border.png
1633 ms
controls.png
1704 ms
but_prev.png
110 ms
but_next.png
232 ms
slider_controlnav.png
220 ms
tobiaslindner.eu 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
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
tobiaslindner.eu 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
tobiaslindner.eu SEO score
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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tobiaslindner.eu 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 Tobiaslindner.eu 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.
tobiaslindner.eu
Open Graph description is not detected on the main page of Tobias Lindner. 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: