6.7 sec in total
1.3 sec
4.8 sec
545 ms
Visit lindebergs.de now to see the best up-to-date LINDEBERGS content and also check out these interesting facts you probably never knew about lindebergs.de
Praxis im Herzen von Bogenhausen ✅ Ganzheitliche Betreuung ✅ Perfekt ausgebildete Therapeuten ✅ Modernste Geräte ✅
Visit lindebergs.deWe analyzed Lindebergs.de page load time and found that the first response time was 1.3 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lindebergs.de performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value23.9 s
0/100
25%
Value16.2 s
0/100
10%
Value2,710 ms
3/100
30%
Value0.001
100/100
15%
Value24.1 s
0/100
10%
1294 ms
302 ms
501 ms
707 ms
305 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 66% of them (77 requests) were addressed to the original Lindebergs.de, 13% (15 requests) were made to Static.xx.fbcdn.net and 3% (4 requests) were made to Lindebergs.envonia.de. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Lindebergs.de.
Page size can be reduced by 2.0 MB (30%)
6.6 MB
4.6 MB
In fact, the total size of Lindebergs.de main page is 6.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 154.8 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 154.8 kB or 85% of the original size.
Potential reduce by 19.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. LINDEBERGS images are well optimized though.
Potential reduce by 697.7 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 697.7 kB or 71% of the original size.
Potential reduce by 1.1 MB
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. Lindebergs.de needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 85% of the original size.
Number of requests can be reduced by 71 (64%)
111
40
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LINDEBERGS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
www.lindebergs.de
1294 ms
wp-emoji-release.min.js
302 ms
shortcodes.css
501 ms
linecons.css
707 ms
pixelicons.css
305 ms
dashicons.min.css
408 ms
jquery-ui-dialog.min.css
402 ms
styles.css
407 ms
cff-style.css
506 ms
font-awesome.min.css
5 ms
settings.css
608 ms
js_composer.min.css
1425 ms
style.css
800 ms
font-awesome.min.css
602 ms
icomoon.css
703 ms
steadysets.css
708 ms
mediaelementplayer.css
761 ms
mobius-grid.css
903 ms
post-like.css
813 ms
jquery.js
1010 ms
jquery-migrate.min.js
863 ms
jquery.themepunch.tools.min.js
999 ms
jquery.themepunch.revolution.min.js
906 ms
modernizr.js
963 ms
preloader.js
1003 ms
css
23 ms
css
35 ms
css
13 ms
all.js
32 ms
easypiechart.js
371 ms
jquery.appear.js
429 ms
themeone-shortcodes.js
464 ms
core.min.js
467 ms
widget.min.js
470 ms
mouse.min.js
473 ms
resizable.min.js
527 ms
draggable.min.js
561 ms
button.min.js
565 ms
position.min.js
569 ms
dialog.min.js
572 ms
wpdialog.min.js
628 ms
post-like.js
659 ms
jquery.form.min.js
664 ms
scripts.js
668 ms
cff-scripts.js
671 ms
js_composer_front.min.js
726 ms
mediaelement-and-player.min.js
882 ms
owl.carousel.js
761 ms
easing.js
766 ms
hammer.js
771 ms
isotope.js
873 ms
sly.js
832 ms
custom.js
917 ms
comment-reply.min.js
829 ms
mobius-grid.js
777 ms
search_autocomplete.js
778 ms
ajax-comments.js
808 ms
wp-embed.min.js
759 ms
waypoints.min.js
739 ms
logo_lindebergs_300.png
187 ms
start_2.jpg
748 ms
start_1.jpg
795 ms
diagnostik_lindebergs.jpg
1235 ms
malonn.png
955 ms
transparent.png
157 ms
diagnose.jpg
762 ms
behandlung.jpg
716 ms
training2.jpg
828 ms
about_lindebergs_1.jpg
1204 ms
ambiente_3.jpg
761 ms
ambiente_2.jpg
1245 ms
ambiente_4.jpg
1202 ms
ambiente_1.jpg
952 ms
lang.png
952 ms
foertsch.png
952 ms
alschibaja.png
952 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
57 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
57 ms
icomoon.woff
873 ms
fontawesome-webfont.woff
1188 ms
fontawesome-webfont.woff
55 ms
12360246_1011309042268380_6947328160105566512_n.jpg
81 ms
www.lindebergs.de
1718 ms
484 ms
analytics.js
24 ms
xd_arbiter.php
404 ms
xd_arbiter.php
445 ms
iframe_api
335 ms
revolution.extension.slideanims.min.js
619 ms
revolution.extension.layeranimation.min.js
600 ms
revolution.extension.navigation.min.js
605 ms
revolution.extension.actions.min.js
636 ms
admin-ajax.php
1166 ms
collect
24 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
16 ms
www-widgetapi.js
31 ms
page.php
149 ms
Ezryo55Cca5.css
45 ms
2NJaWBZ8ldv.css
48 ms
q68gy-v_YMF.js
46 ms
YvxwM8R7ol8.js
72 ms
ihptErjAmMX.js
68 ms
1BQnIVjTFoC.js
69 ms
CZfzbakm8cM.js
68 ms
cUsKAwzqrQw.js
96 ms
12239756_995196080546343_6066682151648329413_n.jpg
156 ms
12360246_1011309042268380_6947328160105566512_n.jpg
72 ms
wL6VQj7Ab77.png
68 ms
s7jcwEQH7Sx.png
71 ms
6GqoI2ZyIrf.png
72 ms
R9a_DtVRZgv.js
118 ms
cUDgRFxaoIk.js
119 ms
0JBr1QHp8Gi.js
118 ms
kDOzhTr2W91.js
119 ms
coloredbg.png
133 ms
loader.gif
131 ms
lindebergs.de 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
Links do not have a discernible name
lindebergs.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lindebergs.de 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 Lindebergs.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 Lindebergs.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.
lindebergs.de
Open Graph description is not detected on the main page of LINDEBERGS. 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: