10.5 sec in total
2.1 sec
8 sec
367 ms
Welcome to wehrburg.de homepage info - get ready to check Wehrburg best content right away, or after learning these important things about wehrburg.de
Welcome to the Hotel Wehrburg, one of the best addresses for vacationers in Cuxhaven. Book here.
Visit wehrburg.deWe analyzed Wehrburg.de page load time and found that the first response time was 2.1 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wehrburg.de performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value11.4 s
0/100
25%
Value11.1 s
6/100
10%
Value5,620 ms
0/100
30%
Value0.068
96/100
15%
Value15.1 s
7/100
10%
2107 ms
194 ms
310 ms
203 ms
206 ms
Our browser made a total of 193 requests to load all elements on the main page. We found that 80% of them (154 requests) were addressed to the original Wehrburg.de, 7% (13 requests) were made to Maps.google.com and 5% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Wehrburg.de.
Page size can be reduced by 1.9 MB (41%)
4.5 MB
2.7 MB
In fact, the total size of Wehrburg.de main page is 4.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. 75% 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 102.2 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 102.2 kB or 83% of the original size.
Potential reduce by 90.9 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. Wehrburg images are well optimized though.
Potential reduce by 1.2 MB
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 1.2 MB or 75% of the original size.
Potential reduce by 447.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. Wehrburg.de needs all CSS files to be minified and compressed as it can save up to 447.7 kB or 83% of the original size.
Number of requests can be reduced by 126 (72%)
174
48
The browser has sent 174 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wehrburg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 60 to 1 for CSS and as a result speed up the page load time.
wehrburg.de
2107 ms
system.css
194 ms
templates.raulff.less.bootstrap.less.css
310 ms
plugins.system.t3.base.less.global-modules.less.css
203 ms
plugins.system.t3.base.less.global-typo.less.css
206 ms
plugins.system.t3.base.less.grid-ext.less.css
205 ms
plugins.system.t3.base.less.t3.less.css
210 ms
templates.raulff.less.layout.less.css
289 ms
templates.raulff.less.core.less.css
301 ms
templates.raulff.less.typo-core.less.css
305 ms
templates.raulff.less.form.less.css
318 ms
templates.raulff.less.navigation-core.less.css
319 ms
templates.raulff.less.navigation.less.css
387 ms
templates.raulff.less.modules.less.css
399 ms
templates.raulff.less.joomla.less.css
405 ms
templates.raulff.less.typo.less.css
402 ms
templates.raulff.less.style.less.css
407 ms
templates.raulff.less.bt-style.less.css
417 ms
templates.raulff.less.bootstrap-responsive.less.css
484 ms
plugins.system.t3.base.less.grid-ext-responsive.less.css
500 ms
plugins.system.t3.base.less.global-typo-responsive.less.css
498 ms
plugins.system.t3.base.less.global-modules-responsive.less.css
504 ms
plugins.system.t3.base.less.t3-responsive.less.css
505 ms
templates.raulff.less.typo-core-responsive.less.css
518 ms
templates.raulff.less.navigation-responsive.less.css
580 ms
templates.raulff.less.joomla-responsive.less.css
595 ms
templates.raulff.less.typo-responsive.less.css
598 ms
templates.raulff.less.style-responsive.less.css
603 ms
templates.raulff.less.megamenu.less.css
606 ms
templates.raulff.less.megamenu-responsive.less.css
620 ms
templates.raulff.less.off-canvas.less.css
676 ms
custom.css
691 ms
sdwa_styles_table.css
695 ms
yui-reset.css
702 ms
pikaday.css
707 ms
booking.css
722 ms
js
23 ms
fonts
103 ms
css
30 ms
jcarousel.css
697 ms
fonts
132 ms
btcontentshowcase.css
611 ms
style.css
608 ms
font-awesome.min.css
612 ms
jquery.mCustomScrollbar.css
618 ms
jquery.fancybox-1.3.4.css
632 ms
default.css
597 ms
raulff.css
598 ms
dpcalendar.css
592 ms
fullcalendar.css
602 ms
dpcalendar.css
603 ms
style.css
625 ms
accordion.css
597 ms
style.css
596 ms
default.css
606 ms
style.css
613 ms
editor.css
615 ms
style_bt.css
736 ms
style_bt_update_v3.0.1.css
593 ms
widget.css
592 ms
datepicker.css
606 ms
system.css
616 ms
jquery.min.js
727 ms
jquery-noconflict.js
659 ms
jquery-migrate.min.js
609 ms
caption.js
610 ms
bootstrap.js
631 ms
jquery.tap.min.js
659 ms
off-canvas.js
666 ms
script.js
668 ms
menu.js
629 ms
responsive.js
645 ms
sdwa_functions_table.js
640 ms
jquery.xdomainajax.js
665 ms
jquery.xml2json.js
666 ms
underscore.js
667 ms
backbone.js
737 ms
moment.js
758 ms
pikaday.js
649 ms
booking.js
674 ms
jcarousel.js
670 ms
bt_jcarousel.js
660 ms
hammer.js
683 ms
css
17 ms
default.js
699 ms
mootools-core.js
793 ms
core.js
686 ms
mootools-more.js
918 ms
engine.mootools.js
723 ms
modernizr.custom.97074.js
687 ms
jquery.mousewheel.min.js
721 ms
jquery.mCustomScrollbar.concat.min.js
710 ms
jquery.fancybox-1.3.4.pack.js
752 ms
default.js
750 ms
dpNoConflict.js
720 ms
dpcalendar.js
719 ms
fullcalendar.min.js
802 ms
btbase64.min.js
749 ms
default.js
719 ms
default.js
722 ms
hammer0.6.4.js
742 ms
default.js
734 ms
ajax_1.5.pack.js
758 ms
3c791ff6edbecbd28d11903f9d272b1b.jpg
421 ms
c7a8ec75b5ee2608c1135700c31ac3cd.jpg
422 ms
raulff_wehrburg.png
279 ms
buchen_flag.png
280 ms
ja-bt-tab-bg1.png
280 ms
ja-bt-tab-bg3.png
278 ms
ja-bt-tab-bg4.png
281 ms
ja-bt-tab-bg5.png
281 ms
ja-bt-tab-bg2.png
282 ms
btTab-tab-bg-r.png
283 ms
btTab-tab-bg.png
369 ms
4406cdeb33c3693c9b8eab7de42f36f8-1.jpg
419 ms
79cca8126cc768e27e6ced8f4d1e4a3d-1.jpg
370 ms
88f69592bf068406dc6ad6610ef792b3-1.jpg
371 ms
e5cf8fd55b338f7abaa1fac42e98ef81-1.jpg
417 ms
700a21f1ca512f667d2d1528f1ffdb60-RaulfHotel_Web_Bilder_Silvester.jpg
419 ms
fd8a0ddc34945f71b8ff0ec7892927be-RaulfHotel_Web_Bilder_WenndieBlaetterfallen.jpg
433 ms
cloudy.png
498 ms
ee5808f7841f0960f809e2095b211c78-RaulfHotel_Web_Bilder_Silvester.jpg
622 ms
68b3eb4021c9ab3891ae3fe9bb3c1c06-RaulfHotel_Web_Bilder_WenndieBlaetterfallen.jpg
510 ms
essen.jpg
925 ms
wellness.jpg
1242 ms
1.jpeg
950 ms
2.jpeg
1217 ms
3.jpeg
845 ms
4.jpeg
1009 ms
5.jpg
1842 ms
6.jpeg
1873 ms
7.jpeg
1170 ms
8.jpeg
1308 ms
9.jpeg
1285 ms
92.jpg
1860 ms
91.jpeg
2873 ms
93.jpg
1394 ms
ajax-loader.gif
1406 ms
arrow_r_h.png
1465 ms
AWM5wXtMJeRP-AcRTgT4qQ.ttf
16 ms
l1cOQ90roY9yC7voEhngDKCWcynf_cDxXwCLxiixG1c.ttf
15 ms
yql
153 ms
common.js
13 ms
util.js
14 ms
geocoder.js
14 ms
OpenSans-Regular.ttf
1434 ms
Bentham-Regular.ttf
1348 ms
OpenSans-Light.ttf
1572 ms
OpenSans-Semibold.ttf
2223 ms
events
1922 ms
lastminute.png
1787 ms
bg_beige.png
1669 ms
Cardo-Regular.ttf
3613 ms
guC5lwT5Dw7anV_xfpCGqw.ttf
82 ms
0b3R8ORT0i9mlMGM3BxXF_esZW2xOQ-xsNqO47m55DA.ttf
82 ms
URSgP3aplSko3CQAzdXHwPesZW2xOQ-xsNqO47m55DA.ttf
82 ms
AuthenticationService.Authenticate
135 ms
GeocodeService.Search
207 ms
fontawesome-webfont.woff
1683 ms
fontawesome-webfont.woff
1784 ms
buchungsanfrage.png
1761 ms
category_img_bg.png
1836 ms
arrow_circle.png
1849 ms
bg-a-back--to-top.png
1886 ms
mCSB_buttons.png
1933 ms
back.png
1940 ms
next.png
1970 ms
loading.gif
1947 ms
pagination_blue.png
1963 ms
map.js
4 ms
StaticMapService.GetMapImage
62 ms
marker.js
34 ms
onion.js
17 ms
openhand_8_8.cur
34 ms
ViewportInfoService.GetViewportInfo
126 ms
stats.js
23 ms
controls.js
21 ms
transparent.png
48 ms
css
81 ms
infowindow.js
63 ms
google4.png
64 ms
pin.png
1731 ms
mapcnt6.png
57 ms
sv5.png
58 ms
tmapctrl.png
23 ms
tmapctrl4.png
24 ms
vt
20 ms
vt
46 ms
vt
44 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
9 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
38 ms
wehrburg.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
button, link, and menuitem elements do not have accessible names.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
wehrburg.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
wehrburg.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
![]()
EN
![]()
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wehrburg.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Wehrburg.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.
wehrburg.de
Open Graph description is not detected on the main page of Wehrburg. 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: