5.2 sec in total
410 ms
4.3 sec
446 ms
Welcome to edoras.de homepage info - get ready to check Edoras best content right away, or after learning these important things about edoras.de
Unsere Offices
Visit edoras.deWe analyzed Edoras.de page load time and found that the first response time was 410 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
edoras.de performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value3.5 s
64/100
25%
Value3.3 s
91/100
10%
Value40 ms
100/100
30%
Value0.001
100/100
15%
Value3.3 s
93/100
10%
410 ms
448 ms
615 ms
111 ms
221 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Edoras.de, 38% (50 requests) were made to Udg.de and 35% (46 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (977 ms) relates to the external source Udg.de.
Page size can be reduced by 1.2 MB (56%)
2.2 MB
972.0 kB
In fact, the total size of Edoras.de main page is 2.2 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 94.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 94.3 kB or 86% of the original size.
Potential reduce by 14.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. Edoras images are well optimized though.
Potential reduce by 816.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 816.9 kB or 69% of the original size.
Potential reduce by 290.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. Edoras.de needs all CSS files to be minified and compressed as it can save up to 290.3 kB or 86% of the original size.
Number of requests can be reduced by 78 (67%)
116
38
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edoras. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
edoras.de
410 ms
448 ms
615 ms
language-selector.css
111 ms
styles.css
221 ms
rgs.css
301 ms
font-awesome.min.css
312 ms
steadysets.css
319 ms
linecon.css
320 ms
style.css
432 ms
responsive.css
330 ms
style.css
403 ms
style.css
425 ms
jquery.js
527 ms
jquery-migrate.min.js
426 ms
jquery.gmap.min.js
457 ms
modernizr.js
505 ms
js
53 ms
jquery.form.min.js
596 ms
scripts.js
597 ms
superfish.js
597 ms
imagesLoaded.min.js
597 ms
easing.js
611 ms
respond.js
630 ms
swipe.min.js
634 ms
nicescroll.js
750 ms
sticky.js
645 ms
prettyPhoto.js
646 ms
flexslider.min.js
716 ms
isotope.min.js
747 ms
carouFredSel.min.js
843 ms
appear.js
762 ms
orbit.js
762 ms
init.js
930 ms
js
44 ms
map.js
866 ms
comment-reply.min.js
865 ms
nectar-love.js
871 ms
main.js
871 ms
wp-embed.min.js
947 ms
sitepress.js
977 ms
wp-emoji-release.min.js
859 ms
udg-logo1.png
568 ms
udg-logo_2x1.png
568 ms
nimbussantot-bol-webfont.woff
545 ms
OpenSans-Regular-webfont.woff
780 ms
OpenSans-Regular-webfont.woff
744 ms
OpenSans-Bold-webfont.woff
766 ms
OpenSansBold-webfont.woff
655 ms
fontawesome-webfont.woff
846 ms
gtm.js
66 ms
conversion_async.js
74 ms
trg.gif
559 ms
gtmext.min.js
77 ms
collect.js
95 ms
webtrekk_v4.min.js
80 ms
analytics.js
78 ms
40 ms
linkid.js
8 ms
collect
14 ms
collect
59 ms
track_page_view
38 ms
collect
22 ms
45 ms
ga-audiences
16 ms
common.js
76 ms
map.js
88 ms
util.js
89 ms
geocoder.js
88 ms
marker.js
87 ms
onion.js
38 ms
openhand_8_8.cur
105 ms
AuthenticationService.Authenticate
108 ms
GeocodeService.Search
216 ms
ViewportInfoService.GetViewportInfo
211 ms
stats.js
31 ms
controls.js
26 ms
css
103 ms
transparent.png
30 ms
google4.png
38 ms
mapcnt6.png
46 ms
sv5.png
45 ms
tmapctrl.png
43 ms
tmapctrl4.png
41 ms
33704_5.js
76 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
67 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
72 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
95 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
95 ms
vt
59 ms
vt
50 ms
vt
49 ms
vt
29 ms
vt
48 ms
vt
50 ms
vt
55 ms
vt
50 ms
vt
61 ms
vt
51 ms
vt
50 ms
vt
51 ms
vt
52 ms
vt
52 ms
vt
54 ms
vt
53 ms
vt
61 ms
vt
55 ms
vt
55 ms
vt
60 ms
vt
62 ms
vt
63 ms
vt
62 ms
vt
70 ms
vt
66 ms
StaticMapService.GetMapImage
187 ms
ViewportInfoService.GetViewportInfo
96 ms
map_marker.png
205 ms
infowindow.js
10 ms
map_marker.png
111 ms
vt
14 ms
vt
36 ms
vt
44 ms
vt
15 ms
vt
16 ms
vt
41 ms
vt
22 ms
vt
46 ms
vt
28 ms
vt
38 ms
map_marker.png
111 ms
webtrekk_geid.min.js
560 ms
wt
464 ms
edoras.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
edoras.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
Page has valid source maps
edoras.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Edoras.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 Edoras.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.
edoras.de
Open Graph data is detected on the main page of Edoras. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: