12.5 sec in total
523 ms
11.5 sec
522 ms
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.deWe analyzed Flaywer.de page load time and found that the first response time was 523 ms and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
flaywer.de performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value5.1 s
25/100
25%
Value4.3 s
76/100
10%
Value330 ms
75/100
30%
Value0
100/100
15%
Value4.6 s
81/100
10%
523 ms
219 ms
440 ms
331 ms
328 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that all of those requests were addressed to Flaywer.de and no external sources were called. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Flaywer.de.
Page size can be reduced by 787.4 kB (51%)
1.6 MB
767.1 kB
In fact, the total size of Flaywer.de main page is 1.6 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. 30% of websites need less resources to load. Images take 608.6 kB which makes up the majority of the site volume.
Potential reduce by 84.4 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 28.5 kB, which is 31% 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 84.4 kB or 90% of the original size.
Potential reduce by 14.6 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.
Potential reduce by 347.9 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 347.9 kB or 78% of the original size.
Potential reduce by 340.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. Flaywer.de needs all CSS files to be minified and compressed as it can save up to 340.4 kB or 84% of the original size.
Number of requests can be reduced by 27 (39%)
70
43
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flaywer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
flaywer.de
523 ms
framework.css
219 ms
style.css
440 ms
colors.css
331 ms
plugins.css
328 ms
enrichments.css
223 ms
emotion.css
547 ms
emotion_blue_129.css
656 ms
paypal.css
444 ms
jquery-1.7.2.min.js
870 ms
jquery.shopware.js
994 ms
jquery.emotion.js
652 ms
jquery.poshytip.js
665 ms
tooltip.content.js
802 ms
bg_header_shadow.png
259 ms
piwik.js
437 ms
aromen_body_bg.jpg
543 ms
alle_6_aromenhersteller_auf_flaywer.jpg
762 ms
jacques_le_mon_flaywer.jpg
585 ms
neue_upakete.jpg
650 ms
flaywer_atmoslab_red_apple_285x255.jpg
435 ms
flaywer_tpa_huckleberry_285x255.jpg
859 ms
flaywer_atmoslab_apricot_285x255.jpg
974 ms
flaywer_tpa_sweet_cream_285x255.jpg
900 ms
flaywer_atmoslab_cherry_285x255.jpg
1083 ms
flaywer_tpa_green_apple_285x255.jpg
1187 ms
flaywer_atmoslab_lemonade_285x255.jpg
1288 ms
flaywer_tpa_papaya_285x255.jpg
1330 ms
tpa_logo2.jpg
1188 ms
atmoslab_flaywer_logo.png
1298 ms
meiwei_logo.png
1403 ms
flaywer_tjuice_logo.png
1404 ms
zubehor.jpg
1511 ms
tastypuff_flaywer_logo.jpg
1619 ms
capella_supplier.jpg
1644 ms
flaywer_flavourart_Logo_t.jpg
1729 ms
findus_facebook.png
1619 ms
findus_gplus.png
1720 ms
findus_pinterest.png
1834 ms
bg_searchfield.png
1823 ms
bg_arrow_search.gif
1841 ms
ico_ajax-loader.gif
1930 ms
logo.png
2126 ms
ico_myaccount.png
2032 ms
ico_listing-bottom-active.png
2038 ms
ico-flags.png
2057 ms
ico_basket.png
2145 ms
bg_ajax_basket.png
2246 ms
wrapper_sprite.png
2252 ms
wrapper_bg.png
2273 ms
mainnavigation_bg.png
2339 ms
flaywer_atmoslab_canela.jpg
2272 ms
bg_trans_black.png
1912 ms
flaywer_meiwei_kiwi.jpg
2080 ms
flaywer_tpa_pear.jpg
2070 ms
sprite_stars.png
1724 ms
flaywer_meiwei_black_coffee_140x140.jpg
1811 ms
ico_listing-next.png
1826 ms
flaywer_meiwei_aprikose2_140x140.jpg
1843 ms
flaywer_meiwei_old_captain_140x140.jpg
1864 ms
flaywer_flavourart_default_140x140.jpg
1825 ms
bg_breadcrumb.png
1740 ms
bg_footer.png
1745 ms
bg_footer_menu.png
1812 ms
bg_newsletter.png
1823 ms
bg_arrow_newsletter.gif
1839 ms
ico_closebutton.png
1747 ms
detailinfo_shadow.png
1646 ms
sprite-banner-slider.png
1734 ms
sprite_slider_arrows.png
1799 ms
print.css
109 ms
flaywer.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.
flaywer.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
Missing source maps for large first-party JavaScript
flaywer.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 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.
flaywer.de
Open Graph description is not detected on the main page of Flaywer. 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: