8 sec in total
1.4 sec
6.4 sec
203 ms
Click here to check amazing Steinburg content for Germany. Otherwise, check out these important facts you probably never knew about steinburg.com
Das Schlosshotel Steinburg liegt hoch über Würzburg, der wunderbaren Stadt am Main, wo sich barocke Pracht mit anmutiger Leichtigkeit vereinen.
Visit steinburg.comWe analyzed Steinburg.com page load time and found that the first response time was 1.4 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
steinburg.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value5.0 s
26/100
25%
Value7.4 s
28/100
10%
Value820 ms
35/100
30%
Value0.077
95/100
15%
Value7.5 s
47/100
10%
1355 ms
1465 ms
687 ms
219 ms
311 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 86% of them (78 requests) were addressed to the original Steinburg.com, 2% (2 requests) were made to Ajax.googleapis.com and 2% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Steinburg.com.
Page size can be reduced by 733.5 kB (39%)
1.9 MB
1.1 MB
In fact, the total size of Steinburg.com main page is 1.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. 55% of websites need less resources to load. Images take 885.9 kB which makes up the majority of the site volume.
Potential reduce by 92.3 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 92.3 kB or 82% of the original size.
Potential reduce by 17.5 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. Steinburg images are well optimized though.
Potential reduce by 445.4 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 445.4 kB or 70% of the original size.
Potential reduce by 178.3 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. Steinburg.com needs all CSS files to be minified and compressed as it can save up to 178.3 kB or 74% of the original size.
Number of requests can be reduced by 66 (75%)
88
22
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Steinburg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
steinburg.com
1355 ms
www.steinburg.com
1465 ms
language-selector.css
687 ms
960.css
219 ms
shortcodes_and_menu.css
311 ms
tabs.css
228 ms
style.css
506 ms
preloader.css
315 ms
prettyPhoto.css
416 ms
navigation.css
445 ms
cms-navigation-base.css
447 ms
cms-navigation.css
445 ms
cat-posts.css
513 ms
front-style.css
712 ms
buttons.min.css
551 ms
dashicons.min.css
652 ms
mediaelementplayer.min.css
680 ms
wp-mediaelement.css
802 ms
media-views.min.css
991 ms
imgareaselect.css
893 ms
styles.css
784 ms
jquery.min.js
45 ms
utils.min.js
783 ms
plupload.full.min.js
1098 ms
sitepress.js
1295 ms
swfobject.js
921 ms
jquery.jplayer.min.js
1115 ms
supersized.css
1016 ms
supersized.3.1.3.min.js
1275 ms
jquery.min.js
9 ms
jquery-latest.js
8 ms
showHide.js
1061 ms
jquery.easing.1.3.js
1261 ms
menuFunctions.js
1168 ms
storage.js
1209 ms
underscore.min.js
1135 ms
shortcode.min.js
1138 ms
backbone.min.js
1593 ms
wp-util.min.js
1163 ms
wp-backbone.min.js
1458 ms
media-models.min.js
1171 ms
jquery.tools.min.js
8 ms
wp-plupload.min.js
1241 ms
core.min.js
1219 ms
widget.min.js
1232 ms
mouse.min.js
1134 ms
sortable.min.js
1180 ms
mediaelement-and-player.min.js
1445 ms
wp-mediaelement.js
1207 ms
media-views.min.js
1339 ms
media-editor.min.js
1301 ms
media-audiovideo.min.js
1251 ms
wp-embed.min.js
1351 ms
comment-reply.min.js
1295 ms
jqueryslidemenu.js
1205 ms
jquery.hoverIntent.minified.js
1280 ms
jquery.preloader.js
1202 ms
jquery.prettyPhoto.js
1201 ms
jquery.cycle.all.min.js
1261 ms
jwplayer.js
2004 ms
script.js
1173 ms
wp-emoji-release.min.js
1176 ms
Menue-auf.png
809 ms
steinburg.png
920 ms
facebook_16.png
909 ms
twitter_16.png
925 ms
Menue_Bild.png
885 ms
black_bck2.png
994 ms
Angebote_Bild.png
972 ms
search_btn.png
980 ms
leer.gif
978 ms
bg_creme.png
976 ms
all.js
7 ms
main_btn.png
1039 ms
136 ms
Menue-weg.png
1032 ms
xd_arbiter.php
25 ms
xd_arbiter.php
33 ms
analytics.js
184 ms
Steinburg_DasTeam61.jpg
865 ms
Steinburg_Steinburg_61.jpg
742 ms
Steinburg_Steinburg5.jpg
672 ms
progress.gif
191 ms
Bild-anzeigen.png
154 ms
Bild-anzeigen.cur
189 ms
navigation_controls.png
276 ms
collect
13 ms
like.php
88 ms
qeKvIRsJabD.js
30 ms
LVx-xkvaJ0b.png
15 ms
print.css
121 ms
steinburg.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
steinburg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
steinburg.com 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Steinburg.com 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 Steinburg.com 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.
steinburg.com
Open Graph description is not detected on the main page of Steinburg. 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: