3.4 sec in total
732 ms
2.4 sec
249 ms
Visit taspo.de now to see the best up-to-date TASPO content for United States and also check out these interesting facts you probably never knew about taspo.de
Das Magazin für alles rund um die Grüne Branche! Jetzt auf einen Blick online.
Visit taspo.deWe analyzed Taspo.de page load time and found that the first response time was 732 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
taspo.de performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value15.2 s
0/100
25%
Value11.0 s
6/100
10%
Value680 ms
44/100
30%
Value0.153
75/100
15%
Value16.5 s
5/100
10%
732 ms
402 ms
423 ms
357 ms
15 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 75% of them (46 requests) were addressed to the original Taspo.de, 8% (5 requests) were made to Tpc.googlesyndication.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Taspo.de.
Page size can be reduced by 555.7 kB (41%)
1.4 MB
799.7 kB
In fact, the total size of Taspo.de main page is 1.4 MB. 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 603.6 kB which makes up the majority of the site volume.
Potential reduce by 65.7 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. This page needs HTML code to be minified as it can gain 18.9 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 65.7 kB or 84% of the original size.
Potential reduce by 7.4 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. TASPO images are well optimized though.
Potential reduce by 301.2 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 301.2 kB or 66% of the original size.
Potential reduce by 181.4 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. Taspo.de needs all CSS files to be minified and compressed as it can save up to 181.4 kB or 83% of the original size.
Number of requests can be reduced by 7 (13%)
56
49
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TASPO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
taspo.de
732 ms
merged-5e263d1653deda2dd07ca5c1a0cbf5d2-b2885cb5ac7f8a8bb6434efc5426088f.css
402 ms
merged-ef4bff6dd818a244063dc4f4e440902e-d39ff39662b10d15b586532572a436f2.js
423 ms
merged-27f06597f25c22779532b9ad21346b93-024c41851bb78e790406634e230fe962.js
357 ms
gpt.js
15 ms
whatsapp.png
134 ms
taspo_logo.png
137 ms
search_btn.png
134 ms
csm_Rewe_Center_Blumenshop_Elgner_9bff9be901.jpg
585 ms
csm_BKN_Strobel_Baumschule_Pflanzenlager_c64314dad6.jpg
424 ms
csm_Gaertnerei_Tablet_Aurelio_Slider_e76a746946.jpg
374 ms
csm_Flora_Mythica_Dornroeschen_dcec3e475e.jpg
536 ms
csm_Friedhof_Grab_Jacob_Lund_2a80445aae.jpg
610 ms
icon_more_detail.png
269 ms
csm_Torfabbau_Griendtsveen_AG_9a159a9595.jpg
377 ms
csm_Fotolia_3724068_garteneidechse_a1d790f169.jpg
484 ms
csm_Woerlein_Gartencenter_Aussenansicht_rve_9a850a5c67.jpg
491 ms
csm_toom_Plakat_ProPlanet_167c327310.jpg
524 ms
csm_Fotolia_21295015_squadcsplayer_9c4e37c72d.jpg
587 ms
csm_Gruenflaeche_Stadt_6cc792a050.jpg
604 ms
csm_Fotolia_66161760_XS_B_Wylezich_264c782170.jpg
630 ms
csm_Fotolia_17131633_mopsgrafik_ef58ad31cb.jpg
648 ms
csm_Grab_Fruehling_Trends_Bayern_9ef9d9bf34.jpg
693 ms
csm_FBB_Gruendachsymposium_c9313e968f.jpg
695 ms
csm_Plantarium_2014_2_ae24d13737.jpg
712 ms
csm_haus_garten_freizeit_2016_c7a90ca8c5.jpg
714 ms
csm_Guerilla_Aktion_Schule_fuer_Weinbau_Gartenbau_Veitshoechheim_d124a0b253.jpg
794 ms
csm_Hochschule_Fotolia_kasto_449fccafeb.jpg
819 ms
csm_Baumstaemme_gerodet_Fotolia__Alberto_Masnovo_3f36c6705e.jpg
844 ms
csm_Indega_IPM_Innovation_Award_3fb7c486bb.jpg
854 ms
csm_Hornbach_Markt_aussen_98af3c9533.jpg
866 ms
csm_Plenarsaal_Deutscher_Bundestag_Marc-Steffen_Unger_6114cc27ee.jpg
865 ms
icon_alle_news.png
921 ms
csm_Taspo_Dossier_trans_d0a8f3acdc.png
923 ms
csm_Woerlein_Webseite_Screenshot_4608deb373.jpg
965 ms
csm_Gartenbau_Produktion_Kraeuter_be2c9f0d77.jpg
1022 ms
csm_Screenshot_Taspo_Video_Interview_Roel_De_Jong_adbc6079b4.jpg
1050 ms
deutsche-baumschule.png
1051 ms
friedhofs-kultur.png
1052 ms
guv.png
1046 ms
gaertnerboerse.png
1058 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
115 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
116 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
116 ms
pubads_impl_81.js
14 ms
show_companion_ad.js
47 ms
ads
197 ms
container.html
47 ms
baumzeitung.png
996 ms
taspo-garten-design.png
1022 ms
fontawesome-webfont.woff
1162 ms
ga.js
56 ms
__utm.gif
11 ms
taspo.png
867 ms
9238205632292713365
81 ms
3621382929009902455
77 ms
8024937154827719500
49 ms
4858562675173146501
90 ms
osd.js
5 ms
csm_Taspo_Dossier_trans_61773d4ee0.png
787 ms
arrow_right.png
810 ms
taspo.de 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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
taspo.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
Page has valid source maps
taspo.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Taspo.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 Taspo.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.
taspo.de
Open Graph description is not detected on the main page of TASPO. 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: