4.1 sec in total
90 ms
2.6 sec
1.4 sec
Click here to check amazing Swiffer content. Otherwise, check out these important facts you probably never knew about swiffer.de
for me stellt Ihnen Swiffer Produkte, Gewinnspiele, Tipps und Storys vor. Erfahren Sie jetzt alles rund um die Reinigungsprodukte und deren Anwendung.
Visit swiffer.deWe analyzed Swiffer.de page load time and found that the first response time was 90 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
swiffer.de performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value15.0 s
0/100
25%
Value17.6 s
0/100
10%
Value10,130 ms
0/100
30%
Value0.013
100/100
15%
Value28.8 s
0/100
10%
90 ms
111 ms
549 ms
953 ms
963 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Swiffer.de, 62% (29 requests) were made to For-me-online-de.secure.footprint.net and 11% (5 requests) were made to For-me-online.de. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source For-me-online-de.secure.footprint.net.
Page size can be reduced by 1.5 MB (67%)
2.2 MB
724.5 kB
In fact, the total size of Swiffer.de main page is 2.2 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. 65% of websites need less resources to load. CSS take 920.7 kB which makes up the majority of the site volume.
Potential reduce by 257.9 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 56.6 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 257.9 kB or 89% of the original size.
Potential reduce by 11.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. Swiffer images are well optimized though.
Potential reduce by 437.8 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 437.8 kB or 69% of the original size.
Potential reduce by 789.1 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. Swiffer.de needs all CSS files to be minified and compressed as it can save up to 789.1 kB or 86% of the original size.
Number of requests can be reduced by 11 (30%)
37
26
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Swiffer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
swiffer.de
90 ms
swiffer
111 ms
swiffer
549 ms
logoEverydayme.gif
953 ms
program-selector-de.jpg
963 ms
program-selector-vi.jpg
970 ms
PGShop.jpg
971 ms
BraunShop.jpg
972 ms
site-bg.jpg
984 ms
swiffer-header-logo.png
977 ms
swiffer-header-text-01.png
973 ms
swiffer-header-text-02.png
978 ms
swiffer-header-text-03.png
978 ms
swiffer-header-text-04.png
980 ms
swiffer-header-sterntext.png
981 ms
bg_navi.jpg
984 ms
bg_navi_active.jpg
985 ms
2-Box-Teaser-swiffer-starterset.jpg
1006 ms
swiffer-header-hgr-desktop.jpg
63 ms
swiffer-header-hgr-head.jpg
61 ms
arrow_03.png
52 ms
gqK4Oc4Us5g
97 ms
0Ac2IwZvGMc
113 ms
s1UCsLiaGkc
109 ms
global-min.js
1008 ms
tag.js
49 ms
2-Box-Teaser-ugc4.jpg
1064 ms
button-swiffer-ugc-140506.png
973 ms
transparent.png
972 ms
ravensburger.jpg
974 ms
ad_choice.jpg
982 ms
www-embed-player-vflfNyN_r.css
26 ms
www-embed-player.js
56 ms
base.js
168 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
53 ms
ad_status.js
61 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
112 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
113 ms
global-de-de.css
47 ms
transparent.png
178 ms
rockwell-cyrillic-std.woff
178 ms
rockwell-cyrillic-bold.woff
179 ms
icons.ttf
179 ms
frutiger-cyrillic-bold.woff
178 ms
frutiger-cyrillic-std.woff
179 ms
tag
161 ms
pollen-allergiker-visual-neu-2-size-2.jpg
32 ms
swiffer.de accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Links do not have a discernible name
swiffer.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
swiffer.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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Swiffer.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 Swiffer.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.
swiffer.de
Open Graph description is not detected on the main page of Swiffer. 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: