6.1 sec in total
333 ms
4.3 sec
1.4 sec
Visit en.schwangau.de now to see the best up-to-date En Schwangau content for Germany and also check out these interesting facts you probably never knew about en.schwangau.de
Visit en.schwangau.deWe analyzed En.schwangau.de page load time and found that the first response time was 333 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
en.schwangau.de performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value4.7 s
32/100
25%
Value12.3 s
3/100
10%
Value200 ms
89/100
30%
Value0
100/100
15%
Value11.0 s
21/100
10%
333 ms
221 ms
26 ms
643 ms
321 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 96% of them (71 requests) were addressed to the original En.schwangau.de, 3% (2 requests) were made to Schwangau.de and 1% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain En.schwangau.de.
Page size can be reduced by 263.5 kB (5%)
4.9 MB
4.6 MB
In fact, the total size of En.schwangau.de main page is 4.9 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. 60% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 73.4 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. This page needs HTML code to be minified as it can gain 21.0 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 73.4 kB or 83% of the original size.
Potential reduce by 102.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. En Schwangau images are well optimized though.
Potential reduce by 87.9 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 87.9 kB or 78% of the original size.
Number of requests can be reduced by 24 (34%)
71
47
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of En Schwangau. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
en.schwangau.de
333 ms
welcome
221 ms
uc.js
26 ms
jquery.js
643 ms
22deac8ab5.css
321 ms
youtubevideo.css
323 ms
reset.css
322 ms
fonts.css
323 ms
jquery-ui.css
428 ms
colorbox.css
428 ms
all.min.css
681 ms
captionjs.css
430 ms
swiper-bundle.min.css
430 ms
navigation.css
535 ms
custom.css
684 ms
englisch.css
536 ms
jquery-3.6.0.min.js
751 ms
jquery.datetimepicker.min.js
646 ms
parsley.min.js
688 ms
Tabs.min.js
644 ms
Form.min.js
646 ms
megamenu.js
647 ms
megamenu_plugins.js
752 ms
fadeSlideShow.js
754 ms
jquery.caption.min.js
755 ms
jquery-ui.min.js
866 ms
swiper-bundle.min.js
883 ms
jquery.colorbox.js
756 ms
scripts.js
859 ms
bg_nav_blaugold_xl.jpg
200 ms
logo_schwangau_ferien_bayern_allgaeu.png
200 ms
down.png
204 ms
bg_submenu.jpg
307 ms
csm_menu_schwangau_allgaeu_hotels_a07c6a9d0d.jpg
306 ms
csm_menu_schwangau_allgaeu_camping_692a4699b8.jpg
309 ms
csm_menu_schwangau_neuschwanstein_koenigscard_12ca6c706b.jpg
311 ms
csm_menu_schwangau_schloss_neuschwanstein_cbc702905e.jpg
316 ms
csm_menu_schwangau_schloss_hohenschwangau_bb80ecbcfd.jpg
314 ms
csm_menu_schwangau_koenig_ludwig_ii_3beb8b8f7c.jpg
413 ms
csm_menu_schwangau_museum_der_bayerischen_koenige_82627cf5f8.jpg
413 ms
csm_menu_schwangau_allgaeu_koenigliche_kristalltherme_f248b70125.jpg
414 ms
csm_menu_schwangau_allgaeu_tegelbergbahn_f339cec021.jpg
418 ms
forggensee_boattrips.jpg
422 ms
csm_menu_schwangau_allgaeu_landschaft_und_natur_4f28b7579a.jpg
422 ms
menu_schwangau_allgaeu_biking.jpg
522 ms
csm_menu_schwangau_allgaeu_ski_langlauf_7e0911272f.jpg
521 ms
csm_SG_Hamam_1_01_adb34f3e33_e7292b1b79.jpg
523 ms
contactus.jpg
525 ms
menu_schwangau_prospekte.jpg
527 ms
menu_ortsplan_karten.jpg
529 ms
csm_Schloss_Neuschwanstein_im_Fruehherbst_2_2357c1407a.jpg
841 ms
csm_Nostalgiebus_Landschaft_7799_5465ebe05a.jpg
1580 ms
csm_Tegelbergbahn_verkleinert_f2783bbca5.jpg
2012 ms
csm_Fotolia_52189467_M_8c0fad3900.jpg
632 ms
csm_Forggenseeschifffahrt_MS_Fuessen_47cf533a58.jpg
740 ms
csm_Panorama_-_Koenigliche_Kristalltherme_Schwangau_-_Foto_Werbeagentur_Schmitz_-_Stein_3599ee2e98.jpg
742 ms
csm_Reiter_des_Colomanvereines_beim_Colomansfest_4b1c0892fe.jpg
931 ms
csm_WIT-_c_Ebener-9480_668fa3e67c.jpg
928 ms
mittwald_oeko.png
759 ms
logo-allgaeu.png
856 ms
csm_Schloss_Hohenschwangau_im_Winter_6cc0ec266c.jpg
2562 ms
csm_Marienbruecke_ueber_der_Poellat__im_Hintergrund_Schloss_Neuschwanstein_055b1c74b3.jpg
2342 ms
youtube_d6977ba82a92171e51aee18df7b6ff67.jpg
1185 ms
youtube_32c2ed93da8e48ce341ed9b621c87b27.jpg
979 ms
youtube_5d1f7231b68204301abf9747f35abe0d.jpg
1297 ms
facebook.png
1288 ms
map.png
1366 ms
instagram.png
1372 ms
Germany.png
545 ms
USA.png
531 ms
ic_cal.png
1384 ms
menu_home.png
1398 ms
search.png
1405 ms
overlay.png
1486 ms
en.schwangau.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
en.schwangau.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
en.schwangau.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise En.schwangau.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that En.schwangau.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.
en.schwangau.de
Open Graph description is not detected on the main page of En Schwangau. 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: