8 sec in total
1.5 sec
6.3 sec
190 ms
Click here to check amazing Dory content. Otherwise, check out these important facts you probably never knew about dory.de
lll➤ Rechtsanwalt Göppingen: ✔️ Schnelle, zuverlässige Hilfe ✔️ Langjährige Erfahrung ✔️ Top Preis-Leistung - Kompetent ▶️ Jetzt Termin vereinbaren.
Visit dory.deWe analyzed Dory.de page load time and found that the first response time was 1.5 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
dory.de performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value4.6 s
34/100
25%
Value6.1 s
45/100
10%
Value1,660 ms
11/100
30%
Value0.002
100/100
15%
Value7.8 s
45/100
10%
1542 ms
25 ms
649 ms
643 ms
643 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 26% of them (15 requests) were addressed to the original Dory.de, 62% (36 requests) were made to Test.dory.de and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Test.dory.de.
Page size can be reduced by 563.1 kB (60%)
931.3 kB
368.2 kB
In fact, the total size of Dory.de main page is 931.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 386.2 kB which makes up the majority of the site volume.
Potential reduce by 22.6 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 22.6 kB or 76% of the original size.
Potential reduce by 5.0 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. Dory images are well optimized though.
Potential reduce by 285.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 285.4 kB or 74% of the original size.
Potential reduce by 250.2 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. Dory.de needs all CSS files to be minified and compressed as it can save up to 250.2 kB or 87% of the original size.
Number of requests can be reduced by 41 (77%)
53
12
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
dory.de
1542 ms
css
25 ms
style.css
649 ms
prettyPhoto.css
643 ms
jquery-ui-1.8.16.custom.css
643 ms
screen.css
1289 ms
custom.css
2291 ms
ui.selectmenu.css
2295 ms
shCore.css
752 ms
shThemeDefault.css
743 ms
jquery.js
869 ms
jquery-migrate.min.js
844 ms
modernizr-2.5.3.min.js
854 ms
respond.min.js
943 ms
jquery.easing.1.3.js
953 ms
general.js
967 ms
jquery.infieldlabel.min.js
1049 ms
min-css-6aeb561ceaaa55d157076258f402ed0b.css
1059 ms
jquery.qtip.min.css
11 ms
zozo.tabs.css
109 ms
jquery.qtip.min.js
18 ms
jquery.rwdImageMaps.min.js
1071 ms
jquery.ba-hashchange.js
205 ms
zozo.tabs.js
306 ms
comment-reply.min.js
1153 ms
jquery.prettyPhoto.js
1176 ms
widget.min.js
1179 ms
ui.selectmenu.js
1261 ms
styled.selectmenu.js
1278 ms
wp-embed.min.js
1288 ms
min-js-fed2c168adfe018f07717470b1a5a498.js
1362 ms
style.css
848 ms
wp-emoji-release.min.js
112 ms
zozo.tabs.core.css
120 ms
zozo.tabs.ajax.css
104 ms
zozo.tabs.vertical.css
104 ms
zozo.tabs.horizontal.css
1983 ms
zozo.tabs.themes.css
1980 ms
zozo.tabs.underlined.css
996 ms
zozo.tabs.multiline.css
205 ms
zozo.tabs.clean.css
209 ms
zozo.tabs.grid.css
227 ms
zozo.tabs.responsive.css
307 ms
zozo.tabs.mobile.css
317 ms
middle_bg.png
112 ms
Logo1.png
112 ms
team_v4_index41.jpg
392 ms
team_dory1.jpg
390 ms
footer_bg.png
108 ms
icon_location.png
109 ms
widget_icon_03.png
215 ms
widget_icon_01.png
216 ms
Logo-small.png
220 ms
icon_totop.png
118 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
6 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
8 ms
GRTkKQvSwrQKMUJtWZsm7w.ttf
16 ms
vjI-nu0OQ4awNWMtISxB9w.ttf
15 ms
dory.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dory.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
dory.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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dory.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Dory.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.
dory.de
Open Graph description is not detected on the main page of Dory. 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: