2.8 sec in total
213 ms
1.9 sec
659 ms
Visit veeve.com now to see the best up-to-date Veeve content for United Kingdom and also check out these interesting facts you probably never knew about veeve.com
Discover Veeve's curated collection of luxury homes in London and Paris for short term rental. Elevate your city break with Veeve. Book now.
Visit veeve.comWe analyzed Veeve.com page load time and found that the first response time was 213 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
veeve.com performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value9.4 s
1/100
25%
Value6.7 s
36/100
10%
Value1,730 ms
11/100
30%
Value0.002
100/100
15%
Value20.0 s
2/100
10%
213 ms
25 ms
33 ms
21 ms
57 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 46% of them (32 requests) were addressed to the original Veeve.com, 23% (16 requests) were made to D34lwz5jiyj0c4.cloudfront.net and 7% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (972 ms) relates to the external source Api-prod.veeve.com.
Page size can be reduced by 1.2 MB (25%)
4.6 MB
3.5 MB
In fact, the total size of Veeve.com main page is 4.6 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. 65% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 69.6 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 69.6 kB or 82% of the original size.
Potential reduce by 45.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. Veeve images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 70% of the original size.
Number of requests can be reduced by 25 (40%)
63
38
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Veeve. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
veeve.com
213 ms
www.veeve.com
25 ms
www.veeve.com
33 ms
vendor-59fce6d8.css
21 ms
app-4ace5cbc.css
57 ms
vendor-225dcfde.js
79 ms
js
77 ms
app-56fa1045.js
56 ms
prum.min.js
434 ms
analytics.js
437 ms
fbevents.js
462 ms
all.js
304 ms
currencies.json
945 ms
tags.json
972 ms
suggestions.json
478 ms
humbingbird-sprite.png
42 ms
pattern.jpg
85 ms
logo-veeve.png
31 ms
futuralt-book-webfont.woff
40 ms
icons.svg
56 ms
icons.woff
56 ms
glyphicons-halflings-regular.woff
56 ms
61 ms
xd_arbiter.php
50 ms
beacon.gif
554 ms
xd_arbiter.php
15 ms
collect
286 ms
283 ms
pattern_bw_white.jpg
272 ms
locate
392 ms
common.js
303 ms
util.js
355 ms
controls.js
353 ms
places_impl.js
391 ms
host-page--15.jpg
502 ms
1800x1200_04-1.jpg
278 ms
1800x1200_12-1.jpg
263 ms
1800x1200_02-1.jpg
262 ms
img-become-a-host.jpg
255 ms
hubert-small.png
205 ms
logo-veeve.svg
206 ms
media-logos.svg
212 ms
grand-designs-big.png
206 ms
sunday-times-big.png
211 ms
the-guardian-big.png
219 ms
pierre.png
256 ms
ambra.png
399 ms
george.png
237 ms
jess.png
275 ms
tom.png
243 ms
sophie.png
254 ms
suggestions.json
246 ms
gbp.png
199 ms
usd.png
199 ms
eur.png
204 ms
aud.png
207 ms
cad.png
209 ms
cny.png
227 ms
dkk.png
227 ms
jpy.png
227 ms
nok.png
228 ms
nzd.png
361 ms
rub.png
360 ms
sek.png
360 ms
ga-audiences
179 ms
collect
127 ms
media-logos.svg
31 ms
grand-designs-big.png
23 ms
sunday-times-big.png
26 ms
the-guardian-big.png
26 ms
veeve.com 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
veeve.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
veeve.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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Veeve.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Veeve.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.
veeve.com
Open Graph description is not detected on the main page of Veeve. 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: