6.1 sec in total
107 ms
3.5 sec
2.4 sec
Click here to check amazing Vital Tracer content. Otherwise, check out these important facts you probably never knew about vitaltracer.com
VitalTracer’s products collects raw bio-signals and translates them into vital signs data such as blood pressure, SPO2, heart rate, and respiratory rate.
Visit vitaltracer.comWe analyzed Vitaltracer.com page load time and found that the first response time was 107 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
vitaltracer.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value22.0 s
0/100
25%
Value23.8 s
0/100
10%
Value20,590 ms
0/100
30%
Value1
2/100
15%
Value31.1 s
0/100
10%
107 ms
245 ms
24 ms
63 ms
50 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 73% of them (86 requests) were addressed to the original Vitaltracer.com, 27% (32 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Vitaltracer.com.
Page size can be reduced by 610.5 kB (8%)
7.3 MB
6.7 MB
In fact, the total size of Vitaltracer.com main page is 7.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. 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 6.9 MB which makes up the majority of the site volume.
Potential reduce by 149.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 149.5 kB or 88% of the original size.
Potential reduce by 402.9 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. Vital Tracer images are well optimized though.
Potential reduce by 6.8 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 6.8 kB or 12% of the original size.
Potential reduce by 51.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. Vitaltracer.com needs all CSS files to be minified and compressed as it can save up to 51.3 kB or 29% of the original size.
Number of requests can be reduced by 31 (37%)
83
52
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vital Tracer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
vitaltracer.com
107 ms
vitaltracer.com
245 ms
wc-blocks-vendors-style.css
24 ms
wc-blocks-style.css
63 ms
swiper.min.css
50 ms
light-box-styles.css
79 ms
woocommerce-layout.css
38 ms
woocommerce.css
52 ms
style.min.css
75 ms
style.min.css
78 ms
front.min.css
82 ms
style-static.min.css
87 ms
style.css
139 ms
et-ct-styles.css
80 ms
front.min.js
82 ms
et-core-unified-8.min.css
137 ms
email-decode.min.js
82 ms
jquery.min.js
233 ms
jquery-migrate.min.js
259 ms
swiper.min.js
252 ms
lazysizes.min.js
258 ms
jquery.blockUI.min.js
249 ms
add-to-cart.min.js
253 ms
js.cookie.min.js
254 ms
woocommerce.min.js
256 ms
jquery.cookie.min.js
261 ms
Cart.min.js
258 ms
scripts.min.js
264 ms
frontend-bundle.min.js
261 ms
frontend-bundle.min.js
262 ms
et-ct-scripts.js
257 ms
et-core-common.min.js
265 ms
jquery.fitvids.js
265 ms
sticky-elements.js
266 ms
site-logo.png
68 ms
shopping-cart.png
70 ms
6.png
879 ms
Favicon_VT.png
70 ms
1200625762895746.png
73 ms
1200625762895746-1.png
70 ms
blood-cells.png
73 ms
oxygen.png
75 ms
thermometer-1.png
155 ms
ppg-logo.png
76 ms
ecg.png
158 ms
cardiology.png
158 ms
foot.png
157 ms
elctron.png
321 ms
VT-Image-1.png
320 ms
VT-Image-10.png
319 ms
VT-Image-7.png
319 ms
VT-Image-5.png
317 ms
pxiEyp8kv8JHgFVrJJnedA.woff
307 ms
pxiEyp8kv8JHgFVrJJnedw.ttf
309 ms
pxiByp8kv8JHgFVrLGT9Z1JlEw.woff
865 ms
pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf
870 ms
pxiByp8kv8JHgFVrLDz8Z1JlEw.woff
867 ms
pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf
867 ms
pxiByp8kv8JHgFVrLFj_Z1JlEw.woff
869 ms
pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf
866 ms
pxiGyp8kv8JHgFVrLPTufntG.woff
869 ms
pxiGyp8kv8JHgFVrLPTufntF.ttf
924 ms
pxiByp8kv8JHgFVrLEj6Z1JlEw.woff
923 ms
pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf
922 ms
pxiByp8kv8JHgFVrLCz7Z1JlEw.woff
923 ms
pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf
923 ms
pxiByp8kv8JHgFVrLDD4Z1JlEw.woff
924 ms
pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf
927 ms
pxiByp8kv8JHgFVrLBT5Z1JlEw.woff
924 ms
pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf
927 ms
VT-Image-8.png
854 ms
VT-Image-3.png
833 ms
VT-Image-2.png
830 ms
VT-Image-4.png
829 ms
VT-Image-9.png
829 ms
VT-Image-6.png
902 ms
vt-featured-cpa.png
902 ms
vt-featured-city-news.png
898 ms
vt-featured-university-concordia.png
898 ms
7.png
993 ms
Mask-Group-110.png
898 ms
Concordia.jpg
904 ms
CDL.jpg
901 ms
Fondation-Montreal.jpg
901 ms
OttawaU.jpg
900 ms
McGill.jpg
899 ms
D3-nouveau.jpg
899 ms
Prompt.jpg
899 ms
Medtech.jpg
899 ms
Age-well.jpg
899 ms
Mitacs.jpg
898 ms
Create-best.jpg
898 ms
Front-row.jpg
900 ms
X1-accelerator.jpg
896 ms
Startup-en-demarrage.jpg
895 ms
Next-AI.jpg
889 ms
Fondation-McGill.jpg
885 ms
IRAP.jpg
884 ms
IRAP.png
883 ms
modules.ttf
990 ms
K2FifZFYk-dHSE0UPPuwQ7CrD94i-NCKm-U48M1wpRnF.woff
783 ms
K2FifZFYk-dHSE0UPPuwQ7CrD94i-NCKm-U48M1wpRnG.ttf
795 ms
Matrix-logo-RGB.png
730 ms
subscribe-loader.gif
800 ms
vitaltracer.com
1804 ms
woocommerce-smallscreen.css
9 ms
KFOmCnqEu92Fr1Mu7GxM.woff
259 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
268 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
259 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
268 ms
KFOlCnqEu92Fr1MmSU5fChc-.woff
280 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
281 ms
KFOkCnqEu92Fr1MmgVxGIzQ.woff
281 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
283 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
282 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
284 ms
KFOlCnqEu92Fr1MmYUtfChc-.woff
282 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
285 ms
vitaltracer.com accessibility score
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
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.
vitaltracer.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
vitaltracer.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
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vitaltracer.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 Vitaltracer.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.
vitaltracer.com
Open Graph data is detected on the main page of Vital Tracer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: