Tools & Wizards About Us
fliesser.de screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fliesser.de

Fliesser - German manufacturer of hoses and oher braid products

Page Load Speed

8.3 sec in total

First Response

2.4 sec

Resources Loaded

5.6 sec

Page Rendered

297 ms

fliesser.de screenshot

About Website

Visit fliesser.de now to see the best up-to-date Fliesser content and also check out these interesting facts you probably never knew about fliesser.de

Fliesser has been active as a customised flexible hoses for sanitary and plumbing applications manufacturer for more than 5 years.

Visit fliesser.de

Key Findings

We analyzed Fliesser.de page load time and found that the first response time was 2.4 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

fliesser.de performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.604

10/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

2395 ms

wp-emoji-release.min.js

125 ms

layerslider.css

228 ms

css

22 ms

styles.css

227 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 70% of them (63 requests) were addressed to the original Fliesser.de, 11% (10 requests) were made to Youtube.com and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Fliesser.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 412.6 kB (3%)

Content Size

14.4 MB

After Optimization

14.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fliesser.de main page is 14.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. Only a small number of websites need less resources to load. Images take 13.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 38.1 kB

  • Original 48.8 kB
  • After minification 47.4 kB
  • After compression 10.6 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 38.1 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 355.3 kB

  • Original 13.8 MB
  • After minification 13.5 MB

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. Fliesser images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 8.1 kB

  • Original 405.5 kB
  • After minification 405.5 kB
  • After compression 397.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 11.0 kB

  • Original 129.7 kB
  • After minification 129.5 kB
  • After compression 118.6 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. Fliesser.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 53 (69%)

Requests Now

77

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fliesser. 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 23 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

2395 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

125 ms

layerslider.css

layerslider.css

228 ms

css

css

22 ms

styles.css

styles.css

227 ms

settings.css

settings.css

244 ms

wordpress-svg-icon-plugin-style.min.css

wordpress-svg-icon-plugin-style.min.css

246 ms

style.css

style.css

358 ms

adaptive.css

adaptive.css

257 ms

retina.css

retina.css

343 ms

fontello.css

fontello.css

345 ms

fontello-custom.css

fontello-custom.css

369 ms

animate.css

animate.css

372 ms

cmsmasters-woo-style.css

cmsmasters-woo-style.css

384 ms

cmsmasters-woo-adaptive.css

cmsmasters-woo-adaptive.css

460 ms

cmsmasters-events-style.css

cmsmasters-events-style.css

463 ms

cmsmasters-events-adaptive.css

cmsmasters-events-adaptive.css

480 ms

ilightbox.css

ilightbox.css

494 ms

dark-skin.css

dark-skin.css

498 ms

all-business.css

all-business.css

744 ms

css

css

20 ms

ytprefs.min.css

ytprefs.min.css

578 ms

greensock.js

greensock.js

688 ms

jquery.js

jquery.js

605 ms

jquery-migrate.min.js

jquery-migrate.min.js

620 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

800 ms

layerslider.transitions.js

layerslider.transitions.js

696 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

735 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

827 ms

jsLibraries.min.js

jsLibraries.min.js

829 ms

jquery.iLightBox.min.js

jquery.iLightBox.min.js

922 ms

ytprefs.min.js

ytprefs.min.js

861 ms

style.css

style.css

863 ms

jquery.megaMenu.js

jquery.megaMenu.js

871 ms

scripts.js

scripts.js

871 ms

add-to-cart.min.js

add-to-cart.min.js

948 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1007 ms

js.cookie.min.js

js.cookie.min.js

1008 ms

woocommerce.min.js

woocommerce.min.js

1008 ms

cart-fragments.min.js

cart-fragments.min.js

890 ms

jqueryLibraries.min.js

jqueryLibraries.min.js

821 ms

jquery.script.js

jquery.script.js

818 ms

jquery.tweet.min.js

jquery.tweet.min.js

903 ms

jquery.cmsmasters-woo-script.js

jquery.cmsmasters-woo-script.js

901 ms

comment-reply.min.js

comment-reply.min.js

892 ms

fitvids.min.js

fitvids.min.js

806 ms

wp-embed.min.js

wp-embed.min.js

1004 ms

Logo_195px.png

Logo_195px.png

412 ms

Logo_390.png

Logo_390.png

450 ms

Slider_1.jpg

Slider_1.jpg

1040 ms

line__.png

line__.png

450 ms

Slider_2.jpg

Slider_2.jpg

1058 ms

Slider_3.jpg

Slider_3.jpg

1033 ms

IMG_4367_DN6.jpg

IMG_4367_DN6.jpg

819 ms

IMG_4344_DN8.jpg

IMG_4344_DN8.jpg

818 ms

IMG_4530_washing_m_.jpg

IMG_4530_washing_m_.jpg

1044 ms

Production_6a-01.jpg

Production_6a-01.jpg

1047 ms

Production_6a-02.jpg

Production_6a-02.jpg

1050 ms

Production_6a-03.jpg

Production_6a-03.jpg

1158 ms

Production_6a-04.jpg

Production_6a-04.jpg

1171 ms

Production_6a_05.jpg

Production_6a_05.jpg

1295 ms

Production_6a_06.jpg

Production_6a_06.jpg

1181 ms

Production_6a_07.jpg

Production_6a_07.jpg

1190 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

11 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

43 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

44 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

44 ms

xKZQ6AlVQrk

xKZQ6AlVQrk

141 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

22 ms

base.js

base.js

48 ms

id

id

134 ms

ad_status.js

ad_status.js

129 ms

Create

Create

107 ms

qoe

qoe

85 ms

s9i9Iyk4Y_s1LD6aqz2X9kjqPppJUVpoTsMZDucYENo.js

s9i9Iyk4Y_s1LD6aqz2X9kjqPppJUVpoTsMZDucYENo.js

81 ms

embed.js

embed.js

59 ms

skin.css

skin.css

774 ms

xKZQ6AlVQrk

xKZQ6AlVQrk

137 ms

iframe_api

iframe_api

32 ms

www-widgetapi.js

www-widgetapi.js

3 ms

ad_status.js

ad_status.js

93 ms

s9i9Iyk4Y_s1LD6aqz2X9kjqPppJUVpoTsMZDucYENo.js

s9i9Iyk4Y_s1LD6aqz2X9kjqPppJUVpoTsMZDucYENo.js

35 ms

embed.js

embed.js

12 ms

Create

Create

120 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

96 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

196 ms

id

id

91 ms

GenerateIT

GenerateIT

16 ms

skin.png

skin.png

124 ms

Accessibility Review

fliesser.de accessibility score

72

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

fliesser.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fliesser.de SEO score

93

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fliesser.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fliesser.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

fliesser.de

Open Graph data is detected on the main page of Fliesser. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: