9.3 sec in total
2 sec
6.7 sec
567 ms
Welcome to cognetivity.com homepage info - get ready to check Cognetivity best content right away, or after learning these important things about cognetivity.com
Whether you are a patient or a professional, discover how our technology saves lives! Give your brain the attention it deserves today!
Visit cognetivity.comWe analyzed Cognetivity.com page load time and found that the first response time was 2 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
cognetivity.com performance score
name
value
score
weighting
Value12.8 s
0/100
10%
Value14.0 s
0/100
25%
Value26.0 s
0/100
10%
Value9,380 ms
0/100
30%
Value0.019
100/100
15%
Value39.5 s
0/100
10%
1963 ms
160 ms
46 ms
415 ms
302 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 86% of them (91 requests) were addressed to the original Cognetivity.com, 4% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Cognetivity.com.
Page size can be reduced by 2.5 MB (69%)
3.6 MB
1.1 MB
In fact, the total size of Cognetivity.com main page is 3.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. CSS take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 216.3 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 216.3 kB or 87% of the original size.
Potential reduce by 18.2 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. Cognetivity images are well optimized though.
Potential reduce by 937.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 937.5 kB or 78% of the original size.
Potential reduce by 1.3 MB
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. Cognetivity.com needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 88% of the original size.
Number of requests can be reduced by 63 (65%)
97
34
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cognetivity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
cognetivity.com
1963 ms
622638d0a4c330001a26383f
160 ms
pep.js
46 ms
style.min.css
415 ms
embed-public.min.css
302 ms
cookie-law-info-public.css
302 ms
cookie-law-info-gdpr.css
446 ms
style.css
424 ms
style.css
321 ms
style.css
861 ms
owl.carousel.min.css
413 ms
select2.min.css
54 ms
lity.min.css
441 ms
font-awesome-legacy.min.css
674 ms
grid-system.css
625 ms
style.css
1201 ms
element-highlighted-text.css
577 ms
element-tabbed-section.css
644 ms
element-clients.css
701 ms
css
55 ms
responsive.css
874 ms
flickity.css
878 ms
skin-material.css
921 ms
menu-dynamic.css
814 ms
js_composer.min.css
1068 ms
salient-dynamic-styles.css
1188 ms
style.css
1147 ms
jquery.min.js
1100 ms
jquery-migrate.min.js
1032 ms
cookie-law-info-public.js
1162 ms
owl.carousel.min.js
1257 ms
lity.min.js
1256 ms
scripts.js
1276 ms
js
80 ms
v2.js
62 ms
jquery.fancybox.css
1244 ms
core.css
1297 ms
slide-out-right-material.css
1244 ms
pdfobject.min.js
1245 ms
embed-public.min.js
1249 ms
app.js
1323 ms
salient-social.js
1298 ms
select2.min.js
13 ms
jquery.easing.js
1483 ms
jquery.mousewheel.js
1295 ms
priority.js
1324 ms
transit.js
1305 ms
waypoints.js
1214 ms
imagesLoaded.min.js
1207 ms
hoverintent.js
1201 ms
jquery.fancybox.min.js
1284 ms
anime.js
1281 ms
flickity.min.js
1386 ms
superfish.js
1095 ms
init.js
1760 ms
touchswipe.min.js
1048 ms
js_composer_front.min.js
1163 ms
ai_secondary-colour.svg
583 ms
Frame.svg
580 ms
Frame1.svg
577 ms
Frame2.svg
664 ms
clay-ipad-pro-12-9-in-mockup-landscape-front-view-31.png
852 ms
Powered-by-The-ICA.svg
688 ms
clay-ipad-pro-12-9-in-mockup-landscape-front-view-4.png
976 ms
Faster.svg
778 ms
Sensitivity-and-Accuracy.svg
800 ms
Accessibility.svg
814 ms
image-39.svg
935 ms
logos_bbc.svg
903 ms
Moneyweek-Logo-Red-logo.jpeg
1258 ms
WSJ-Logo-e1633420127422.jpeg
970 ms
image-42.svg
997 ms
Press-release-thumbnail-large@2x-1.png
1004 ms
frontiers.png
1031 ms
Logos-8.png
1033 ms
js
68 ms
analytics.js
60 ms
Logos-9.png
1155 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
199 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
226 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
232 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
230 ms
AvertaStd-Regular.otf
1154 ms
AvertaStd-Light.otf
1299 ms
collect
65 ms
AvertaStd-Semibold.otf
956 ms
Logos-10.png
955 ms
fontawesome-webfont.svg
1715 ms
ISO-13485-PNG-1-e1675069516623.png
1106 ms
Logos-12.png
1107 ms
ARUK_Horizontal_Logo-web-01-e1674920958698.jpeg
1107 ms
MSAD_Insurance_Group_logo.svg-e1674920981605.png
1107 ms
limage-3714-457-photo-e1674921013762.png
1105 ms
DPUK-Logo-e1674921025227.jpeg
1009 ms
menu-icon.svg
1082 ms
close-icon.svg
1082 ms
menu-arrow.svg
1082 ms
19883486.js
144 ms
arrow_forward_black_24dp-3.png
944 ms
cta-arrow.svg
966 ms
ico-settings.svg
982 ms
quote-b.svg
968 ms
quote.svg
938 ms
arrow_forward.svg
115 ms
arrow_next.svg
114 ms
fontawesome-webfont.woff
210 ms
cognetivity.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-*] attributes do not match their roles
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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.
cognetivity.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
cognetivity.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cognetivity.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 Cognetivity.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.
cognetivity.com
Open Graph description is not detected on the main page of Cognetivity. 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: