4.1 sec in total
394 ms
3.4 sec
361 ms
Visit weesen.de now to see the best up-to-date Weesen content and also check out these interesting facts you probably never knew about weesen.de
This website is for sale! weesen.de is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, weesen.de has it all...
Visit weesen.deWe analyzed Weesen.de page load time and found that the first response time was 394 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
weesen.de performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value1.9 s
98/100
25%
Value3.5 s
88/100
10%
Value220 ms
87/100
30%
Value0.219
57/100
15%
Value4.1 s
87/100
10%
394 ms
738 ms
303 ms
1049 ms
314 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Weesen.de, 95% (19 requests) were made to Web62.server104.rhs-it.de. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Web62.server104.rhs-it.de.
Page size can be reduced by 277 B (45%)
619 B
342 B
In fact, the total size of Weesen.de main page is 619 B. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. HTML takes 619 B which makes up the majority of the site volume.
Potential reduce by 277 B
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 277 B or 45% of the original size.
Number of requests can be reduced by 3 (17%)
18
15
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weesen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
weesen.de
394 ms
web62.server104.rhs-it.de
738 ms
shadowbox.css
303 ms
mootools.js
1049 ms
caption.js
314 ms
audio-player.js
308 ms
yoo_effects.js.php
621 ms
general.css
331 ms
template.css
735 ms
hintergrund.gif
734 ms
seitelinks.png
1038 ms
bgmenu.gif
284 ms
headerbg.gif
844 ms
logo.gif
447 ms
headeroben.png
287 ms
slogan.jpg
901 ms
footer.png
705 ms
search_bg.png
698 ms
drum.gif
921 ms
footer2.gif
1127 ms
weesen.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.
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
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.
weesen.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
weesen.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weesen.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Weesen.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.
weesen.de
Open Graph description is not detected on the main page of Weesen. 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: