Tools & Wizards About Us
gt-scan.net screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

gt-scan.net

GT-Scan Suite: A CRISPR/Cas9 genome editing toolbox

Page Load Speed

4.9 sec in total

First Response

511 ms

Resources Loaded

4 sec

Page Rendered

355 ms

gt-scan.net screenshot

About Website

Click here to check amazing GT Scan content for Australia. Otherwise, check out these important facts you probably never knew about gt-scan.net

The GT-Scan Suite is a series of tools for designing efficient CRISPR-Cas9 targets based on their uniqueness and efficiency.

Visit gt-scan.net

Key Findings

We analyzed Gt-scan.net page load time and found that the first response time was 511 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

gt-scan.net performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

gt-scan.net

511 ms

gt-scan.csiro.au

1449 ms

css

35 ms

icon

54 ms

styles.47d79c0cc896dedcabbf.css

473 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Gt-scan.net, 45% (18 requests) were made to Platform.twitter.com and 25% (10 requests) were made to Gt-scan.csiro.au. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Gt-scan.csiro.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 39.0 kB (8%)

Content Size

480.9 kB

After Optimization

441.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Gt-scan.net main page is 480.9 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. 65% of websites need less resources to load. Images take 419.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 32.9 kB

  • Original 40.4 kB
  • After minification 40.3 kB
  • After compression 7.5 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 32.9 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 6.1 kB

  • Original 419.6 kB
  • After minification 413.5 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. GT Scan images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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 24 (71%)

Requests Now

34

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gt-scan.net

gt-scan.net

511 ms

gt-scan.csiro.au

gt-scan.csiro.au

1449 ms

css

css

35 ms

icon

icon

54 ms

styles.47d79c0cc896dedcabbf.css

styles.47d79c0cc896dedcabbf.css

473 ms

runtime-es2015.a07ce0d5e5344583c4af.js

runtime-es2015.a07ce0d5e5344583c4af.js

697 ms

runtime-es5.a07ce0d5e5344583c4af.js

runtime-es5.a07ce0d5e5344583c4af.js

709 ms

polyfills-es5.c96276297f781df841db.js

polyfills-es5.c96276297f781df841db.js

1177 ms

polyfills-es2015.62dc6c8bfd12d06523ed.js

polyfills-es2015.62dc6c8bfd12d06523ed.js

725 ms

main-es2015.90bf37f539794ab29b57.js

main-es2015.90bf37f539794ab29b57.js

1631 ms

main-es5.90bf37f539794ab29b57.js

main-es5.90bf37f539794ab29b57.js

1213 ms

widgets.js

widgets.js

19 ms

analytics.js

analytics.js

61 ms

background.jpg

background.jpg

1596 ms

noise.png

noise.png

951 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

22 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

23 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

29 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

42 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

144 ms

collect

collect

71 ms

settings

settings

77 ms

js

js

74 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

3 ms

gt_scan

gt_scan

222 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

4 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

23 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

27 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

36 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

35 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

36 ms

_buildManifest.js

_buildManifest.js

60 ms

_ssgManifest.js

_ssgManifest.js

58 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

11 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

11 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

3 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

16 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

9 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

16 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

8 ms

Accessibility Review

gt-scan.net accessibility score

85

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

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

gt-scan.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

gt-scan.net SEO score

83

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

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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 Gt-scan.net 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 Gt-scan.net 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

gt-scan.net

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