17.1 sec in total
674 ms
16.1 sec
263 ms
Click here to check amazing Muscus content. Otherwise, check out these important facts you probably never knew about muscus.de
In diesem Gartenblog wird über interessante Themen der Natur gebloggt, ob Pflanze, Käfer oder Neuigkeit
Visit muscus.deWe analyzed Muscus.de page load time and found that the first response time was 674 ms and then it took 16.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
muscus.de performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value3.3 s
69/100
25%
Value3.1 s
93/100
10%
Value140 ms
96/100
30%
Value0.219
57/100
15%
Value3.3 s
93/100
10%
674 ms
178 ms
441 ms
179 ms
281 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 54% of them (29 requests) were addressed to the original Muscus.de, 11% (6 requests) were made to Googleads.g.doubleclick.net and 9% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (15.1 sec) relates to the external source Topblogs.de.
Page size can be reduced by 153.3 kB (34%)
452.3 kB
299.1 kB
In fact, the total size of Muscus.de main page is 452.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. 35% of websites need less resources to load. Images take 223.6 kB which makes up the majority of the site volume.
Potential reduce by 23.2 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 23.2 kB or 77% of the original size.
Potential reduce by 9.7 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. Muscus images are well optimized though.
Potential reduce by 111.1 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 111.1 kB or 59% of the original size.
Potential reduce by 9.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. Muscus.de needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 80% of the original size.
Number of requests can be reduced by 13 (25%)
52
39
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Muscus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
muscus.de
674 ms
style.css
178 ms
jquery.js
441 ms
jquery-migrate.min.js
179 ms
jquery.lightbox.min.js
281 ms
jquery.lightbox.plugin.min.js
227 ms
wp-page-numbers.css
301 ms
brand
40 ms
brand
37 ms
show_ads.js
7 ms
no-right-click-images.js
245 ms
tracker.php
15090 ms
bgpublicon.jpg
14109 ms
blog_button6.gif
13971 ms
publicon.png
13980 ms
bg.jpg
14142 ms
headerbg.gif
13872 ms
igelst%C3%A4ubling-150x150.jpg
13900 ms
klebrigerh%C3%B6rnling-150x150.jpg
13899 ms
blumenhartriegel1-150x150.jpg
13898 ms
klettenlabkraut1-150x150.jpg
13899 ms
fliegenpilz-150x150.jpg
14061 ms
waldmistk%C3%A4fer-150x150.jpg
14073 ms
Herkulesstaude-150x150.jpg
14081 ms
g%C3%A4nsebl%C3%BCmchen-150x150.jpg
14081 ms
ruprechtskraut-150x150.jpg
14081 ms
besenginster-150x150.jpg
14359 ms
navibg.gif
14246 ms
topborderbg.png
14251 ms
widgettitlebg.gif
14252 ms
google_custom_search_watermark.gif
13793 ms
ca-pub-4683060771083853.js
68 ms
zrt_lookup.html
63 ms
show_ads_impl.js
64 ms
ga.js
22 ms
jquery.lightbox.min.css
479 ms
not.gif
517 ms
loading.gif
629 ms
prev.gif
633 ms
next.gif
633 ms
blank.gif
633 ms
__utm.gif
51 ms
ads
156 ms
osd.js
11 ms
ads
136 ms
ads
209 ms
ads
125 ms
abg.js
16 ms
6280660806085194682
12 ms
x_button_blue2.png
12 ms
s
7 ms
m_js_controller.js
9 ms
googlelogo_color_112x36dp.png
46 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
3 ms
muscus.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
muscus.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
muscus.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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Muscus.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Muscus.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.
muscus.de
Open Graph description is not detected on the main page of Muscus. 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: