10.8 sec in total
3 sec
7.5 sec
273 ms
Click here to check amazing Waz Trauer content for Germany. Otherwise, check out these important facts you probably never knew about waz.trauer.de
Finden Sie hier Traueranzeigen, Todesanzeigen und Beileidsbekundungen aus Ihrer Tageszeitung oder passende Hilfe im Trauerfall. Jetzt online gedenken.
Visit waz.trauer.deWe analyzed Waz.trauer.de page load time and found that the first response time was 3 sec and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
waz.trauer.de performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value14.0 s
0/100
25%
Value9.7 s
10/100
10%
Value870 ms
33/100
30%
Value0.013
100/100
15%
Value14.1 s
9/100
10%
3029 ms
219 ms
220 ms
212 ms
213 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 75% of them (99 requests) were addressed to the original Waz.trauer.de, 16% (21 requests) were made to Waz.vrsmedia-trauerportal.de and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Waz.trauer.de.
Page size can be reduced by 1.3 MB (32%)
4.3 MB
2.9 MB
In fact, the total size of Waz.trauer.de main page is 4.3 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. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 91.0 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 91.0 kB or 78% of the original size.
Potential reduce by 35.6 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. Waz Trauer 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 75% of the original size.
Potential reduce by 203.4 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. Waz.trauer.de needs all CSS files to be minified and compressed as it can save up to 203.4 kB or 82% of the original size.
Number of requests can be reduced by 62 (48%)
129
67
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waz Trauer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
waz.trauer.de
3029 ms
jcarousel.css
219 ms
UL_FP1.css
220 ms
defaultTabControl.css
212 ms
StartPage.css
213 ms
SearchResult.css
228 ms
StyleSheet.css
302 ms
Mainmenu.css
403 ms
assistance.css
407 ms
payment.css
410 ms
Buttons.css
411 ms
Branchenbuch-2.0.css
426 ms
ContentPage.css
505 ms
Registry.css
601 ms
jcarousel-skin-ModulMiddle-w470pxh246px.css
608 ms
jquery-ui-1.8rc3.custom.css
610 ms
lightbox.css
613 ms
selectBox.css
626 ms
Gallery.css
709 ms
trauer-de.css
791 ms
69.css
813 ms
verticaltabsLibrary.css
829 ms
verticaltabs.css
826 ms
jquery.rating.css
831 ms
tipTip.css
1021 ms
branchenbuch.css
1024 ms
colorbox.css
1018 ms
jquery-1.7.1.js
1124 ms
jquery-ui-1.8rc3.custom.min.js
1114 ms
jquery.ui.datepicker-de.js
1030 ms
jquery-ui-1.8.1.custom.min.js
1445 ms
jquery.jcarousel.min.js
1251 ms
jquery.maphilight.min.js
1250 ms
selectBox.js
1249 ms
jquery.lightbox-0.5.js
1313 ms
jquery.watermark.min.js
1328 ms
js
44 ms
iam.js
488 ms
fktwe4.js
578 ms
cookieconsent.min.js
23 ms
WebResource.axd
1372 ms
autocolumn.js
1252 ms
jquery.tipTip.minified.js
1251 ms
browserWarning.css
1307 ms
jquery.rating.pack.js
1344 ms
jquery.boxy.js
1423 ms
ExtraFKT.js
1366 ms
chili-1.7.pack.js
1262 ms
jquery.easing.js
1258 ms
jquery.dimensions.js
1301 ms
accordion.js
1325 ms
executeAccordionPayment.js
1424 ms
executeAccordionPaymentType.js
1373 ms
jquery.colorbox.js
1276 ms
browserVersions.js
1268 ms
WebResource.axd
1303 ms
ScriptResource.axd
1422 ms
ScriptResource.axd
1439 ms
ScriptResource.axd
1466 ms
default.aspx
1478 ms
jquery.cookie.js
1267 ms
gpt.js
7 ms
pubads_impl_81.js
11 ms
container.html
22 ms
Trauerspruch180.jpg
498 ms
portrait.jpg
439 ms
browserWarning_close.png
201 ms
firefox.png
292 ms
chrome.png
307 ms
opera.png
345 ms
ie.png
438 ms
safari.png
522 ms
waz-trauer.png
493 ms
trauer.de.jpg
505 ms
d07809d4-8e32-43a9-bca6-876291e6b4fc.jpg
724 ms
a919a2a4-e378-44f3-bbf2-e235ce6d3e28.jpg
644 ms
da77e5d7-f887-4ea0-ad70-5b6d4ff96ab3.jpg
717 ms
7b2734db-bb75-4046-b253-5503f30c87bc.jpg
794 ms
fe16a9f6-f28a-474b-954b-92b26720e08d.jpg
805 ms
b6dc93fd-e6a7-41f4-a8e9-36741dce9ea6.jpg
918 ms
ce14a306-4061-4e65-af27-d4e422f7aac6.jpg
942 ms
d50bb2be-da9c-4cc6-8e53-daae01c01691.jpg
1320 ms
5d985184-80dd-4c4d-a181-7091b7b0150c.jpg
1024 ms
8382c016-dfd3-4c90-939b-cf7ee963c533.jpg
1096 ms
033ca30f-9f26-4daa-ba7a-77104e100632.jpg
1107 ms
73b30d79-fd97-4e22-847b-e172a858f344.jpg
1320 ms
abbd2bf2-79c7-4ab5-8bc3-af8a0a37e5fa.jpg
1262 ms
cb0173ab-48f9-49ba-9447-42a0b0839674.jpg
1429 ms
d5029b63-2f7d-4f82-9b29-f0fab96cbad0.jpg
1788 ms
51a51d10-37fd-4ee2-8f98-c2e9e9d55c22.jpg
1512 ms
630cf819-2ab9-40fd-973c-74f6dbcbcaa2.jpg
1576 ms
265eb6d1-5529-45c7-84ca-2e41e686ad9e.jpg
1619 ms
253c4438-d3f7-4301-936b-a400398bd07a.jpg
1723 ms
117a81be-2a4e-4665-83f5-2f7cb7d94437.jpg
1832 ms
Nr1-banner_trauer-de_300x90.jpg
1942 ms
Nr5-Trauer_de_Banner_300_90.jpg
2548 ms
17fb1418-dd78-11e1-84da-6de350e91111.jpg
609 ms
d8520e26-b9de-11e1-9ce5-7757a8609d8c.jpg
511 ms
fc8586c7-685a-11e1-81a2-6d1ecfb28696.jpg
612 ms
b4ba688a-3767-11e1-81a2-6d1ecfb28696.jpg
611 ms
5b4483bd-98ee-11e0-8e40-bfbab1fca189.jpg
613 ms
008d30c7-98f4-11e0-8e40-bfbab1fca189.jpg
826 ms
9489a888-d220-11df-b67a-1598697095f5.jpg
927 ms
4b75c1bf-b98d-11df-a4ff-efb7e323ed09.jpg
948 ms
91d178e8-8e56-11df-bca2-1de321d03415.jpg
1035 ms
3e78a207-6999-11df-9b91-114c7740494b.jpg
1057 ms
9934f4f0-5d9c-11df-be00-d349471cf1d9.jpg
1059 ms
4311c76e-3656-11df-a200-05134cfe89f0.jpg
1243 ms
8afe7636-1cb3-11df-a200-05134cfe89f0.jpg
1352 ms
68eb0e7a-006b-11df-a200-05134cfe89f0.jpg
1364 ms
cffa0b0e-006d-11df-a200-05134cfe89f0.jpg
1478 ms
523a0050-00f3-11df-a200-05134cfe89f0.jpg
1484 ms
16436dd4-faa1-11de-a200-05134cfe89f0.jpg
1486 ms
1106d9e7-f3c2-11de-a200-05134cfe89f0.jpg
1700 ms
th_ablauf_beerdigung_400px.png
2060 ms
mz_testament_verfassen_400px.png
1871 ms
bgd_content.png
1470 ms
new.png
1611 ms
bgd_Search.jpg
1734 ms
calenderClick.png
1678 ms
list_icon.png
1703 ms
more.png
1793 ms
TS-Stoerer.png
1792 ms
v_icon_prev.png
1840 ms
v_icon_next.png
1863 ms
icon_prev.png
1892 ms
ga.js
15 ms
__utm.gif
16 ms
__utm.gif
11 ms
icon_next.png
1908 ms
overlay.png
1856 ms
dark-top.css
6 ms
waz.trauer.de 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
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
waz.trauer.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
Browser errors were logged to the console
waz.trauer.de SEO score
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 doesn't use legible font sizes
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waz.trauer.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 Waz.trauer.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.
waz.trauer.de
Open Graph description is not detected on the main page of Waz Trauer. 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: