Tools & Wizards About Us
flaywer.de screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

flaywer.de

Flaywer - Über 600 leckere Aromen für jeden Geschmack!

Page Load Speed

2.7 sec in total

First Response

352 ms

Resources Loaded

2.2 sec

Page Rendered

117 ms

flaywer.de screenshot

About Website

Welcome to flaywer.de homepage info - get ready to check Flaywer best content for Switzerland right away, or after learning these important things about flaywer.de

Auf Flaywer finden Sie viele leckere Aromen zum Selbermischen, tolle Milkshakes, Joghurts oder zum Aromatisieren von Wasser.

Visit flaywer.de

Key Findings

We analyzed Flaywer.de page load time and found that the first response time was 352 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

flaywer.de performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value4.1 s

80/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

flaywer.de

352 ms

flaywer.de

456 ms

1710722505_28c8463925abd745a8a657f92c31388e.css

221 ms

1710722505_28c8463925abd745a8a657f92c31388e.js

663 ms

findus_facebook.png

320 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 87% of them (13 requests) were addressed to the original Flaywer.de, 13% (2 requests) were made to Matomo.flaywer.de. The less responsive or slowest element that took the longest time to load (692 ms) relates to the external source Matomo.flaywer.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.5 kB (11%)

Content Size

413.9 kB

After Optimization

367.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flaywer.de main page is 413.9 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. 15% of websites need less resources to load. Javascripts take 165.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 45.9 kB

  • Original 56.5 kB
  • After minification 56.5 kB
  • After compression 10.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. 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 45.9 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 96 B

  • Original 130.6 kB
  • After minification 130.5 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. Flaywer images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 31 B

  • Original 165.1 kB
  • After minification 165.1 kB
  • After compression 165.1 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

-1%

Potential reduce by 492 B

  • Original 61.7 kB
  • After minification 61.7 kB
  • After compression 61.2 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. Flaywer.de has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flaywer. According to our analytics all requests are already optimized.

Network Requests Diagram

flaywer.de

flaywer.de

352 ms

flaywer.de

flaywer.de

456 ms

1710722505_28c8463925abd745a8a657f92c31388e.css

1710722505_28c8463925abd745a8a657f92c31388e.css

221 ms

1710722505_28c8463925abd745a8a657f92c31388e.js

1710722505_28c8463925abd745a8a657f92c31388e.js

663 ms

findus_facebook.png

findus_facebook.png

320 ms

findus_pinterest.png

findus_pinterest.png

320 ms

flaywer_background_header_small_2020_trans_1920x1920.png

flaywer_background_header_small_2020_trans_1920x1920.png

318 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

382 ms

OpenSans-Light.woff

OpenSans-Light.woff

390 ms

OpenSans-Semibold.woff

OpenSans-Semibold.woff

539 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

533 ms

OpenSans-ExtraBold.woff

OpenSans-ExtraBold.woff

428 ms

shopware.woff

shopware.woff

424 ms

piwik.js

piwik.js

692 ms

piwik.php

piwik.php

380 ms

Accessibility Review

flaywer.de accessibility score

97

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.

Best Practices

flaywer.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

flaywer.de SEO score

92

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

flaywer.de

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