2.5 sec in total
315 ms
2 sec
148 ms
Welcome to alive.nl homepage info - get ready to check Alive best content right away, or after learning these important things about alive.nl
Welkom bij de Alive, Vitality for LifeAlle soorten Wellness produktenWij zijn al meer dan 25 jaar online!Bestellingen worden binnen 2 dagen geleverd, ligt aan de vervoersdienst.Wij
Visit alive.nlWe analyzed Alive.nl page load time and found that the first response time was 315 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
alive.nl performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value4.5 s
36/100
25%
Value8.3 s
19/100
10%
Value990 ms
27/100
30%
Value0.149
76/100
15%
Value12.9 s
13/100
10%
315 ms
756 ms
281 ms
306 ms
317 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Alive.nl, 96% (24 requests) were made to Shop.alive.nl. The less responsive or slowest element that took the longest time to load (840 ms) relates to the external source Shop.alive.nl.
Page size can be reduced by 69.6 kB (48%)
144.9 kB
75.3 kB
In fact, the total size of Alive.nl main page is 144.9 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. Only 5% of websites need less resources to load. Images take 127.3 kB which makes up the majority of the site volume.
Potential reduce by 147 B
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 147 B or 40% of the original size.
Potential reduce by 54.8 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, Alive needs image optimization as it can save up to 54.8 kB or 43% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 14.7 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. Alive.nl needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 85% of the original size.
We found no issues to fix!
24
24
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alive. According to our analytics all requests are already optimized.
alive.nl
315 ms
shop.alive.nl
756 ms
cataloge.css
281 ms
cb_17.gif
306 ms
left_fot.jpg
317 ms
search.jpg
331 ms
cart.jpg
326 ms
s_941.jpg
364 ms
s_1114.jpg
814 ms
s_923.jpg
502 ms
3__18_ms2.rvf_1.jpg
377 ms
3__18_ms2.rvf_2.jpg
379 ms
s_157.jpg
460 ms
s_1092.jpg
459 ms
s_232.jpg
840 ms
cent_fot.jpg
554 ms
fot_bg.jpg
587 ms
top_bg.jpg
443 ms
arrow.jpg
469 ms
left_cont.jpg
562 ms
left_top.jpg
699 ms
arrow1.gif
545 ms
buttons.jpg
642 ms
cent_cont.jpg
753 ms
cent_top.jpg
735 ms
alive.nl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
alive.nl 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
alive.nl 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
NL
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alive.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Alive.nl main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
alive.nl
Open Graph description is not detected on the main page of Alive. 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: