Tools & Wizards About Us
gtexportal.org screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

gtexportal.org

GTEx Portal

Page Load Speed

1.7 sec in total

First Response

70 ms

Resources Loaded

1.5 sec

Page Rendered

142 ms

gtexportal.org screenshot

About Website

Click here to check amazing GTEx Portal content for United States. Otherwise, check out these important facts you probably never knew about gtexportal.org

The Genotype-Tissue Expression (GTEx) project is an ongoing effort to build a comprehensive public resource to study tissue-specific gene expression and regulation. Samples were collected from 53 non-...

Visit gtexportal.org

Key Findings

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

Performance Metrics

gtexportal.org performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

gtexportal.org

70 ms

gtexportal.org

51 ms

index.html

28 ms

index.html

67 ms

gtm.js

77 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 82% of them (84 requests) were addressed to the original Gtexportal.org, 4% (4 requests) were made to Use.fontawesome.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (588 ms) belongs to the original domain Gtexportal.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (15%)

Content Size

8.0 MB

After Optimization

6.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gtexportal.org main page is 8.0 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. 70% of websites need less resources to load. Javascripts take 7.7 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 17.6 kB

  • Original 23.4 kB
  • After minification 22.2 kB
  • After compression 5.8 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 17.6 kB or 75% of the original size.

Image Optimization

-30%

Potential reduce by 61.7 kB

  • Original 202.8 kB
  • After minification 141.1 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, GTEx Portal needs image optimization as it can save up to 61.7 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 1.1 MB

  • Original 7.7 MB
  • After minification 7.7 MB
  • After compression 6.6 MB

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 1.1 MB or 14% of the original size.

CSS Optimization

-19%

Potential reduce by 16.4 kB

  • Original 86.1 kB
  • After minification 85.7 kB
  • After compression 69.7 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. Gtexportal.org needs all CSS files to be minified and compressed as it can save up to 16.4 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 80 (87%)

Requests Now

92

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gtexportal.org

gtexportal.org

70 ms

gtexportal.org

gtexportal.org

51 ms

index.html

index.html

28 ms

index.html

index.html

67 ms

gtm.js

gtm.js

77 ms

jquery-ui.css

jquery-ui.css

41 ms

bootstrap.min.css

bootstrap.min.css

93 ms

fontawesome-all.min.css

fontawesome-all.min.css

100 ms

all.css

all.css

88 ms

select2.min.css

select2.min.css

102 ms

ptv.css

ptv.css

98 ms

bubbleMap.css

bubbleMap.css

120 ms

dendrogram.css

dendrogram.css

119 ms

halfMap.css

halfMap.css

139 ms

tissueGroup.css

tissueGroup.css

106 ms

violin.css

violin.css

139 ms

eqtlDashboard.css

eqtlDashboard.css

105 ms

expressMap.css

expressMap.css

122 ms

geneExpViolin.css

geneExpViolin.css

160 ms

isoform.css

isoform.css

134 ms

locusBrowser.css

locusBrowser.css

136 ms

locusBrowserVC.css

locusBrowserVC.css

175 ms

singleCellMultiGeneAPM.css

singleCellMultiGeneAPM.css

188 ms

css

css

96 ms

forestpm.css

forestpm.css

153 ms

pcaplot.css

pcaplot.css

152 ms

jquery.dataTables_themeroller.css

jquery.dataTables_themeroller.css

190 ms

buttons.jqueryui.min.css

buttons.jqueryui.min.css

171 ms

css

css

104 ms

icon

icon

119 ms

gtex-body-map.css

gtex-body-map.css

205 ms

jquery.min.js

jquery.min.js

61 ms

bootstrap.min.js

bootstrap.min.js

175 ms

jquery-ui.min.js

jquery-ui.min.js

254 ms

jquery.cookie.js

jquery.cookie.js

189 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

245 ms

dataTables.jqueryui.min.js

dataTables.jqueryui.min.js

241 ms

dataTables.buttons.min.js

dataTables.buttons.min.js

246 ms

buttons.jqueryui.min.js

buttons.jqueryui.min.js

247 ms

jszip.min.js

jszip.min.js

275 ms

buttons.html5.min.js

buttons.html5.min.js

273 ms

buttons.flash.min.js

buttons.flash.min.js

273 ms

moment.min.js

moment.min.js

68 ms

datetime-moment.js

datetime-moment.js

66 ms

jquery.form.js

jquery.form.js

273 ms

jquery.hotkeys.js

jquery.hotkeys.js

301 ms

jquery.placeholder.js

jquery.placeholder.js

274 ms

highcharts.js

highcharts.js

100 ms

streamgraph.js

streamgraph.js

123 ms

series-label.js

series-label.js

127 ms

igv.min.js

igv.min.js

85 ms

dataTables.select.min.js

dataTables.select.min.js

96 ms

popper.min.js

popper.min.js

93 ms

js

js

103 ms

slick.css

slick.css

283 ms

react-select.css

react-select.css

284 ms

gtex-hip.css

gtex-hip.css

226 ms

app.2996903e.css

app.2996903e.css

230 ms

spin.js

spin.js

235 ms

jquery.spin.js

jquery.spin.js

195 ms

jquery.validate.min.js

jquery.validate.min.js

208 ms

additional-methods.min.js

additional-methods.min.js

252 ms

jquery.uploadifive.js

jquery.uploadifive.js

213 ms

simple-expand.min.js

simple-expand.min.js

219 ms

select2.full.min.js

select2.full.min.js

232 ms

FileSaver.js

FileSaver.js

248 ms

d3.v3.min.js

d3.v3.min.js

239 ms

ptvviz.js

ptvviz.js

264 ms

d3-forestpm.js

d3-forestpm.js

265 ms

jquery.html5storage.js

jquery.html5storage.js

218 ms

openseadragon.min.js

openseadragon.min.js

303 ms

openseadragon-imaginghelper.min.js

openseadragon-imaginghelper.min.js

339 ms

pcaplot.js

pcaplot.js

231 ms

gtex-body-map.js

gtex-body-map.js

421 ms

expression-map.webpack.min.js

expression-map.webpack.min.js

303 ms

eqtl-dashboard.webpack.min.js

eqtl-dashboard.webpack.min.js

266 ms

transcript-browser.webpack.min.js

transcript-browser.webpack.min.js

313 ms

qtl-violin-plot.webpack.min.js

qtl-violin-plot.webpack.min.js

536 ms

locus-browser.webpack.min.js

locus-browser.webpack.min.js

359 ms

locus-browser-vc.webpack.min.js

locus-browser-vc.webpack.min.js

394 ms

iqtl-scatter-plot.webpack.min.js

iqtl-scatter-plot.webpack.min.js

527 ms

gene-expression-violin-plot.webpack.min.js

gene-expression-violin-plot.webpack.min.js

533 ms

single-cell-multi-gene-apm.webpack.min.js

single-cell-multi-gene-apm.webpack.min.js

456 ms

chunk-vendors.55e18043.js

chunk-vendors.55e18043.js

422 ms

app.7ca0150e.js

app.7ca0150e.js

588 ms

analytics.js

analytics.js

102 ms

gtex-portal-logo.50480ab0.png

gtex-portal-logo.50480ab0.png

57 ms

gtex-logo-no-text.54c480f3.png

gtex-logo-no-text.54c480f3.png

22 ms

dGTEx-logo-no-text.300b2995.png

dGTEx-logo-no-text.300b2995.png

49 ms

nhp-dgtex-logo-no-text.d39ce0d8.png

nhp-dgtex-logo-no-text.d39ce0d8.png

93 ms

broad-logo.57b1ddc3.png

broad-logo.57b1ddc3.png

77 ms

ui-bg_inset-hard_100_fcfdfd_1x100.png

ui-bg_inset-hard_100_fcfdfd_1x100.png

21 ms

ui-icons_469bdd_256x240.png

ui-icons_469bdd_256x240.png

47 ms

ui-bg_highlight-hard_45_5c89cc_1x100.png

ui-bg_highlight-hard_45_5c89cc_1x100.png

117 ms

ui-bg_glass_85_dfeffc_1x400.png

ui-bg_glass_85_dfeffc_1x400.png

55 ms

ui-icons_6da8d5_256x240.png

ui-icons_6da8d5_256x240.png

145 ms

fa-solid-900.woff

fa-solid-900.woff

18 ms

fa-solid-900.woff

fa-solid-900.woff

173 ms

fa-regular-400.woff

fa-regular-400.woff

20 ms

fa-regular-400.woff

fa-regular-400.woff

126 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

155 ms

fa-brands-400.woff

fa-brands-400.woff

46 ms

fa-brands-400.woff

fa-brands-400.woff

244 ms

Accessibility Review

gtexportal.org accessibility score

86

Accessibility Issues

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.

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

gtexportal.org best practices score

92

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

Page has valid source maps

SEO Factors

gtexportal.org SEO score

77

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

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

gtexportal.org

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