7.9 sec in total
334 ms
7 sec
623 ms
Welcome to tomaten.de homepage info - get ready to check Tomaten best content for Germany right away, or after learning these important things about tomaten.de
Bei Tomaten.de steht die Tomate im Mittelpunkt ✓ Lernen Sie alles über Anbau und Pflege von Tomatenpflanzen. Mit vielen Rezepte und Infos zur Verwendung. Das Tomaten-Magazin für alle Liebhaber der rot...
Visit tomaten.deWe analyzed Tomaten.de page load time and found that the first response time was 334 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
tomaten.de performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value7.2 s
5/100
25%
Value7.0 s
32/100
10%
Value310 ms
77/100
30%
Value0.001
100/100
15%
Value11.0 s
21/100
10%
334 ms
1094 ms
418 ms
221 ms
218 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 39% of them (46 requests) were addressed to the original Tomaten.de, 9% (11 requests) were made to S1.2mdn.net and 8% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source S3.amazonaws.com.
Page size can be reduced by 253.2 kB (28%)
903.5 kB
650.3 kB
In fact, the total size of Tomaten.de main page is 903.5 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. 70% of websites need less resources to load. Images take 554.6 kB which makes up the majority of the site volume.
Potential reduce by 54.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 54.2 kB or 78% of the original size.
Potential reduce by 66.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. Obviously, Tomaten needs image optimization as it can save up to 66.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 86.0 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 86.0 kB or 39% of the original size.
Potential reduce by 46.9 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. Tomaten.de needs all CSS files to be minified and compressed as it can save up to 46.9 kB or 80% of the original size.
Number of requests can be reduced by 55 (50%)
110
55
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tomaten. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
tomaten.de
334 ms
www.tomaten.de
1094 ms
main.css
418 ms
fonts.css
221 ms
jquery.fancybox.css
218 ms
jquery.min.js
474 ms
jquery.fancybox.pack.js
221 ms
smooth.pack.js
432 ms
jquery.equalheights.min.js
431 ms
plusone.js
74 ms
cookieconsent.js
432 ms
show_ads.js
5 ms
cb=gapi.loaded_0
58 ms
61KNM0YtCOL._SL90_.jpg
52 ms
61b8kDAvUNL._SL90_.jpg
52 ms
61LF3sNBxJL._SL90_.jpg
51 ms
41GEP3twPFL._SL90_.jpg
52 ms
bg.png
193 ms
bg_header.png
366 ms
index.php
570 ms
bg_logo.png
266 ms
bg_header_title.png
293 ms
bg_mainnav.png
292 ms
nav_back.png
331 ms
trenner.png
530 ms
nav_back.png
568 ms
nav_back.png
567 ms
nav_back.png
598 ms
ad_sticker.png
600 ms
index.php
921 ms
index.php
918 ms
tomatensamen_2.jpg
1004 ms
tomatensuppe_1.jpg
1006 ms
index.php
928 ms
index.php
927 ms
tomaten-rezepte_1.jpg
1218 ms
facebook-tomaten_1.jpg
1233 ms
tomatenfest-tomatina_1.jpg
1346 ms
index.php
1182 ms
tomatenflecken-entfernen-small.jpg
1330 ms
erdbeeren-pflanzen.jpg
1221 ms
gartentagebuch_2.jpg
1512 ms
ca-pub-6849494168309786.js
79 ms
zrt_lookup.html
77 ms
show_ads_impl.js
83 ms
TitilliumText22L005-webfont.woff
1497 ms
TitilliumText22L004-webfont.woff
1507 ms
TitilliumText22L003-webfont.woff
2090 ms
cse.js
61 ms
aws_button_amazon.gif
1498 ms
aws_button_more_information.gif
1499 ms
cse.js
201 ms
arrow_top.gif
1625 ms
bg_most_read.png
1653 ms
bg_head2.png
1660 ms
arrow.gif
1661 ms
arrow.png
1674 ms
ads
352 ms
ga.js
28 ms
osd.js
70 ms
ads
315 ms
like.php
246 ms
cb=gapi.loaded_1
66 ms
fastbutton
137 ms
__utm.gif
52 ms
ads
255 ms
postmessageRelay
74 ms
jsapi
40 ms
default+de.css
15 ms
default.css
30 ms
default+de.I.js
37 ms
cb=gapi.loaded_0
22 ms
cb=gapi.loaded_1
22 ms
default.css
12 ms
3193398744-postmessagerelay.js
136 ms
rpc:shindig_random.js
125 ms
qeKvIRsJabD.js
413 ms
LVx-xkvaJ0b.png
460 ms
async-ads.js
95 ms
google_custom_search_watermark.gif
68 ms
small-logo.png
87 ms
search_box_icon.png
87 ms
clear.png
88 ms
s_0RLrjwjzNL_1716723033.html
119 ms
abg.js
86 ms
m_js_controller.js
99 ms
cb=gapi.loaded_0
47 ms
cl
89 ms
creative_add_on.js
196 ms
s
38 ms
googlelogo_color_112x36dp.png
40 ms
nessie_icon_tiamat_white.png
22 ms
x_button_blue2.png
28 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
6 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
72 ms
lidar.js
41 ms
index.html
34 ms
surly.js
51 ms
styles.css
8 ms
faucet0.png
3 ms
faucet1.png
11 ms
faucet2.png
10 ms
t0.png
11 ms
t1.png
12 ms
logo.svg
13 ms
cta_bg.png
13 ms
cta_text.png
14 ms
bathroom_bg.png
6 ms
ba.html
34 ms
4.gif
36 ms
2532.js
10 ms
activeview
14 ms
box_19_top-right.png
14 ms
ci.png
18 ms
activeview
13 ms
activeview
16 ms
dark-bottom.css
3095 ms
TitilliumText22L003-webfont.ttf
332 ms
ui
13 ms
tomaten.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
tomaten.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
tomaten.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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomaten.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 Tomaten.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.
tomaten.de
Open Graph description is not detected on the main page of Tomaten. 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: