Tools & Wizards About Us
weitz-wasserwelt.de screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

weitz-wasserwelt.de

Teichpflege Weitz Wasserwelt, Teichpflegeprodukte online

Page Load Speed

5.3 sec in total

First Response

192 ms

Resources Loaded

4.8 sec

Page Rendered

313 ms

weitz-wasserwelt.de screenshot

About Website

Welcome to weitz-wasserwelt.de homepage info - get ready to check Weitz Wasserwelt best content for Germany right away, or after learning these important things about weitz-wasserwelt.de

Teichpflege Weitz Wasserwelt, dem führenden Anbieter von biotechnischen u. naturbiologischen Produkten für Teichpflege + Wasserpflege

Visit weitz-wasserwelt.de

Key Findings

We analyzed Weitz-wasserwelt.de page load time and found that the first response time was 192 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

weitz-wasserwelt.de performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.833

4/100

15%

TTI (Time to Interactive)

Value13.7 s

10/100

10%

Network Requests Diagram

weitz-wasserwelt.de

192 ms

www.weitz-wasserwelt.de

659 ms

calendar.css

96 ms

mpBlogIcon.css

191 ms

styles-m.css

477 ms

Our browser made a total of 182 requests to load all elements on the main page. We found that 94% of them (171 requests) were addressed to the original Weitz-wasserwelt.de, 3% (6 requests) were made to Provenexpert.com and 1% (2 requests) were made to Code.etracker.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Weitz-wasserwelt.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 516.9 kB (42%)

Content Size

1.2 MB

After Optimization

701.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weitz-wasserwelt.de main page is 1.2 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. 70% of websites need less resources to load. Images take 645.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 212.4 kB

  • Original 235.2 kB
  • After minification 177.2 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 58.0 kB, which is 25% 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 212.4 kB or 90% of the original size.

Image Optimization

-32%

Potential reduce by 205.4 kB

  • Original 645.5 kB
  • After minification 440.1 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, Weitz Wasserwelt needs image optimization as it can save up to 205.4 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 88.2 kB

  • Original 148.9 kB
  • After minification 148.9 kB
  • After compression 60.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 88.2 kB or 59% of the original size.

CSS Optimization

-6%

Potential reduce by 10.9 kB

  • Original 188.3 kB
  • After minification 188.3 kB
  • After compression 177.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. Weitz-wasserwelt.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 136 (80%)

Requests Now

170

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 170 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weitz Wasserwelt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 115 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

weitz-wasserwelt.de

weitz-wasserwelt.de

192 ms

www.weitz-wasserwelt.de

www.weitz-wasserwelt.de

659 ms

calendar.css

calendar.css

96 ms

mpBlogIcon.css

mpBlogIcon.css

191 ms

styles-m.css

styles-m.css

477 ms

owl.carousel.css

owl.carousel.css

301 ms

jquery.fancybox.css

jquery.fancybox.css

283 ms

porto-icons-codes.css

porto-icons-codes.css

300 ms

simple-line-icons.css

simple-line-icons.css

301 ms

animation.css

animation.css

302 ms

font-awesome.min.css

font-awesome.min.css

376 ms

frendlyCaptcha.css

frendlyCaptcha.css

393 ms

algoliasearch.css

algoliasearch.css

394 ms

style.css

style.css

395 ms

owl.carousel.css

owl.carousel.css

396 ms

styles-l.css

styles-l.css

569 ms

9664721b367fea0223dc14c4aeaea616.js

9664721b367fea0223dc14c4aeaea616.js

591 ms

uc.js

uc.js

25 ms

bootstrap.min.css

bootstrap.min.css

618 ms

animate.css

animate.css

507 ms

type1.css

type1.css

507 ms

custom.css

custom.css

585 ms

design_de.css

design_de.css

623 ms

settings_de.css

settings_de.css

625 ms

font-awesome.min.css

font-awesome.min.css

25 ms

e.js

e.js

791 ms

bar_weitz-wasserwelt.js

bar_weitz-wasserwelt.js

227 ms

widget.module.min.js

widget.module.min.js

688 ms

jquery.js

jquery.js

305 ms

common.js

common.js

102 ms

dataPost.js

dataPost.js

130 ms

bootstrap.js

bootstrap.js

131 ms

app.js

app.js

129 ms

form-key-provider.js

form-key-provider.js

178 ms

mage-translation-dictionary.js

mage-translation-dictionary.js

222 ms

theme.js

theme.js

223 ms

cookies.js

cookies.js

222 ms

logo_1.webp

logo_1.webp

201 ms

02.webp

02.webp

224 ms

art._210_kombi_500g_1_.webp

art._210_kombi_500g_1_.webp

266 ms

art._191_fadenalgenkiller_500g_1_.webp

art._191_fadenalgenkiller_500g_1_.webp

308 ms

art._310_sauerstoff_aktiv_500g_1_1.webp

art._310_sauerstoff_aktiv_500g_1_1.webp

309 ms

art._011_brilliant_1_kg_1_.webp

art._011_brilliant_1_kg_1_.webp

309 ms

art._250_nm_biospeed_500g_1_.webp

art._250_nm_biospeed_500g_1_.webp

310 ms

art._115__algenkiller_protect_150g_1_.webp

art._115__algenkiller_protect_150g_1_.webp

350 ms

ad1n.webp

ad1n.webp

367 ms

ad2n_1.webp

ad2n_1.webp

381 ms

ad3n.webp

ad3n.webp

384 ms

client-1-11_1.webp

client-1-11_1.webp

383 ms

img1.webp

img1.webp

401 ms

img3.webp

img3.webp

443 ms

teichservice-startseite.webp

teichservice-startseite.webp

460 ms

Videobild_Algenkiller_1.webp

Videobild_Algenkiller_1.webp

660 ms

zahlunggls.webp

zahlunggls.webp

478 ms

jquery-mixin.js

jquery-mixin.js

463 ms

apear.js

apear.js

476 ms

OpenSans-Regular.ttf

OpenSans-Regular.ttf

706 ms

opensans-400.woff

opensans-400.woff

540 ms

opensans-300.woff

opensans-300.woff

650 ms

opensans-600.woff

opensans-600.woff

562 ms

opensans-700.woff

opensans-700.woff

573 ms

autocomplete.js

autocomplete.js

600 ms

typeahead.js

typeahead.js

626 ms

porto-icons.woff

porto-icons.woff

718 ms

domReady.js

domReady.js

666 ms

sw_megamenu.js

sw_megamenu.js

650 ms

Hotel_Mooshof_Bodenmais_Credit_040424.jpg

Hotel_Mooshof_Bodenmais_Credit_040424.jpg

1187 ms

owl.carousel.min.js

owl.carousel.min.js

695 ms

template.js

template.js

664 ms

confirm.js

confirm.js

642 ms

widget.js

widget.js

650 ms

main.js

main.js

665 ms

bootstrap.js

bootstrap.js

681 ms

t.js

t.js

110 ms

types.js

types.js

688 ms

provenexpert_logo_black.png

provenexpert_logo_black.png

10 ms

browserbar.css

browserbar.css

10 ms

bubble.png

bubble.png

31 ms

titilliumweb-regular-webfont.woff

titilliumweb-regular-webfont.woff

4 ms

titilliumweb-semibold-webfont.woff

titilliumweb-semibold-webfont.woff

12 ms

layout.js

layout.js

672 ms

Oswald-Regular.ttf

Oswald-Regular.ttf

667 ms

ShadowsIntoLight-Regular.ttf

ShadowsIntoLight-Regular.ttf

656 ms

text.js

text.js

672 ms

mage.js

mage.js

696 ms

cookie-wrapper.js

cookie-wrapper.js

714 ms

smart-keyboard-handler.js

smart-keyboard-handler.js

689 ms

jquery.lazyload.js

jquery.lazyload.js

687 ms

cntcc

cntcc

519 ms

wrapper.js

wrapper.js

595 ms

underscore.js

underscore.js

422 ms

translate.js

translate.js

444 ms

modal.js

modal.js

445 ms

version.js

version.js

433 ms

scripts.js

scripts.js

420 ms

knockout.js

knockout.js

405 ms

knockout-es5.js

knockout-es5.js

406 ms

engine.js

engine.js

402 ms

bootstrap.js

bootstrap.js

405 ms

observable_array.js

observable_array.js

406 ms

bound-nodes.js

bound-nodes.js

434 ms

main.js

main.js

419 ms

registry.js

registry.js

387 ms

console-logger.js

console-logger.js

388 ms

js-translation.json

js-translation.json

352 ms

js.cookie.js

js.cookie.js

325 ms

animate.js

animate.js

302 ms

client-1-11_1.webp

client-1-11_1.webp

133 ms

art._210_kombi_500g_1_.webp

art._210_kombi_500g_1_.webp

134 ms

art._115__algenkiller_protect_150g_1_.webp

art._115__algenkiller_protect_150g_1_.webp

136 ms

art._011_brilliant_1_kg_1_.webp

art._011_brilliant_1_kg_1_.webp

141 ms

art._191_fadenalgenkiller_500g_1_.webp

art._191_fadenalgenkiller_500g_1_.webp

167 ms

art._250_nm_biospeed_500g_1_.webp

art._250_nm_biospeed_500g_1_.webp

224 ms

art._310_sauerstoff_aktiv_500g_1_1.webp

art._310_sauerstoff_aktiv_500g_1_1.webp

230 ms

modal-popup.html

modal-popup.html

216 ms

modal-slide.html

modal-slide.html

220 ms

modal-custom.html

modal-custom.html

221 ms

key-codes.js

key-codes.js

246 ms

core.js

core.js

301 ms

z-index.js

z-index.js

302 ms

knockout-repeat.js

knockout-repeat.js

291 ms

knockout-fast-foreach.js

knockout-fast-foreach.js

293 ms

observable_source.js

observable_source.js

293 ms

renderer.js

renderer.js

322 ms

resizable.js

resizable.js

376 ms

i18n.js

i18n.js

376 ms

scope.js

scope.js

381 ms

range.js

range.js

383 ms

mage-init.js

mage-init.js

385 ms

keyboard.js

keyboard.js

414 ms

optgroup.js

optgroup.js

468 ms

after-render.js

after-render.js

468 ms

autoselect.js

autoselect.js

473 ms

datepicker.js

datepicker.js

474 ms

outer_click.js

outer_click.js

475 ms

fadeVisible.js

fadeVisible.js

506 ms

collapsible.js

collapsible.js

560 ms

staticChecked.js

staticChecked.js

560 ms

simple-checked.js

simple-checked.js

563 ms

bind-html.js

bind-html.js

563 ms

tooltip.js

tooltip.js

561 ms

color-picker.js

color-picker.js

569 ms

events.js

events.js

564 ms

local.js

local.js

562 ms

arrays.js

arrays.js

568 ms

compare.js

compare.js

566 ms

misc.js

misc.js

562 ms

objects.js

objects.js

569 ms

strings.js

strings.js

560 ms

template.js

template.js

558 ms

logger.js

logger.js

562 ms

entry-factory.js

entry-factory.js

561 ms

console-output-handler.js

console-output-handler.js

562 ms

formatter.js

formatter.js

569 ms

message-pool.js

message-pool.js

563 ms

levels-pool.js

levels-pool.js

562 ms

logger-utils.js

logger-utils.js

568 ms

data.js

data.js

567 ms

disable-selection.js

disable-selection.js

562 ms

focusable.js

focusable.js

569 ms

form.js

form.js

563 ms

ie.js

ie.js

564 ms

keycode.js

keycode.js

565 ms

labels.js

labels.js

566 ms

jquery-patch.js

jquery-patch.js

565 ms

plugin.js

plugin.js

569 ms

safe-active-element.js

safe-active-element.js

563 ms

safe-blur.js

safe-blur.js

563 ms

scroll-parent.js

scroll-parent.js

564 ms

tabbable.js

tabbable.js

566 ms

unique-id.js

unique-id.js

565 ms

class.js

class.js

569 ms

loader.js

loader.js

565 ms

async.js

async.js

567 ms

tooltip.html

tooltip.html

560 ms

spectrum.js

spectrum.js

543 ms

tinycolor.js

tinycolor.js

548 ms

entry.js

entry.js

409 ms

moment.js

moment.js

432 ms

dom-observer.js

dom-observer.js

100 ms

bindings.js

bindings.js

99 ms

print.css

print.css

96 ms

Accessibility Review

weitz-wasserwelt.de accessibility score

70

Accessibility Issues

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

High

[role]s do not have all required [aria-*] attributes

High

[role]s are not contained by their required parent element

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

weitz-wasserwelt.de best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

weitz-wasserwelt.de SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weitz-wasserwelt.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 Weitz-wasserwelt.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.

Social Sharing Optimization

weitz-wasserwelt.de

Open Graph description is not detected on the main page of Weitz Wasserwelt. 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: