7.1 sec in total
1.1 sec
5.8 sec
238 ms
Welcome to doder.org homepage info - get ready to check Doder best content right away, or after learning these important things about doder.org
Das Diskussionsforum für Rollenspieler aus München
Visit doder.orgWe analyzed Doder.org page load time and found that the first response time was 1.1 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
doder.org performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value2.2 s
95/100
25%
Value2.9 s
95/100
10%
Value90 ms
99/100
30%
Value0.138
79/100
15%
Value2.1 s
99/100
10%
1122 ms
6 ms
1338 ms
849 ms
2026 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 27% of them (21 requests) were addressed to the original Doder.org, 35% (27 requests) were made to Maps.googleapis.com and 15% (12 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Doder.org.
Page size can be reduced by 1.1 MB (59%)
1.8 MB
724.1 kB
In fact, the total size of Doder.org main page is 1.8 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. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 27.9 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 27.9 kB or 78% of the original size.
Potential reduce by 24.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. Doder images are well optimized though.
Potential reduce by 1.0 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.0 MB or 70% of the original size.
Number of requests can be reduced by 40 (56%)
71
31
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doder. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
portal.php
1122 ms
combo
6 ms
vbulletin-core.js
1338 ms
css.php
849 ms
vbulletin_lightbox.js
2026 ms
css.php
1656 ms
css.php
2159 ms
vbulletin_md5.js
894 ms
vbulletin_md5.js
1456 ms
background.gif
570 ms
logo.png
864 ms
search.png
864 ms
navbit-home.png
862 ms
collapse_40b.png
222 ms
Doder-Banner-02.png
1228 ms
lastpost-right.png
222 ms
doderlogo_kopf_klein.png
1159 ms
cron.php
863 ms
header_bg.png
862 ms
navred.png
846 ms
navbl.png
848 ms
generic_button.png
218 ms
maps
38 ms
maps
49 ms
embed
469 ms
embed
438 ms
js
80 ms
init_embed.js
38 ms
js
95 ms
init_embed.js
25 ms
common.js
91 ms
map.js
89 ms
google4.png
116 ms
overlay.js
114 ms
util.js
161 ms
onion.js
112 ms
search_impl.js
160 ms
StaticMapService.GetMapImage
359 ms
common.js
203 ms
map.js
201 ms
overlay.js
167 ms
util.js
161 ms
onion.js
160 ms
search_impl.js
240 ms
stats.js
213 ms
openhand_8_8.cur
104 ms
StaticMapService.GetMapImage
306 ms
ViewportInfoService.GetViewportInfo
229 ms
ViewportInfoService.GetViewportInfo
153 ms
kh
221 ms
transparent.png
63 ms
controls.js
92 ms
stats.js
124 ms
ViewportInfoService.GetViewportInfo
106 ms
ViewportInfoService.GetViewportInfo
64 ms
css
149 ms
entity11.png
67 ms
kh
54 ms
controls.js
42 ms
ViewportInfoService.GetViewportInfo
43 ms
mapcnt6.png
77 ms
ViewportInfoService.GetViewportInfo
68 ms
vt
132 ms
vt
137 ms
vt
104 ms
vt
96 ms
vt
103 ms
tmapctrl.png
42 ms
vt
148 ms
vt
171 ms
vt
167 ms
vt
155 ms
vt
163 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
16 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
28 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
37 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
37 ms
AuthenticationService.Authenticate
15 ms
doder.org 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Links do not have a discernible name
doder.org 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
doder.org 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
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doder.org 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 Doder.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
doder.org
Open Graph description is not detected on the main page of Doder. 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: