Tools & Wizards About Us
cortext.imprivata.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

cortext.imprivata.com

Imprivata Cortext® - Sign In

Page Load Speed

68 ms in total

First Response

12 ms

Resources Loaded

56 ms

Page Rendered

0 ms

cortext.imprivata.com screenshot

About Website

Visit cortext.imprivata.com now to see the best up-to-date Cortext Imprivata content for United States and also check out these interesting facts you probably never knew about cortext.imprivata.com

Visit cortext.imprivata.com

Key Findings

We analyzed Cortext.imprivata.com page load time and found that the first response time was 12 ms and then it took 56 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

cortext.imprivata.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

cortext.imprivata.com

12 ms

cortext.imprivata.com

18 ms

jquery-ui-1.8.5.css

3 ms

messagingweb.css

5 ms

browserdetect.js

10 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that all of those requests were addressed to Cortext.imprivata.com and no external sources were called. The less responsive or slowest element that took the longest time to load (18 ms) belongs to the original domain Cortext.imprivata.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 189.5 kB (79%)

Content Size

239.1 kB

After Optimization

49.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Cortext.imprivata.com main page is 239.1 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. 25% of websites need less resources to load. CSS take 157.5 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 703 B

  • Original 1.1 kB
  • After minification 794 B
  • After compression 354 B

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. This page needs HTML code to be minified as it can gain 263 B, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 703 B or 67% of the original size.

JavaScript Optimization

-72%

Potential reduce by 57.9 kB

  • Original 80.5 kB
  • After minification 67.7 kB
  • After compression 22.6 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 57.9 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 130.9 kB

  • Original 157.5 kB
  • After minification 120.4 kB
  • After compression 26.6 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. Cortext.imprivata.com needs all CSS files to be minified and compressed as it can save up to 130.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (93%)

Requests Now

28

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cortext Imprivata. 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 20 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

cortext.imprivata.com

cortext.imprivata.com

12 ms

cortext.imprivata.com

cortext.imprivata.com

18 ms

jquery-ui-1.8.5.css

jquery-ui-1.8.5.css

3 ms

messagingweb.css

messagingweb.css

5 ms

browserdetect.js

browserdetect.js

10 ms

config.js

config.js

9 ms

underscore.js

underscore.js

11 ms

messagingweb.nocache.js

messagingweb.nocache.js

10 ms

jquery.maskedinput.js

jquery.maskedinput.js

11 ms

jquery.linkify.js

jquery.linkify.js

11 ms

jstz-1.0.4.min.js

jstz-1.0.4.min.js

11 ms

qrcode.js

qrcode.js

12 ms

base-web.css

base-web.css

9 ms

login.css

login.css

11 ms

header.css

header.css

11 ms

menu.css

menu.css

12 ms

conversation.css

conversation.css

10 ms

conversation-cell.css

conversation-cell.css

13 ms

lists.css

lists.css

14 ms

accountSetting.css

accountSetting.css

14 ms

dialog.css

dialog.css

16 ms

pagination.css

pagination.css

16 ms

message-details.css

message-details.css

17 ms

date-picker.css

date-picker.css

14 ms

cortext-2.0.0.css

cortext-2.0.0.css

15 ms

utilities.css

utilities.css

4 ms

inbox.css

inbox.css

3 ms

layout.css

layout.css

4 ms

contact-info.css

contact-info.css

5 ms

common.css

common.css

5 ms

Accessibility Review

cortext.imprivata.com accessibility score

64

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

cortext.imprivata.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

cortext.imprivata.com SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cortext.imprivata.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cortext.imprivata.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.

Social Sharing Optimization

cortext.imprivata.com

Open Graph description is not detected on the main page of Cortext Imprivata. 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: