Tools & Wizards About Us
febreze.ch screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

febreze.ch

Febreze: Bewertungen lesen & selber schreiben | for me

Page Load Speed

4.3 sec in total

First Response

238 ms

Resources Loaded

4 sec

Page Rendered

53 ms

febreze.ch screenshot

About Website

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

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

Visit febreze.ch

Key Findings

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

Performance Metrics

febreze.ch performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value22.1 s

0/100

10%

TBT (Total Blocking Time)

Value21,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value36.8 s

0/100

10%

Network Requests Diagram

febreze

238 ms

febreze

697 ms

fonts.css

749 ms

122.73087ff6.chunk.css

1051 ms

main.1df4b938.chunk.css

624 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Febreze.ch, 29% (16 requests) were made to Youtube-nocookie.com and 14% (8 requests) were made to Prd-cdn-emea1-joltx.pgsitecore.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Prd-cdn-emea1-joltx.pgsitecore.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.5 kB (7%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Febreze.ch main page is 1.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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 83.2 kB

  • Original 106.9 kB
  • After minification 106.9 kB
  • After compression 23.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 83.2 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 1.1 MB
  • After minification 1.1 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. Febreze images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 15.3 kB

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

-0%

Potential reduce by 0 B

  • Original 59.2 kB
  • After minification 59.2 kB
  • After compression 59.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. Febreze.ch has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (44%)

Requests Now

41

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 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 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

febreze

febreze

238 ms

febreze

febreze

697 ms

fonts.css

fonts.css

749 ms

122.73087ff6.chunk.css

122.73087ff6.chunk.css

1051 ms

main.1df4b938.chunk.css

main.1df4b938.chunk.css

624 ms

logo-positiv--196x196.ashx

logo-positiv--196x196.ashx

621 ms

aViUqEaXR94

aViUqEaXR94

98 ms

OIygN-MRQU0

OIygN-MRQU0

544 ms

q4YabdFXRd0

q4YabdFXRd0

493 ms

Dh691PjVuk4

Dh691PjVuk4

443 ms

122.87ab08d8.chunk.js

122.87ab08d8.chunk.js

971 ms

main.b387efb2.chunk.js

main.b387efb2.chunk.js

747 ms

teaser-lufterfrischer.ashx

teaser-lufterfrischer.ashx

1327 ms

teaser-textilerfrischer.ashx

teaser-textilerfrischer.ashx

1452 ms

teaser-car.ashx

teaser-car.ashx

1494 ms

teaser-duftstecker.ashx

teaser-duftstecker.ashx

1627 ms

infografik-1.ashx

infografik-1.ashx

1359 ms

infografik-2.ashx

infografik-2.ashx

1484 ms

infografik-3.ashx

infografik-3.ashx

1865 ms

www-player.css

www-player.css

16 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

55 ms

embed.js

embed.js

167 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

26 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

29 ms

Create

Create

25 ms

Create

Create

107 ms

Create

Create

108 ms

Create

Create

105 ms

GenerateIT

GenerateIT

348 ms

GenerateIT

GenerateIT

353 ms

GenerateIT

GenerateIT

284 ms

GenerateIT

GenerateIT

210 ms

de-DE

de-DE

397 ms

Montserrat-regular.woff

Montserrat-regular.woff

696 ms

Montserrat-semibold.woff

Montserrat-semibold.woff

716 ms

Montserrat-bold.woff

Montserrat-bold.woff

858 ms

picturefill.min.js

picturefill.min.js

140 ms

qoe

qoe

9 ms

log_event

log_event

0 ms

qoe

qoe

6 ms

log_event

log_event

0 ms

qoe

qoe

7 ms

log_event

log_event

0 ms

qoe

qoe

7 ms

log_event

log_event

1 ms

BreadcrumbsContainer.108ffd4c.chunk.js

BreadcrumbsContainer.108ffd4c.chunk.js

367 ms

BrandHero.a08aa0e0.chunk.js

BrandHero.a08aa0e0.chunk.js

558 ms

Separator.27fbdbf0.chunk.js

Separator.27fbdbf0.chunk.js

344 ms

globalRichText.2f51abb7.chunk.js

globalRichText.2f51abb7.chunk.js

333 ms

Tabs.056006e1.chunk.js

Tabs.056006e1.chunk.js

618 ms

CookieConsent.1924ff00.chunk.js

CookieConsent.1924ff00.chunk.js

708 ms

Footer.cb2ecc67.chunk.css

Footer.cb2ecc67.chunk.css

760 ms

Footer.c37f5bdc.chunk.js

Footer.c37f5bdc.chunk.js

975 ms

sso_lite.js

sso_lite.js

27 ms

gtm.js

gtm.js

110 ms

Accessibility Review

febreze.ch accessibility score

99

Accessibility Issues

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

febreze.ch 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

febreze.ch 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.ch 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.ch 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.ch

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