3.4 sec in total
737 ms
2.5 sec
225 ms
Visit physioneo.de now to see the best up-to-date Physio Neo content for Germany and also check out these interesting facts you probably never knew about physioneo.de
PhysioNeo, die Physiotherapie und Wellness Praxis von Athanasia Styfoudi in Esslingen bietet Physiotherapie, Wellness und Baby-Massage Kurse.
Visit physioneo.deWe analyzed Physioneo.de page load time and found that the first response time was 737 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
physioneo.de performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value12.1 s
0/100
25%
Value13.0 s
2/100
10%
Value380 ms
70/100
30%
Value0.139
79/100
15%
Value16.4 s
5/100
10%
737 ms
319 ms
402 ms
312 ms
196 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 68% of them (43 requests) were addressed to the original Physioneo.de, 14% (9 requests) were made to Static.worldsoft-cms.info and 10% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (806 ms) belongs to the original domain Physioneo.de.
Page size can be reduced by 103.2 kB (12%)
835.1 kB
732.0 kB
In fact, the total size of Physioneo.de main page is 835.1 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. 45% of websites need less resources to load. Images take 726.9 kB which makes up the majority of the site volume.
Potential reduce by 96.0 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 96.0 kB or 89% of the original size.
Potential reduce by 7.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. Physio Neo images are well optimized though.
Number of requests can be reduced by 38 (68%)
56
18
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Physio Neo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
physioneo.de
737 ms
jquery-1.7.2.min.js
319 ms
jquery-ui-1.8.12.custom.css
402 ms
jquery-ui-1.8.2.custom.css
312 ms
bootstrap-menu.css
196 ms
bootstrap.min.css
296 ms
bootstrap.ws.overrides.css
196 ms
gutters.css
212 ms
connector.css
213 ms
css
26 ms
template-startseite.css
305 ms
cookie.js
360 ms
lazyload-min.js
360 ms
xoops.js
293 ms
bootstrap.js
357 ms
overlib.js
538 ms
youtubewmode.js
357 ms
jquery-ui-1.8.12.custom.min.js
660 ms
bootstrap.min.js
393 ms
responsive.menubuilder.js
391 ms
waypoints.min.js
404 ms
waypoints-sticky-custom.min.js
419 ms
script.js
420 ms
build.css
420 ms
style.css
488 ms
default.css
489 ms
no-thing.css
498 ms
responsive.css
522 ms
font-awesome.min.css
526 ms
settings.css
526 ms
static-captions.css
587 ms
dynamic-captions.css
589 ms
css
30 ms
jquery.themepunch.revolution.js
806 ms
jquery.themepunch.tools.min.js
734 ms
css
14 ms
Web_stopp.png
315 ms
blank.gif
221 ms
physioneo-logo-balken.jpg
222 ms
image.php
499 ms
image.php
625 ms
image.php
380 ms
image.php
625 ms
image.php
715 ms
pn-w.jpg
624 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
6 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
10 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
8 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
23 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
8 ms
image.php
421 ms
image.php
448 ms
loader.gif
430 ms
shadow3.png
430 ms
large_left.png
452 ms
large_right.png
505 ms
AjAmkoP1y0Vaad0UPPR466Yg0IPT4GEZJSIWMW-0ug4.ttf
19 ms
locale.js.php
122 ms
user.js.php
116 ms
ajaxLogin.js
105 ms
ajaxInvite.js
110 ms
ajaxPortalRecommend.js
98 ms
log
320 ms
physioneo.de 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
<frame> or <iframe> elements do not have a title
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.
physioneo.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
Browser errors were logged to the console
physioneo.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 Physioneo.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 Physioneo.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.
physioneo.de
Open Graph description is not detected on the main page of Physio Neo. 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: