1.1 sec in total
145 ms
584 ms
413 ms
Welcome to vlex.es homepage info - get ready to check VLex best content for Spain right away, or after learning these important things about vlex.es
La plataforma de inteligencia jurídica que multiplica tu inteligencia legal
Visit vlex.esWe analyzed Vlex.es page load time and found that the first response time was 145 ms and then it took 997 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
vlex.es performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value5.1 s
25/100
25%
Value7.5 s
26/100
10%
Value3,690 ms
1/100
30%
Value0
100/100
15%
Value21.4 s
1/100
10%
145 ms
5 ms
19 ms
4 ms
38 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 90% of them (43 requests) were addressed to the original Vlex.es, 4% (2 requests) were made to Chtatic.appspot.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (181 ms) relates to the external source Chtatic.appspot.com.
Page size can be reduced by 617.2 kB (48%)
1.3 MB
678.2 kB
In fact, the total size of Vlex.es main page is 1.3 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. 50% of websites need less resources to load. Images take 539.7 kB which makes up the majority of the site volume.
Potential reduce by 82.5 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 23.2 kB, which is 24% 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 82.5 kB or 85% of the original size.
Potential reduce by 54.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. VLex images are well optimized though.
Potential reduce by 248.3 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 248.3 kB or 65% of the original size.
Potential reduce by 231.9 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. Vlex.es needs all CSS files to be minified and compressed as it can save up to 231.9 kB or 83% of the original size.
Number of requests can be reduced by 9 (20%)
44
35
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VLex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
vlex.es
145 ms
ccm.base.css
5 ms
jquery.js
19 ms
ccm.base.js
4 ms
cms-min.css
38 ms
cms-min.js
15 ms
snapabug.js
91 ms
logo.png
5 ms
mini-logo.png
6 ms
promo_login.png
7 ms
google.png
7 ms
facebook.png
6 ms
twitter.png
7 ms
linkedin.png
7 ms
allen-overy.png
7 ms
jones-day.png
9 ms
banesto.png
7 ms
bbva.png
7 ms
backermackenzie.png
8 ms
uni_ve_2.png
10 ms
uni_vg_2.png
9 ms
pub_ve_2.png
17 ms
pub_vg_2.png
17 ms
emp_ve_2.png
17 ms
emp_ps_2.png
17 ms
MHernandez.png
24 ms
test_1.png
15 ms
logofooter.png
21 ms
enisa_small.jpg
21 ms
credit-cards.png
22 ms
thawte-logo.png
23 ms
help_right_es.png
181 ms
bg_noise-2.png
152 ms
ga.js
112 ms
bg_net_1.png
13 ms
bg_azul.jpg
14 ms
bg_features.png
13 ms
bg_tab_arrow.png
13 ms
promo_global.png
45 ms
promo_esp.png
41 ms
promo_mercantil.png
42 ms
pro_ve_2.png
42 ms
pro_ppc_2.png
43 ms
blank.gif
12 ms
titilliumweb-regular-webfont.woff
42 ms
vLex.woff
44 ms
titilliumweb-semibold-webfont.woff
43 ms
__utm.gif
49 ms
vlex.es 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
ARIA input fields do not have accessible names
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
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.
vlex.es 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
Browser errors were logged to the console
vlex.es SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vlex.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Vlex.es 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.
vlex.es
Open Graph description is not detected on the main page of VLex. 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: