Tools & Wizards About Us
anvilproject.org screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

anvilproject.org

AnVIL Portal

Page Load Speed

1.4 sec in total

First Response

9 ms

Resources Loaded

758 ms

Page Rendered

653 ms

anvilproject.org screenshot

About Website

Click here to check amazing AnVIL Project content for United States. Otherwise, check out these important facts you probably never knew about anvilproject.org

Visit anvilproject.org

Key Findings

We analyzed Anvilproject.org page load time and found that the first response time was 9 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

anvilproject.org performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value2,100 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

anvilproject.org

9 ms

anvilproject.org

298 ms

widgets.js

369 ms

polyfills-c67a75d1b6f99dc8.js

293 ms

webpack-c4acd79e87956a0e.js

388 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 67% of them (31 requests) were addressed to the original Anvilproject.org, 24% (11 requests) were made to Platform.twitter.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (485 ms) belongs to the original domain Anvilproject.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 316.2 kB (20%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Anvilproject.org main page is 1.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. 55% of websites need less resources to load. Images take 926.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 192.0 kB

  • Original 229.4 kB
  • After minification 229.4 kB
  • After compression 37.4 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 192.0 kB or 84% of the original size.

Image Optimization

-13%

Potential reduce by 123.9 kB

  • Original 926.9 kB
  • After minification 803.0 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. Obviously, AnVIL Project needs image optimization as it can save up to 123.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 325 B

  • Original 421.4 kB
  • After minification 421.4 kB
  • After compression 421.0 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 17 (40%)

Requests Now

42

After Optimization

25

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

anvilproject.org

anvilproject.org

9 ms

anvilproject.org

anvilproject.org

298 ms

widgets.js

widgets.js

369 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

293 ms

webpack-c4acd79e87956a0e.js

webpack-c4acd79e87956a0e.js

388 ms

framework-10fac88913917d91.js

framework-10fac88913917d91.js

383 ms

main-82eb924645ccaff6.js

main-82eb924645ccaff6.js

310 ms

_app-8aa3e298c601c91a.js

_app-8aa3e298c601c91a.js

485 ms

index-c1482c9149a383d0.js

index-c1482c9149a383d0.js

349 ms

_buildManifest.js

_buildManifest.js

309 ms

_ssgManifest.js

_ssgManifest.js

382 ms

logoAnvil.png

logoAnvil.png

304 ms

terra.png

terra.png

54 ms

anvil-explorer.png

anvil-explorer.png

122 ms

dockstore.png

dockstore.png

137 ms

ncpi.png

ncpi.png

214 ms

bioconductor.png

bioconductor.png

122 ms

galaxy.png

galaxy.png

171 ms

jupyter.png

jupyter.png

208 ms

seqr.png

seqr.png

130 ms

gatk.png

gatk.png

131 ms

hail.png

hail.png

199 ms

inferCNV.png

inferCNV.png

203 ms

optimusPipeline.png

optimusPipeline.png

222 ms

cloudCheck.svg

cloudCheck.svg

247 ms

piggyBank.svg

piggyBank.svg

259 ms

fileShield.svg

fileShield.svg

210 ms

megaphone.svg

megaphone.svg

270 ms

nhgri.svg

nhgri.svg

216 ms

nih.svg

nih.svg

219 ms

hhs.svg

hhs.svg

339 ms

usagov.png

usagov.png

334 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff

28 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZs.woff

35 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

49 ms

settings

settings

70 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

19 ms

useAnVIL

useAnVIL

80 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

19 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

39 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

75 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

67 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

85 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

90 ms

_buildManifest.js

_buildManifest.js

88 ms

_ssgManifest.js

_ssgManifest.js

89 ms

Accessibility Review

anvilproject.org accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

anvilproject.org 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

anvilproject.org SEO score

82

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

    N/A

  • Encoding

    UTF-8

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

anvilproject.org

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