5 sec in total
346 ms
4.1 sec
518 ms
Click here to check amazing Weedate content for Germany. Otherwise, check out these important facts you probably never knew about weedate.de
Online Dating Ghostwriter Markus Dobler verhilft dir zu mehr Erfolg bei der Online Partnersuche und mehr Matches & Dates.
Visit weedate.deWe analyzed Weedate.de page load time and found that the first response time was 346 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
weedate.de performance score
name
value
score
weighting
Value12.9 s
0/100
10%
Value15.2 s
0/100
25%
Value32.8 s
0/100
10%
Value16,930 ms
0/100
30%
Value0.048
99/100
15%
Value32.0 s
0/100
10%
346 ms
654 ms
166 ms
548 ms
269 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 72% of them (63 requests) were addressed to the original Weedate.de, 10% (9 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Weedate.de.
Page size can be reduced by 583.6 kB (59%)
988.9 kB
405.3 kB
In fact, the total size of Weedate.de main page is 988.9 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. 50% of websites need less resources to load. Javascripts take 357.6 kB which makes up the majority of the site volume.
Potential reduce by 70.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 70.3 kB or 88% of the original size.
Potential reduce by 23.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. Weedate images are well optimized though.
Potential reduce by 247.6 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 247.6 kB or 69% of the original size.
Potential reduce by 242.6 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. Weedate.de needs all CSS files to be minified and compressed as it can save up to 242.6 kB or 84% of the original size.
Number of requests can be reduced by 16 (21%)
75
59
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weedate. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
weedate.de
346 ms
www.weedate.de
654 ms
xr_fonts.css
166 ms
xr_main.css
548 ms
xr_text.css
269 ms
custom_styles.css
332 ms
roe.js
375 ms
replaceMobileFonts.js
279 ms
prs4.js
345 ms
ani.css
438 ms
css
26 ms
css
38 ms
css
47 ms
css
44 ms
css
45 ms
analytics.js
26 ms
7960.png
256 ms
8026.jpg
187 ms
8027.jpg
254 ms
8028.jpg
452 ms
8029.jpg
256 ms
8030.jpg
255 ms
8031.jpg
352 ms
8032.jpg
448 ms
8033.jpg
425 ms
8034.jpg
450 ms
8035.jpg
427 ms
8036.jpg
543 ms
8037.jpg
627 ms
8038.jpg
627 ms
8039.jpg
792 ms
8041.jpg
653 ms
8042.jpg
657 ms
8044.jpg
1048 ms
8045.jpg
810 ms
8046.jpg
876 ms
8047.jpg
927 ms
1546.png
841 ms
1562.png
992 ms
8050.jpg
983 ms
8051.jpg
1017 ms
8052.jpg
1069 ms
1551.png
1121 ms
1552.png
1174 ms
8056.jpg
1775 ms
7121.png
1496 ms
8457.png
1495 ms
8463.png
1496 ms
8458.png
1497 ms
8459.png
1356 ms
8460.png
1821 ms
7126.png
1680 ms
ulK9u722BGg
96 ms
wcgnAbnvSG8
162 ms
collect
59 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
11 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
25 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
25 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
56 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
57 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
57 ms
PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf
56 ms
collect
138 ms
XaraWDEmbeddedHTMLfont1.woff
1826 ms
www-embed-player-vflfNyN_r.css
31 ms
www-embed-player.js
69 ms
7127.png
1575 ms
7128.png
1575 ms
8005.png
1618 ms
7130.png
1692 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
42 ms
ad_status.js
41 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
26 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
30 ms
8007.png
1719 ms
8008.png
1647 ms
7133.png
1569 ms
7117.png
1623 ms
7118.png
1680 ms
8073.png
1781 ms
8074.png
1688 ms
8075.png
1625 ms
8076.png
1612 ms
8019.png
1597 ms
8462.png
1640 ms
8464.png
1630 ms
ulK9u722BGg
66 ms
wcgnAbnvSG8
80 ms
weedate.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.
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
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
weedate.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
weedate.de 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
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weedate.de can be misinterpreted by Google and other search engines. Our service has detected that German 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 Weedate.de main page’s claimed encoding is windows-1252. 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.
weedate.de
Open Graph description is not detected on the main page of Weedate. 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: