8.8 sec in total
175 ms
7.7 sec
955 ms
Visit veeve.fr now to see the best up-to-date Veeve content and also check out these interesting facts you probably never knew about veeve.fr
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.frWe analyzed Veeve.fr page load time and found that the first response time was 175 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
veeve.fr performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value11.2 s
0/100
25%
Value16.9 s
0/100
10%
Value39,120 ms
0/100
30%
Value0.525
14/100
15%
Value51.6 s
0/100
10%
175 ms
530 ms
139 ms
170 ms
424 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Veeve.fr, 52% (62 requests) were made to Veeve.com and 14% (17 requests) were made to D1yky9nbw2vwym.cloudfront.net. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Veeve.com.
Page size can be reduced by 559.8 kB (32%)
1.8 MB
1.2 MB
In fact, the total size of Veeve.fr 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 906.3 kB which makes up the majority of the site volume.
Potential reduce by 287.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. 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 287.5 kB or 86% of the original size.
Potential reduce by 2.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. Veeve images are well optimized though.
Potential reduce by 29.5 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 29.5 kB or 13% of the original size.
Potential reduce by 240.1 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. Veeve.fr needs all CSS files to be minified and compressed as it can save up to 240.1 kB or 84% of the original size.
Number of requests can be reduced by 81 (82%)
99
18
The browser has sent 99 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 50 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
veeve.fr
175 ms
530 ms
tp.widget.bootstrap.min.js
139 ms
jquery.min.js
170 ms
jquery-ui.min.js
424 ms
js
498 ms
script.min.js
407 ms
flickity.min.js
618 ms
moment.min.js
644 ms
popper.min.js
618 ms
bootstrap.min.js
1273 ms
select2.min.js
1271 ms
t-datepicker.min.js
1077 ms
wow-737fb47a92905293560e38e584047e50.js
1074 ms
daterangepicker.min.js
1074 ms
lightslider-73db40c487c992860a2145c8cf977a7e.js
1073 ms
jquery.simplePagination-d8ab4aac2774a5f6769313f95ebc2f4a.js
1272 ms
olark-7848d34bd3c49e4f2edc05aa85f18b34.js
1273 ms
pagescript-da64a9fca56251ad049cd1fac84206d7.js
1276 ms
elementorFormScripts-85dc48404184ff22cd33d26e758f2af8.js
1277 ms
smush-lazy-load.min.js
1276 ms
intlTelInput.min.js
1276 ms
script.min.js
1282 ms
imagesloaded.min.js
1278 ms
make-column-clickable-0e52c6139d187c9f4a790781e41b06c4.js
1278 ms
webpack.runtime.min.js
1279 ms
frontend-modules.min.js
1282 ms
waypoints.min.js
1282 ms
core.min.js
1283 ms
swiper.min.js
1291 ms
share-link.min.js
1283 ms
dialog.min.js
1284 ms
frontend.min.js
1284 ms
app-5cbd5b4ddc7ec6eddc0d03933b8b552b.js
1286 ms
webpack-pro.runtime.min.js
1288 ms
regenerator-runtime.min.js
1287 ms
wp-polyfill.min.js
1289 ms
hooks.min.js
1289 ms
i18n.min.js
1290 ms
frontend.min.js
1290 ms
preloaded-elements-handlers.min.js
1291 ms
9334202.js
394 ms
preloaded-modules.min.js
1273 ms
gtm.js
1065 ms
arrow_dn-sm.svg
550 ms
menu-icon.svg
513 ms
veevelogo.svg
639 ms
phone.svg
903 ms
login.svg
855 ms
aleart-close.svg
857 ms
veeve_monogram.svg
906 ms
linkedin.svg
935 ms
pinterest.svg
944 ms
facebook.svg
954 ms
instagram.svg
951 ms
twitter.svg
946 ms
ico_newsletter.svg
955 ms
spe2ckm.css
932 ms
jquery-ui.css
314 ms
bootstrap.min.css
495 ms
bootstrap-icons.css
590 ms
css
585 ms
a0838d089a3955a24167d114e043d25c.css
991 ms
gen_204
153 ms
custom1.css
689 ms
post-3365.css
697 ms
post-2788.css
711 ms
post-1730.css
288 ms
post-1727.css
314 ms
post-1174.css
444 ms
post-836.css
447 ms
p.css
1019 ms
post-832.css
1033 ms
post-826.css
1017 ms
post-809.css
1004 ms
post-796.css
1053 ms
post-789.css
1039 ms
jquery.sticky.min.js
1051 ms
veeve_monogram.svg
2435 ms
livechat.svg
2355 ms
call.svg
2330 ms
arx7bqy.css
1038 ms
KFOmCnqEu92Fr1Mu4mxM.woff
1286 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
1359 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
2132 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
2221 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
2221 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
2221 ms
KFOkCnqEu92Fr1Mu51xIIzQ.woff
2221 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff
2221 ms
KFOjCnqEu92Fr1Mu51TjASc6CsI.woff
2220 ms
KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff
2376 ms
KFOjCnqEu92Fr1Mu51TzBic6CsI.woff
2375 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff
2375 ms
bootstrap-icons.woff
629 ms
Homepage-Images-test.jpg
1277 ms
doublecote.png
1396 ms
p.css
1269 ms
analytics.js
2026 ms
bat.js
2024 ms
d
515 ms
d
918 ms
3AA02A_1_0.woff
514 ms
3AA02A_3_0.woff
513 ms
eicons.woff
512 ms
3AA02A_0_0.woff
512 ms
Rippled.jpg
662 ms
Paris-loft.jpg
731 ms
October-half-term.jpg
1084 ms
9334202.js
1087 ms
fb.js
1088 ms
9334202.js
1085 ms
arrow-small.png
285 ms
loc.svg
251 ms
collect
44 ms
collect
39 ms
ga-audiences
51 ms
Homepage-Images-2020.02.10-6-1.jpg
7 ms
common.js
21 ms
util.js
13 ms
veeve.fr 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-*] 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.fr 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.fr 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
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Veeve.fr 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 Veeve.fr main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
veeve.fr
Open Graph data is detected on the main page of Veeve. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: