1.1 sec in total
88 ms
850 ms
156 ms
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.orgWe analyzed Gtexportal.org page load time and found that the first response time was 88 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
gtexportal.org performance score
name
value
score
weighting
Value10.8 s
0/100
10%
Value11.0 s
0/100
25%
Value10.8 s
6/100
10%
Value10 ms
100/100
30%
Value0.094
91/100
15%
Value10.9 s
21/100
10%
88 ms
28 ms
56 ms
63 ms
54 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 94% of them (101 requests) were addressed to the original Gtexportal.org, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Igv.org. The less responsive or slowest element that took the longest time to load (220 ms) belongs to the original domain Gtexportal.org.
Page size can be reduced by 1.8 MB (59%)
3.1 MB
1.2 MB
In fact, the total size of Gtexportal.org 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. 70% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 53.9 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. This page needs HTML code to be minified as it can gain 11.7 kB, which is 17% 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 53.9 kB or 80% of the original size.
Potential reduce by 199.3 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 199.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.4 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.4 MB or 74% of the original size.
Potential reduce by 203.8 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 203.8 kB or 83% of the original size.
Number of requests can be reduced by 78 (76%)
103
25
The browser has sent 103 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 62 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
gtexportal.org
88 ms
home
28 ms
56 ms
jquery.dataTables_themeroller.css
63 ms
screen.css
54 ms
jquery-ui.css
57 ms
temporary-fix.css
53 ms
plotviz.css
63 ms
bootstrap.min.css
67 ms
font-awesome.min.css
81 ms
spliceViz.css
79 ms
ptv.css
79 ms
portal.css
82 ms
igv-0.9.3.css
70 ms
gtexBubbleMap.css
81 ms
spinner.css
91 ms
jquery.min.js
39 ms
bootstrap.min.js
112 ms
jquery-ui.min.js
138 ms
jquery.cookie.js
115 ms
jquery.dataTables.min.js
121 ms
dataTables.tableTools.min.js
115 ms
jquery.form.js
117 ms
jquery.hotkeys.js
131 ms
jquery.placeholder.js
131 ms
spin.js
165 ms
jquery.spin.js
165 ms
jquery.validate.min.js
166 ms
additional-methods.min.js
167 ms
jquery.uploadifive.js
167 ms
jquery.history.js
177 ms
simple-expand.min.js
168 ms
highcharts.js
201 ms
account.js
175 ms
autocomplete.js
181 ms
browse-datasets.js
184 ms
bsp-sample-search.js
189 ms
contact.js
220 ms
directory.js
220 ms
eqtl.js
220 ms
igv-0.9.3.js
158 ms
eqtl-table-maker.js
218 ms
external-resource.js
183 ms
external-server-manager.js
187 ms
forgotPassword.js
182 ms
genePage.js
184 ms
login.js
189 ms
message-handler.js
181 ms
dataset.js
181 ms
egene.js
189 ms
file.js
189 ms
fileset.js
190 ms
gtex-webservice.js
194 ms
ptv-table-maker.js
166 ms
register.js
167 ms
rest-utils.js
177 ms
server-props.js
176 ms
table-id-utility.js
178 ms
table-maker.js
180 ms
table-utils.js
172 ms
tissue.js
176 ms
tissueDonutChart.js
154 ms
imprinting.js
153 ms
multiTissue.js
155 ms
bubbleHeatmapPage.js
157 ms
spliceQTL.js
158 ms
gtexVersion.js
164 ms
summaryPlots.js
174 ms
plotviz.js
187 ms
d3.v3.min.js
213 ms
spliceviz.min.js
173 ms
ptvviz.min.js
172 ms
ptv-summary-page.js
167 ms
jquery.html5storage.js
174 ms
navigationRouter.js
182 ms
portal.js
182 ms
bubblemap.min.js
181 ms
gtex2.png
69 ms
gtexhome.cropped.png
184 ms
spinner.gif
70 ms
gtexTissueBar.png
70 ms
gtexIgv.png
71 ms
bubbleHeatmap.png
71 ms
gtexBoxplot.png
74 ms
gtexExon.png
73 ms
BroadLogoFooter.gif
70 ms
local-service-override.json
83 ms
userContext
47 ms
maintenanceMessage
45 ms
tissues
56 ms
47 ms
114 ms
tissues
116 ms
analytics.js
18 ms
ui-bg_inset-hard_100_fcfdfd_1x100.png
113 ms
ui-icons_469bdd_256x240.png
113 ms
ui-bg_highlight-hard_45_5c89cc_1x100.png
114 ms
ui-bg_glass_85_dfeffc_1x400.png
116 ms
ui-icons_6da8d5_256x240.png
115 ms
glyphicons-halflings-regular.woff
179 ms
collect
77 ms
usage
154 ms
server
78 ms
externalServer
79 ms
usage
148 ms
tissues
77 ms
collect
69 ms
collect
92 ms
gtexportal.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
gtexportal.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
gtexportal.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
EN
EN
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.
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: