6.6 sec in total
994 ms
5.2 sec
457 ms
Welcome to e-liquide.com homepage info - get ready to check E Liquide best content for France right away, or after learning these important things about e-liquide.com
E-liquides direct laboratoire fabriquant français, 10 ml, 15 ml et 60 ml. DIY, arômes concentrés, nicotine et bases neutres.
Visit e-liquide.comWe analyzed E-liquide.com page load time and found that the first response time was 994 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
e-liquide.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value6.4 s
10/100
25%
Value4.0 s
80/100
10%
Value200 ms
89/100
30%
Value0.025
100/100
15%
Value6.3 s
61/100
10%
994 ms
325 ms
163 ms
439 ms
186 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 91% of them (80 requests) were addressed to the original E-liquide.com, 2% (2 requests) were made to Facebook.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Efvi.eu.
Page size can be reduced by 332.5 kB (19%)
1.8 MB
1.4 MB
In fact, the total size of E-liquide.com main page is 1.8 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 54.0 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 54.0 kB or 81% of the original size.
Potential reduce by 31.9 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. E Liquide images are well optimized though.
Potential reduce by 163.0 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 163.0 kB or 71% of the original size.
Potential reduce by 83.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. E-liquide.com needs all CSS files to be minified and compressed as it can save up to 83.7 kB or 83% of the original size.
Number of requests can be reduced by 33 (38%)
86
53
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Liquide. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
www.e-liquide.com
994 ms
v_69_07325fe505d4a1b59d2f307dcc61bb25_all.css
325 ms
tooltipster.css
163 ms
jquery-1.11.0.min.js
439 ms
jquery-migrate-1.2.1.min.js
186 ms
jquery.easing.js
191 ms
tools.js
297 ms
products-comparison.js
241 ms
blockfacebook.js
280 ms
categoriestopmenu.js
285 ms
jquery.ui.totop.min.js
332 ms
jquery.ui.totop.init.js
373 ms
ajax-cart.js
473 ms
jquery.scrollTo.js
395 ms
jquery.serialScroll.js
400 ms
jquery.bxslider.js
400 ms
jquery.autocomplete.js
468 ms
hoverIntent.js
493 ms
superfish-modified.js
479 ms
css
25 ms
tooltipster.js
479 ms
formstyle.js
519 ms
products_block.js
561 ms
cookie.js
563 ms
core.js
557 ms
we-support-white-180x60.png
3214 ms
body_bg.png
154 ms
page_bg.jpg
153 ms
header_bg.jpg
178 ms
logo.jpg
396 ms
cart.png
149 ms
button_blue.png
149 ms
kit-subox-mini-kangertech.jpg
176 ms
e-liquide-black-tobacco.jpg
399 ms
arome-louisiana.jpg
399 ms
kit-ego-one-mega-joyetech.jpg
215 ms
istick-tc-40w-2600-mah-eleaf.jpg
241 ms
subtank-nano-kangertech.jpg
260 ms
subtank-mini-kangertech.jpg
308 ms
kit-evod-mega-1900-mah-kangertech.jpg
321 ms
kit-ego-one-xl-joyetech.jpg
347 ms
clearomizer-atlantis-aspire.jpg
402 ms
arome-aqua-oriental.jpg
559 ms
clearomizer-nautilus-bvc-aspire.jpg
435 ms
e-liquide-mojito.jpg
591 ms
gold-and-black-blend.jpg
556 ms
gold-blend.jpg
586 ms
subzero-menthol.jpg
683 ms
tabac-gaulois.jpg
607 ms
menthe-glaciale.jpg
715 ms
route-66-blend.jpg
639 ms
e-liquide-menthol-blend.jpg
682 ms
e-liquide-energy.jpg
689 ms
western-blend.jpg
695 ms
desert-blend.jpg
717 ms
tobacco-blend.jpg
775 ms
batterie-stylish-650-mah-vision.jpg
776 ms
e-liquide-pg100-100-ml.jpg
788 ms
e-liquide-pg75vg25-100-ml.jpg
781 ms
batterie-ego-evod-1000mah.jpg
798 ms
FR_vertical_solution_PP.png
796 ms
footer_img_1.png
857 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
20 ms
all.js
69 ms
www.e-liquide.com
1164 ms
logo_payment.png
728 ms
topmenu_bg.jpg
725 ms
topmenu_bt.jpg
721 ms
home.png
709 ms
130 ms
arrows.png
788 ms
xd_arbiter.php
42 ms
xd_arbiter.php
44 ms
block_header_blue.jpg
750 ms
categories_block_bg.jpg
732 ms
block_header_grey.jpg
705 ms
button_green.png
685 ms
block_header_green.jpg
729 ms
footercustom_warning.jpg
697 ms
hazard_N.jpg
672 ms
hazard_T.jpg
670 ms
footercustom_bg.jpg
694 ms
social_fb.png
723 ms
social_twi.png
702 ms
social_rss.png
604 ms
editor_blocks_bg.jpg
605 ms
ui.totop.png
604 ms
ping
58 ms
e-liquide.com 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.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
e-liquide.com 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
e-liquide.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-liquide.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that E-liquide.com 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.
e-liquide.com
Open Graph description is not detected on the main page of E Liquide. 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: