Tools & Wizards About Us
febreze.de screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    43% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

febreze.de

Febreze: Bewertungen lesen & selber schreiben | for me

Page Load Speed

4.1 sec in total

First Response

421 ms

Resources Loaded

3.4 sec

Page Rendered

335 ms

febreze.de screenshot

About Website

Welcome to febreze.de homepage info - get ready to check Febreze best content right away, or after learning these important things about febreze.de

Febreze entfernt Gerüche, statt sie zu überdecken. Entdecke das Febreze Sicherheitsversprechen, Tipps sowie ehrliche Produktbewertungen ➪ Jetzt lesen!

Visit febreze.de

Key Findings

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

Performance Metrics

febreze.de performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value23.6 s

0/100

10%

TBT (Total Blocking Time)

Value30,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value45.5 s

0/100

10%

Network Requests Diagram

febreze.de

421 ms

18 ms

2153 ms

global-min.js

169 ms

tag.js

80 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Febreze.de, 78% (25 requests) were made to For-me-online-de.secure.footprint.net and 9% (3 requests) were made to S.btstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source For-me-online.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (70%)

Content Size

1.5 MB

After Optimization

458.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Febreze.de main page is 1.5 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. 35% of websites need less resources to load. CSS take 676.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 158.9 kB

  • Original 183.6 kB
  • After minification 147.6 kB
  • After compression 24.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 36.0 kB, which is 20% 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 158.9 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 10.9 kB

  • Original 230.5 kB
  • After minification 219.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. Febreze images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 300.0 kB

  • Original 423.7 kB
  • After minification 422.8 kB
  • After compression 123.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 300.0 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 586.5 kB

  • Original 676.5 kB
  • After minification 669.7 kB
  • After compression 90.0 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. Febreze.de needs all CSS files to be minified and compressed as it can save up to 586.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (38%)

Requests Now

24

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

febreze.de

febreze.de

421 ms

18 ms

2153 ms

global-min.js

global-min.js

169 ms

tag.js

tag.js

80 ms

logoEverydayme.gif

logoEverydayme.gif

136 ms

program-selector-de.jpg

program-selector-de.jpg

147 ms

program-selector-vi.jpg

program-selector-vi.jpg

140 ms

PGShop.jpg

PGShop.jpg

144 ms

BraunShop.jpg

BraunShop.jpg

142 ms

header_bg_news-aktionen_desktop.jpg

header_bg_news-aktionen_desktop.jpg

246 ms

arrow.png

arrow.png

164 ms

arrow_white_small.png

arrow_white_small.png

173 ms

arrow_blue_small.png

arrow_blue_small.png

169 ms

de-DE9823215152002-2-size-1.jpg

de-DE9823215152002-2-size-1.jpg

159 ms

transparent.png

transparent.png

179 ms

ravensburger.jpg

ravensburger.jpg

187 ms

ad_choice.jpg

ad_choice.jpg

184 ms

global-de-de.css

global-de-de.css

37 ms

transparent.png

transparent.png

81 ms

rockwell-cyrillic-std.woff

rockwell-cyrillic-std.woff

78 ms

rockwell-cyrillic-bold.woff

rockwell-cyrillic-bold.woff

81 ms

icons.ttf

icons.ttf

81 ms

frutiger-cyrillic-bold.woff

frutiger-cyrillic-bold.woff

97 ms

frutiger-cyrillic-std.woff

frutiger-cyrillic-std.woff

97 ms

tag

tag

82 ms

Febreze5-neu-3-size-2.jpg

Febreze5-neu-3-size-2.jpg

92 ms

Tirocke-Visual-neu-3-size-2.jpg

Tirocke-Visual-neu-3-size-2.jpg

90 ms

Stiftung-RTL-Visual-neu-2-2-size-2.jpg

Stiftung-RTL-Visual-neu-2-2-size-2.jpg

35 ms

febreze-vanille-4-size-1.jpg

febreze-vanille-4-size-1.jpg

25 ms

a46f12f820f911feb7336318592d831fdc200db9.js

a46f12f820f911feb7336318592d831fdc200db9.js

9 ms

278afe2d73add98b2852b30170b81e0cd7f64e79.js

278afe2d73add98b2852b30170b81e0cd7f64e79.js

29 ms

Accessibility Review

febreze.de accessibility score

93

Accessibility Issues

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

High

Some elements have a [tabindex] value greater than 0

Best Practices

febreze.de best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

febreze.de SEO score

91

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 Febreze.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 Febreze.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

febreze.de

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