2.3 sec in total
76 ms
990 ms
1.2 sec
Click here to check amazing Veevr content for Italy. Otherwise, check out these important facts you probably never knew about veevr.com
Visit veevr.comWe analyzed Veevr.com page load time and found that the first response time was 76 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
veevr.com performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value3.3 s
70/100
25%
Value3.3 s
91/100
10%
Value1,670 ms
11/100
30%
Value0
100/100
15%
Value9.3 s
31/100
10%
76 ms
76 ms
88 ms
60 ms
77 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 13% of them (7 requests) were addressed to the original Veevr.com, 45% (25 requests) were made to Img.veevr.com and 9% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (616 ms) relates to the external source Img.veevr.com.
Page size can be reduced by 412.5 kB (13%)
3.3 MB
2.9 MB
In fact, the total size of Veevr.com main page is 3.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. 65% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 49.4 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 49.4 kB or 82% of the original size.
Potential reduce by 83.4 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. Veevr images are well optimized though.
Potential reduce by 168.4 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 168.4 kB or 56% of the original size.
Potential reduce by 111.2 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. Veevr.com needs all CSS files to be minified and compressed as it can save up to 111.2 kB or 83% of the original size.
Number of requests can be reduced by 18 (36%)
50
32
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Veevr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
veevr.com
76 ms
css
76 ms
css
88 ms
bootstrap.min.css
60 ms
base.css
77 ms
api.js
69 ms
jquery.min.js
95 ms
raven.min.js
140 ms
status.js
189 ms
bootstrap.min.js
67 ms
base.js
77 ms
analytics.js
72 ms
recaptcha__de.js
151 ms
thumbnail.png
80 ms
logo.png
81 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
126 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
160 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
160 ms
collect
63 ms
TSDaXhyJuDJ-NBU0popSWA.ttf
154 ms
347576b31d.jpg
195 ms
192 ms
green-gobbler.png
87 ms
347556d7df.jpg
160 ms
3475556cea.jpg
177 ms
347554052b.jpg
164 ms
347553edb4.jpg
161 ms
346239632c.jpg
165 ms
346228a080.jpg
164 ms
3462189ce4.jpg
166 ms
3462043d5a.jpg
167 ms
344751cca8.jpg
168 ms
344750a023.jpg
172 ms
3447494bbb.jpg
172 ms
344748ae59.jpg
177 ms
3447462777.jpg
170 ms
3447453d19.jpg
175 ms
344744bb03.jpg
176 ms
344620d797.jpg
187 ms
3446198e7c.jpg
616 ms
344617aea3.jpg
614 ms
344616cc04.jpg
180 ms
3446158f75.jpg
185 ms
344614dd56.jpg
181 ms
344613af63.jpg
186 ms
34461211e0.jpg
604 ms
344611f50f.jpg
614 ms
collect
140 ms
fallback
72 ms
fallback__ltr.css
35 ms
payload
46 ms
css
18 ms
logo_48.png
14 ms
refresh.png
18 ms
audio.png
30 ms
fine-uploader.min.css
426 ms
veevr.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
veevr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
veevr.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Veevr.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Veevr.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.
veevr.com
Open Graph description is not detected on the main page of Veevr. 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: