19.5 sec in total
528 ms
18.5 sec
537 ms
Welcome to very.com homepage info - get ready to check Very best content right away, or after learning these important things about very.com
Discover fashion, home, tech & more online with a choice of ways to pay and next day delivery with click & collect. Download our app for exclusive offers
Visit very.comWe analyzed Very.com page load time and found that the first response time was 528 ms and then it took 19 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
very.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value18.0 s
0/100
25%
Value28.7 s
0/100
10%
Value45,390 ms
0/100
30%
Value0
100/100
15%
Value60.0 s
0/100
10%
528 ms
314 ms
178 ms
594 ms
526 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Very.com, 8% (10 requests) were made to Googleads.g.doubleclick.net and 8% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Speedtrap.shopdirect.com.
Page size can be reduced by 1.6 MB (67%)
2.3 MB
750.9 kB
In fact, the total size of Very.com main page is 2.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. 60% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 532.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. 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 532.2 kB or 84% of the original size.
Potential reduce by 23.0 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. Very images are well optimized though.
Potential reduce by 995.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 995.3 kB or 73% of the original size.
Number of requests can be reduced by 84 (80%)
105
21
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Very. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and as a result speed up the page load time.
www.very.co.uk
528 ms
global_head.js
314 ms
sdgExp.min.js
178 ms
opentag-56535-278157.js
594 ms
homeCombine2.js
526 ms
new-slider.js
141 ms
smartserve-2290.js
427 ms
very-logo.png
159 ms
basket-grey.png
159 ms
stunt-promo.gif
361 ms
searchcloseicons.png
339 ms
take3-banner-960x100.png
338 ms
save-on-brands.jpg
339 ms
sprite-new.jpg
371 ms
loading.gif
170 ms
small-close-icon.png
325 ms
session.js
626 ms
JavascriptInsert.js
5238 ms
activityi;src=3987677;type=verys374;cat=veryh507;ord=1;num=7966965769883.245
425 ms
conversion_async.js
416 ms
fbds.js
413 ms
kenshoo.js
394 ms
d3e241322df1.js
596 ms
v1.js
578 ms
channel.js
519 ms
analytics.js
368 ms
ve-mid-season-hp-primary.jpg
498 ms
sfl.0.5.min.js
342 ms
3090.js
335 ms
bat.js
559 ms
d749fb98324e.js
302 ms
ec.js
135 ms
linkid.js
214 ms
372 ms
kid
441 ms
1062 ms
saved.png
64 ms
udash.min.js
587 ms
c.aspx
839 ms
iconSavedRetina.png
57 ms
activity;src=4869603;type=invmedia;cat=otnxqrzf;ord=1
200 ms
196 ms
collect
81 ms
collect
226 ms
b=25289500
81 ms
74 ms
133 ms
pixel.js
111 ms
smart.js
122 ms
ga-audiences
114 ms
1
223 ms
sync
430 ms
26975
318 ms
sync
463 ms
pixel
287 ms
pushFileAppendData.php
1095 ms
45 ms
noop
581 ms
noop
552 ms
lr.gif
492 ms
match
42 ms
t.js
180 ms
57 ms
activity;src=2345444;type=very_433;cat=homep236;ord=1
174 ms
lb
201 ms
s
309 ms
rmboom;rm=mythingsveryretarghpandcat;dc_seg=19736530;ord=1
348 ms
activityi;src=5182129;type=invmedia;cat=vtcq1ws1;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=0.7661978364922106
352 ms
n.js
513 ms
t
304 ms
tap.php
968 ms
tap.php
980 ms
368 ms
lr.gif
263 ms
pix.aspx
174 ms
js
65 ms
56 ms
t
1912 ms
pixel
56 ms
pixel
108 ms
sync
82 ms
match
70 ms
78 ms
tap.php
69 ms
sync
27 ms
80 ms
dc_match
1125 ms
pixel
101 ms
setgoogid.aspx
192 ms
fbnomatch.aspx
300 ms
match
281 ms
info.php
304 ms
939 ms
Pug
1195 ms
transparent.gif
1208 ms
tap.php
354 ms
rum
181 ms
401 ms
rum
53 ms
setgoogid.aspx
149 ms
setgoogid.aspx
181 ms
match
53 ms
mapuser
121 ms
info.php
242 ms
tap.php
369 ms
47 ms
rs
64 ms
rs
69 ms
98 ms
rs
752 ms
123 ms
69 ms
109 ms
109 ms
104 ms
145 ms
cm
98 ms
42 ms
pixtrk.aspx
153 ms
pixel
61 ms
homepage.jpg
123 ms
shopdirect_very_pink_desktop.png
52 ms
66 ms
tv-cta.jpg
41 ms
new-in-womens.jpg
39 ms
homeSprite.png
77 ms
adrum-ext.dc7135e81648fca28b1e62b72cf2e576.js
47 ms
very.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.
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 [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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
very.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
very.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Very.com 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 Very.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.
very.com
Open Graph data is detected on the main page of Very. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: