4.3 sec in total
239 ms
3.2 sec
844 ms
Welcome to vayava.es homepage info - get ready to check Vayava best content for Spain right away, or after learning these important things about vayava.es
Entra en Vayava y descubre los mejores precios en smartphones de marcas como Xiaomi, Meizu o Nubia y todo tipo de productos tecnológicos y gadgets. Somos tu tienda de referencia.
Visit vayava.esWe analyzed Vayava.es page load time and found that the first response time was 239 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.
vayava.es performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value10.9 s
0/100
25%
Value8.3 s
19/100
10%
Value1,060 ms
25/100
30%
Value0.267
46/100
15%
Value20.5 s
2/100
10%
239 ms
979 ms
126 ms
246 ms
329 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Vayava.es, 40% (28 requests) were made to Image1.vayava.es and 30% (21 requests) were made to Content1.vayava.es. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Image1.vayava.es.
Page size can be reduced by 588.2 kB (19%)
3.0 MB
2.4 MB
In fact, the total size of Vayava.es main page is 3.0 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 2.4 MB which makes up the majority of the site volume.
Potential reduce by 178.2 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 59.6 kB, which is 29% 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 178.2 kB or 85% of the original size.
Potential reduce by 130.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. Vayava images are well optimized though.
Potential reduce by 250.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 250.0 kB or 65% of the original size.
Potential reduce by 29.3 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. Vayava.es needs all CSS files to be minified and compressed as it can save up to 29.3 kB or 78% of the original size.
Number of requests can be reduced by 21 (31%)
68
47
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vayava. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
vayava.es
239 ms
www.vayava.es
979 ms
reset.css
126 ms
base.css
246 ms
jquery-1.7.1.min.js
329 ms
cookie.js
200 ms
sea.js
248 ms
index.css
459 ms
vyvFont.css
69 ms
html5.min.js
298 ms
0-201615105018xiaomi-2.png
297 ms
0-20156231736374.png
273 ms
0-2015624112516%E8%BF%90%E5%8A%A8%E5%92%8C%E6%88%B7%E5%A4%96.png
404 ms
0-20156241124561.png
600 ms
0-2015623175240%E8%BF%90%E5%8A%A8%E5%92%8C%E6%88%B7%E5%A4%96.png
685 ms
0-2015629956212.png
1449 ms
0-201562995547xiaomi.png
427 ms
0-20161615234tronsmart.png
424 ms
banner2016227121216mm.jpg
498 ms
banner201621715521%E5%8D%8E%E7%A1%95%E6%89%8B%E6%9C%BAzenfone-max-banner(3).jpg
526 ms
banner201625171745%E6%89%8B%E6%9C%BA%E6%B8%85%E4%BB%93banner.jpg
506 ms
banner201612211234%E6%89%8B%E8%A1%A8banner_%E5%89%AF%E6%9C%AC.jpg
588 ms
banner2016224133542X98-plus%E5%A4%A7banner(3).jpg
614 ms
banner20162515466ea.jpg
635 ms
toplogo.png
168 ms
Discount.png
42 ms
label1.png
43 ms
label8.png
171 ms
emailBanner.jpg
82 ms
index.js
59 ms
xyupngIco.png
280 ms
icoList.png
136 ms
analytics.js
36 ms
emailbt.png
99 ms
start.png
99 ms
lineEmail.png
98 ms
collect
28 ms
main.js
57 ms
doofinder-4.latest.min.js
26 ms
jquery.lazyload.min.js
141 ms
loading.gif
140 ms
20151205164710713yhpx6.jpg
142 ms
2016013015003430kzmvh6.jpg
189 ms
2016011818305413m86og6.jpg
156 ms
20160121164113vrh680y6.jpg
182 ms
20151121115143qu34dzp6.jpg
178 ms
201511301722566dj0t436.jpg
189 ms
201509241719372th5iy36.jpg
212 ms
20151222110927mtxpive6.jpg
224 ms
20160114153959zpehjdl6.jpg
271 ms
20150820125520ze64wsv6.jpg
222 ms
201601061450479rxq7sj6.jpg
271 ms
20160204113821r54q9x26.jpg
245 ms
201512311059245g4ke8b6.jpg
255 ms
201601141525438b7ifvx6.jpg
261 ms
sdk.js
33 ms
collect
4 ms
190 ms
xd_arbiter.php
69 ms
xd_arbiter.php
109 ms
a8111ae0f54de6cea669de7cae2b0dda.js
170 ms
like_box.php
111 ms
gPetWftPCXn.css
49 ms
brXCB1QvZVP.css
58 ms
_rx8naC75Dy.js
73 ms
b94UUzHjapV.js
112 ms
0wM5s1Khldu.js
109 ms
TTCre3391I0.js
110 ms
I6-MnjEovm5.js
14 ms
f6T91Deal_q.js
18 ms
vayava.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-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
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
Links do not have a discernible name
vayava.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
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
Page has valid source maps
vayava.es 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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vayava.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Vayava.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.
vayava.es
Open Graph description is not detected on the main page of Vayava. 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: