Tools & Wizards About Us
annalise.ai screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

annalise.ai

Revolutionary AI in Medical Imaging - Annalise.ai

Page Load Speed

15 sec in total

First Response

1.1 sec

Resources Loaded

11.9 sec

Page Rendered

2 sec

annalise.ai screenshot

About Website

Visit annalise.ai now to see the best up-to-date Annalise content and also check out these interesting facts you probably never knew about annalise.ai

Comprehensive, clinician-friendly medical imaging AI solutions to aid diagnostic confidence, speed and patient outcomes. Robustly tested, easy to use.

Visit annalise.ai

Key Findings

We analyzed Annalise.ai page load time and found that the first response time was 1.1 sec and then it took 13.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

annalise.ai performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value1,640 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value1.009

2/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

annalise.ai

1110 ms

annalise.ai

60 ms

script.js

32 ms

styles.css

642 ms

wpcf7-redirect-frontend.min.css

643 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 91% of them (73 requests) were addressed to the original Annalise.ai, 5% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Cdn-cookieyes.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Annalise.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 507.4 kB (16%)

Content Size

3.1 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Annalise.ai main page is 3.1 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. 50% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 234.4 kB

  • Original 298.6 kB
  • After minification 293.3 kB
  • After compression 64.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 234.4 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 273.0 kB

  • Original 2.8 MB
  • After minification 2.5 MB

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. Annalise images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 33.8 kB
  • After minification 33.8 kB
  • After compression 33.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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

70

After Optimization

52

  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Annalise. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

annalise.ai

annalise.ai

1110 ms

annalise.ai

annalise.ai

60 ms

script.js

script.js

32 ms

styles.css

styles.css

642 ms

wpcf7-redirect-frontend.min.css

wpcf7-redirect-frontend.min.css

643 ms

css

css

72 ms

style.min.css

style.min.css

1193 ms

style.css

style.css

1223 ms

jquery.min.js

jquery.min.js

975 ms

style-custom.css

style-custom.css

762 ms

index.js

index.js

1278 ms

index.js

index.js

1278 ms

frontend_full.js

frontend_full.js

1399 ms

wpcf7r-fe.js

wpcf7r-fe.js

1628 ms

init.js

init.js

1817 ms

cookie.js

cookie.js

1880 ms

setcookie.js

setcookie.js

1902 ms

magnific-popup.js

magnific-popup.js

1904 ms

us.core.min.js

us.core.min.js

2415 ms

owl.carousel.js

owl.carousel.js

2508 ms

isotope.js

isotope.js

2663 ms

royalslider.js

royalslider.js

2727 ms

log

log

416 ms

logo.svg

logo.svg

1320 ms

Aunt-Minnie-The-Best-of-Radiology.png

Aunt-Minnie-The-Best-of-Radiology.png

1508 ms

banner_graphics_us-1024x824-3.webp

banner_graphics_us-1024x824-3.webp

2041 ms

Group-539.png

Group-539.png

2085 ms

home-map.png

home-map.png

2348 ms

Hospital-Authority-HK.svg

Hospital-Authority-HK.svg

2245 ms

I-Med-Radiology.svg

I-Med-Radiology.svg

3939 ms

Raleigh-Radiology.svg

Raleigh-Radiology.svg

2164 ms

NHS-Epsom.svg

NHS-Epsom.svg

2685 ms

Ramsay-Sime.svg

Ramsay-Sime.svg

2975 ms

NHS-Morecambe.svg

NHS-Morecambe.svg

3001 ms

Sonic-Healthcare.svg

Sonic-Healthcare.svg

2879 ms

aarthi04.png

aarthi04.png

3176 ms

unilabs-1.svg

unilabs-1.svg

2913 ms

imgpsh_fullsize_anim.png

imgpsh_fullsize_anim.png

3508 ms

g2530.png

g2530.png

3540 ms

Target.png

Target.png

3623 ms

Group.png

Group.png

3654 ms

Vector-1.png

Vector-1.png

3806 ms

Group1.png

Group1.png

4172 ms

Clinical-CTB-ROW-e-a-hematoma-simple-over-website2.png

Clinical-CTB-ROW-e-a-hematoma-simple-over-website2.png

4764 ms

Clinical-CXR-ROW-Focal-Airspace-Opacity-over-website.png

Clinical-CXR-ROW-Focal-Airspace-Opacity-over-website.png

4470 ms

CXR-Edge-1.png

CXR-Edge-1.png

4680 ms

Clinical-CTB-ROW-e-a-hematoma-simple-over-website-blurred.png

Clinical-CTB-ROW-e-a-hematoma-simple-over-website-blurred.png

5027 ms

fa-regular-400.woff

fa-regular-400.woff

5358 ms

fa-light-300.woff

fa-light-300.woff

5564 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

57 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

57 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

69 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

70 ms

fa-solid-900.woff

fa-solid-900.woff

5631 ms

Clinical-CXR-ROW-Focal-Airspace-Opacity-over-website-Blurred.png

Clinical-CXR-ROW-Focal-Airspace-Opacity-over-website-Blurred.png

5539 ms

image_2023_05_23T11_27_28_646Z.png

image_2023_05_23T11_27_28_646Z.png

5641 ms

Triage-Screen-Mockup-1.gif

Triage-Screen-Mockup-1.gif

5440 ms

Layer_1-2.png

Layer_1-2.png

5385 ms

Layer_1-1.png

Layer_1-1.png

5640 ms

Layer_1-3.png

Layer_1-3.png

5250 ms

Layer_1.png

Layer_1.png

5328 ms

icona3.png

icona3.png

5386 ms

icona2.png

icona2.png

5287 ms

ANA-Map-020223.png

ANA-Map-020223.png

5612 ms

home-team.webp

home-team.webp

5803 ms

icon-blog-new.svg

icon-blog-new.svg

5164 ms

logo-axrem.png

logo-axrem.png

5192 ms

logo-bsi.png

logo-bsi.png

5325 ms

logo-bsi2.png

logo-bsi2.png

5657 ms

footer-logo.svg

footer-logo.svg

4817 ms

icon-backtotop.svg

icon-backtotop.svg

5112 ms

Group-602.png

Group-602.png

4700 ms

home-team.webp

home-team.webp

5958 ms

slider1.png

slider1.png

6006 ms

drafting-future1.png

drafting-future1.png

6284 ms

03.jpg

03.jpg

4985 ms

imgpsh_fullsize_anim.png

imgpsh_fullsize_anim.png

5083 ms

testimonial-bg.webp

testimonial-bg.webp

5235 ms

No_img01.jpg

No_img01.jpg

5708 ms

tick.svg

tick.svg

5456 ms

Accessibility Review

annalise.ai accessibility score

97

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

annalise.ai 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

annalise.ai SEO score

89

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Annalise.ai 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 Annalise.ai 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

annalise.ai

Open Graph data is detected on the main page of Annalise. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: