4.8 sec in total
142 ms
4 sec
612 ms
Visit quentry.com now to see the best up-to-date Quentry content and also check out these interesting facts you probably never knew about quentry.com
A specialized exchange platform for healthcare professionals: Medical image sharing, viewing and analysis and secure cloud storage of patient data.
Visit quentry.comWe analyzed Quentry.com page load time and found that the first response time was 142 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
quentry.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value12.6 s
0/100
25%
Value7.8 s
23/100
10%
Value8,640 ms
0/100
30%
Value0.127
82/100
15%
Value24.8 s
0/100
10%
142 ms
285 ms
230 ms
81 ms
109 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Quentry.com, 93% (100 requests) were made to Brainlab.com and 2% (2 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (872 ms) relates to the external source Brainlab.com.
Page size can be reduced by 192.6 kB (24%)
801.8 kB
609.2 kB
In fact, the total size of Quentry.com main page is 801.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 299.9 kB which makes up the majority of the site volume.
Potential reduce by 190.8 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 190.8 kB or 83% of the original size.
Potential reduce by 0 B
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. Quentry images are well optimized though.
Potential reduce by 927 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 870 B
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. Quentry.com has all CSS files already compressed.
Number of requests can be reduced by 95 (93%)
102
7
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Quentry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
www.quentry.com
142 ms
www.quentry.com
285 ms
230 ms
gtm.js
81 ms
usercentric-styles.css
109 ms
contact-form-7.css
194 ms
style.min.css
300 ms
classic-themes.min.css
343 ms
styles.css
350 ms
styles.css
344 ms
magnific-popup.css
344 ms
styles.min.css
348 ms
cf7mls.css
387 ms
progress_bar.css
432 ms
animate.min.css
434 ms
base-imports.css
529 ms
page-onepager-quentry-text-video-two-columns.css
504 ms
page-onepager-quentry-cloud-services.css
439 ms
page-onepager-quentry-cloud-services-benefits.css
472 ms
page-onepager-quentry-cloud-services-hero-content.css
590 ms
page-onepager-quentry-cloud-services-solutions-tabbed.css
524 ms
page-onepager-quentry-cloud-services-nav-anchor.css
545 ms
page-onepager-quentry-cloud-services-table-content-two-columns.css
625 ms
technical-info-and-contact-teaser.css
595 ms
swiper.min.css
615 ms
slick.css
618 ms
slick-theme.css
620 ms
slick-center-mode-custom.css
679 ms
base-imports-dynamic-hotspot.css
690 ms
twitter-typeahead.css
706 ms
style.css
713 ms
loader.js
25 ms
uc-block.bundle.js
35 ms
jquery.min.js
736 ms
jquery-migrate.min.js
725 ms
language-cookie.js
841 ms
jquery.magnific-popup.min.js
843 ms
wpmp.js
845 ms
email-decode.min.js
842 ms
contact-form-7.js
843 ms
index.js
844 ms
jquery-ui.min.css
872 ms
jquery-ui.theme.min.css
784 ms
intlTelInput.min.css
701 ms
video-js.css
598 ms
video-js.css
553 ms
index.js
581 ms
cf7mls.js
619 ms
svg-click-handler.js
790 ms
solutions.js
636 ms
stickyfill.js
597 ms
init-stickyfill.js
555 ms
lodash.min.js
595 ms
nav-anchor-quentry.js
700 ms
datalayer-tracking.js
665 ms
a11y.js
635 ms
smooth-scroll.js
614 ms
bootstrap.js
604 ms
carousel-with-tabbed-navigation.js
604 ms
video.js
586 ms
slick.min.js
581 ms
swiper.min.js
578 ms
swiper-slider-init.js
597 ms
slick-slider-init.js
607 ms
drawer.js
615 ms
storage.js
568 ms
typeahead.bundle.js
583 ms
solr.js
579 ms
bundle.js
10 ms
aos.js
583 ms
init.js
591 ms
index.js
490 ms
accordion.js
493 ms
table.js
518 ms
carousel-icons-captions.js
530 ms
carousel-accordion.js
552 ms
card-slider.js
560 ms
index.js
584 ms
scroll-slider.js
539 ms
index.js
569 ms
show-more.js
579 ms
tabs.js
601 ms
helpers.js
606 ms
scripts.js
601 ms
navbar.js
573 ms
navbar-search.js
565 ms
banner.js
577 ms
contact-sidebar.js
598 ms
core.min.js
557 ms
datepicker.min.js
487 ms
intlTelInput.min.js
493 ms
callback-datepicker.js
500 ms
video.min.js
580 ms
en.js
529 ms
Youtube.min.js
545 ms
youtube-parser.js
555 ms
video.js
599 ms
lazyload.min.js
598 ms
BrainlabNowW05-Regular.woff
739 ms
BrainlabNowW05-Medium.woff
606 ms
BrainlabNowW05-Bold.woff
628 ms
iframe_api
90 ms
intel_logo.png
121 ms
hipaa_logo.png
121 ms
quentry-medical-data-exchange-1024x533.jpg
122 ms
HTML_Viewer_Colorful-1024x533.jpg
208 ms
Quentry_Analytics_Dashboard_IIa-1024x533.jpg
246 ms
www-widgetapi.js
8 ms
quentry.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
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
quentry.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Quentry.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 Quentry.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.
quentry.com
Open Graph data is detected on the main page of Quentry. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: