4 sec in total
470 ms
3.2 sec
251 ms
Visit wato.de now to see the best up-to-date Wato content for Germany and also check out these interesting facts you probably never knew about wato.de
Wato.de - Rollstuhl und Tourismus. Wato informiert zum Urlaub mit dem Rollstuhl aus Sicht der Rollstuhlfahrer aber auch aus Sicht der Touristiker. Wato ist ein Synonym für
Visit wato.deWe analyzed Wato.de page load time and found that the first response time was 470 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster. This domain responded with an error, which can significantly jeopardize Wato.de rating and web reputation
wato.de performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value8.7 s
1/100
25%
Value6.6 s
37/100
10%
Value440 ms
63/100
30%
Value0.455
20/100
15%
Value10.6 s
23/100
10%
470 ms
1193 ms
59 ms
184 ms
190 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 57% of them (41 requests) were addressed to the original Wato.de, 8% (6 requests) were made to Pagead2.googlesyndication.com and 8% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Wato.de.
Page size can be reduced by 465.8 kB (49%)
955.6 kB
489.8 kB
In fact, the total size of Wato.de main page is 955.6 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. 50% of websites need less resources to load. Javascripts take 488.5 kB which makes up the majority of the site volume.
Potential reduce by 25.5 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 25.5 kB or 73% of the original size.
Potential reduce by 35.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. Wato images are well optimized though.
Potential reduce by 338.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 338.1 kB or 69% of the original size.
Potential reduce by 66.8 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. Wato.de needs all CSS files to be minified and compressed as it can save up to 66.8 kB or 79% of the original size.
Number of requests can be reduced by 38 (55%)
69
31
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wato. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
wato.de
470 ms
www.wato.de
1193 ms
plusone.js
59 ms
style.css
184 ms
logo_de.css
190 ms
media.css
190 ms
style_custom.css
206 ms
media_custom.css
207 ms
style_vn.css
208 ms
media_vn.css
274 ms
style_dp.css
273 ms
media_dp.css
278 ms
tbf.css
295 ms
jquery-1.8.3.js
572 ms
site.js
300 ms
touch.js
363 ms
fuf.js
366 ms
voting.js
370 ms
mtb.js
383 ms
as.js
393 ms
tb.js
452 ms
class-extend.js
458 ms
jquery-ui.js
748 ms
jquery.datepick.js
660 ms
jquery.datepick-de.js
484 ms
jquery.trackbar.js
544 ms
jquery-ui.css
551 ms
adsbygoogle.js
17 ms
cb=gapi.loaded_0
6 ms
share42.js
513 ms
show_ads.js
3 ms
all.js
270 ms
co-de.js
303 ms
bg.png
130 ms
loading.gif
184 ms
top.png
380 ms
ca-pub-8794947707308555.js
90 ms
show_ads_impl.js
54 ms
header.JPG
419 ms
bg-tr-wh.png
144 ms
logo_de.png
115 ms
search.png
188 ms
down.png
187 ms
open.png
238 ms
wato-treppe-rollstuhl.jpg
358 ms
piktogramme.png
501 ms
rss_icon.png
268 ms
news.png
320 ms
177 ms
pixel.gif
308 ms
ads
292 ms
ga.js
51 ms
xd_arbiter.php
171 ms
xd_arbiter.php
411 ms
show_ads.js
32 ms
all.js
410 ms
plusone.js
58 ms
ads
221 ms
ads
227 ms
__utm.gif
12 ms
like.php
85 ms
TY3MhkXpWJ-.js
507 ms
LVx-xkvaJ0b.png
571 ms
15649663073446800436
52 ms
abg.js
53 ms
m_js_controller.js
74 ms
googlelogo_color_112x36dp.png
102 ms
7880414221577026928
56 ms
9132616576190501120
65 ms
s
40 ms
x_button_blue2.png
38 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
wato.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-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
wato.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
Browser errors were logged to the console
Page has valid source maps
wato.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wato.de 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 Wato.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.
wato.de
Open Graph data is detected on the main page of Wato. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: