2 sec in total
155 ms
1.6 sec
271 ms
Welcome to vanish.no homepage info - get ready to check Vanish best content right away, or after learning these important things about vanish.no
Velkommen til nettstedet for Vanish NO. Her kan du finne informasjon om Vanish-produkter, tips om flekkfjerning sammen med videoer som viser hvordan Vanish virker.
Visit vanish.noWe analyzed Vanish.no page load time and found that the first response time was 155 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
vanish.no performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value10.8 s
0/100
25%
Value7.1 s
31/100
10%
Value630 ms
48/100
30%
Value0.795
5/100
15%
Value13.8 s
10/100
10%
155 ms
488 ms
284 ms
279 ms
369 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 84% of them (26 requests) were addressed to the original Vanish.no, 6% (2 requests) were made to Cdn.cookielaw.org and 3% (1 request) were made to Footer.digital-rb.com. The less responsive or slowest element that took the longest time to load (745 ms) belongs to the original domain Vanish.no.
Page size can be reduced by 155.3 kB (20%)
794.4 kB
639.2 kB
In fact, the total size of Vanish.no main page is 794.4 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. 35% of websites need less resources to load. Images take 688.8 kB which makes up the majority of the site volume.
Potential reduce by 71.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 13.0 kB, which is 16% 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 71.4 kB or 87% of the original size.
Potential reduce by 77.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. Obviously, Vanish needs image optimization as it can save up to 77.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 5.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 5.7 kB or 27% of the original size.
Potential reduce by 713 B
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. Vanish.no needs all CSS files to be minified and compressed as it can save up to 713 B or 33% of the original size.
Number of requests can be reduced by 12 (46%)
26
14
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vanish. 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 from 7 to 1 for CSS and as a result speed up the page load time.
vanish.no
155 ms
www.vanish.no
488 ms
284 ms
279 ms
369 ms
rb-footer.min.css
333 ms
wapp.css
277 ms
cookie.css
277 ms
bootstrap-multiselect.css
278 ms
745 ms
555 ms
556 ms
bootstrap-multiselect.js
437 ms
p.css
48 ms
gtm.js
94 ms
vanish-orion.png
459 ms
Norway.png
131 ms
3022446_rb_vanish_oxiaction_front.png
136 ms
8059845_rb_vanish_oxiaction_liquid_front.png
231 ms
8157238_rb_vanish_pre-treater_spray_font_dk-no.png
231 ms
8157877_rb_vanish_carpetcare_spray_dk-no.png
251 ms
hd_transparent_picture.png
253 ms
rainbow.png
324 ms
latte-cappuccino-mocha-how-to-beat-coffee-stains.jpg
332 ms
vanish_oxiaction-green0pc_440g.png
456 ms
30-seconds.png
457 ms
logo__small__new.png
506 ms
fontawesome-webfont.woff
483 ms
glyphicons-halflings-regular.woff
437 ms
otSDKStub.js
35 ms
c4b00b05-23f9-4464-9207-fbe0cf3a5c02.json
24 ms
vanish.no 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
vanish.no 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
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
vanish.no 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
EN
NN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vanish.no can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed language. Our system also found out that Vanish.no 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.
vanish.no
Open Graph data is detected on the main page of Vanish. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: