19.7 sec in total
809 ms
18.6 sec
273 ms
Visit kakteen.ws now to see the best up-to-date Kakteen content and also check out these interesting facts you probably never knew about kakteen.ws
Kurzinfos zur Familie der Kakteen und Bestimmungshilfen für die einzelnen Arten sowie für ähnlich aussehende Sukkulenten.
Visit kakteen.wsWe analyzed Kakteen.ws page load time and found that the first response time was 809 ms and then it took 18.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
kakteen.ws performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value5.4 s
21/100
25%
Value5.5 s
55/100
10%
Value1,840 ms
9/100
30%
Value0
100/100
15%
Value9.9 s
27/100
10%
809 ms
326 ms
218 ms
456 ms
226 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 44% of them (25 requests) were addressed to the original Kakteen.ws, 12% (7 requests) were made to Pagead2.googlesyndication.com and 11% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (16.7 sec) belongs to the original domain Kakteen.ws.
Page size can be reduced by 313.7 kB (34%)
913.7 kB
600.0 kB
In fact, the total size of Kakteen.ws main page is 913.7 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. Images take 418.5 kB which makes up the majority of the site volume.
Potential reduce by 13.8 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 13.8 kB or 73% of the original size.
Potential reduce by 2.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. Kakteen images are well optimized though.
Potential reduce by 205.7 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 205.7 kB or 57% of the original size.
Potential reduce by 92.3 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. Kakteen.ws needs all CSS files to be minified and compressed as it can save up to 92.3 kB or 82% of the original size.
Number of requests can be reduced by 32 (62%)
52
20
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kakteen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
kakteen.ws
809 ms
wp-emoji-release.min.js
326 ms
front.css
218 ms
style.css
456 ms
responsive.css
226 ms
font-awesome.min.css
228 ms
jquery.js
554 ms
jquery-migrate.min.js
442 ms
jquery.flexslider.min.js
445 ms
adsbygoogle.js
6 ms
front.js
438 ms
jquery.jplayer.min.js
676 ms
scripts.js
681 ms
wp-embed.min.js
682 ms
Kakteen-Sukkulente.jpg
16661 ms
ca-pub-7836581778119886.js
36 ms
zrt_lookup.html
40 ms
show_ads_impl.js
52 ms
Header.jpg
16619 ms
opacity-10.png
220 ms
s-right-s2.png
262 ms
s-left.png
270 ms
titillium-light-webfont.svg
16619 ms
titillium-regular-webfont.svg
16622 ms
titillium-semibold-webfont.svg
16620 ms
fontawesome-webfont.woff
16621 ms
ads
242 ms
piwik.js
16542 ms
osd.js
14 ms
ads
16438 ms
ads
16431 ms
ads
16400 ms
abg.js
73 ms
css
97 ms
m_js_controller.js
79 ms
s_0RInxextBY_2088657436.html
76 ms
titillium-light-webfont.woff
432 ms
titillium-regular-webfont.woff
437 ms
titillium-semibold-webfont.woff
447 ms
cl
104 ms
creative_add_on.js
170 ms
nessie_icon_tiamat_white.png
34 ms
s
28 ms
googlelogo_color_112x36dp.png
28 ms
x_button_blue2.png
18 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
4 ms
RIS247_Banner_160x600_02.jpg
66 ms
lidar.js
20 ms
sbhK2lTE.js
16 ms
cTrvNaRi.html
11 ms
surly.js
52 ms
ba.html
18 ms
4.gif
24 ms
2532.js
9 ms
box_19_top-right.png
10 ms
ci.png
12 ms
activeview
14 ms
kakteen.ws 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
[aria-*] attributes do not match their roles
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
kakteen.ws 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
kakteen.ws SEO score
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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kakteen.ws 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 Kakteen.ws 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.
kakteen.ws
Open Graph description is not detected on the main page of Kakteen. 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: