6.7 sec in total
287 ms
3.8 sec
2.6 sec
Welcome to rest.genenames.org homepage info - get ready to check REST Gene Names best content for United States right away, or after learning these important things about rest.genenames.org
The HUGO Gene Nomenclature Committee (HGNC) REST web-service is a convenient and quick way of searching and fetching data from our database within a script/program. Users may request results as either...
Visit rest.genenames.orgWe analyzed Rest.genenames.org page load time and found that the first response time was 287 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
rest.genenames.org performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value4.9 s
29/100
25%
Value8.9 s
15/100
10%
Value1,380 ms
16/100
30%
Value0.001
100/100
15%
Value14.3 s
9/100
10%
287 ms
486 ms
121 ms
201 ms
376 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Rest.genenames.org, 47% (15 requests) were made to Genenames.org and 19% (6 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Genenames.org.
Page size can be reduced by 439.9 kB (75%)
585.1 kB
145.1 kB
In fact, the total size of Rest.genenames.org main page is 585.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 397.1 kB which makes up the majority of the site volume.
Potential reduce by 96.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 96.4 kB or 84% of the original size.
Potential reduce by 24.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 24.3 kB or 33% of the original size.
Potential reduce by 319.2 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. Rest.genenames.org needs all CSS files to be minified and compressed as it can save up to 319.2 kB or 80% of the original size.
Number of requests can be reduced by 8 (33%)
24
16
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of REST Gene Names. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
rest.genenames.org
287 ms
486 ms
gtm.js
121 ms
default-bf.css
201 ms
hgnc-logo-dark-bckgrnd-small.svg
376 ms
Zrn5l6fTVH0
296 ms
default-bf.js
1442 ms
analytics.js
537 ms
js
220 ms
www-player.css
604 ms
www-embed-player.js
642 ms
base.js
678 ms
fetch-polyfill.js
600 ms
fa-solid-900.woff
1403 ms
fa-regular-400.woff
329 ms
collect
872 ms
hgnc-light-bkgrd-no-txt.svg
512 ms
EMBL_EBI_logo-grayscale.svg
745 ms
cambs-long-gs.svg
506 ms
HUGO.svg
733 ms
NHGRI.svg
593 ms
elixir_unitedkingdom_grayscale_transparent_bkgrd.svg
595 ms
wellcome-logo-black-trans.svg
740 ms
collect
608 ms
VM1LbcxuQZ7urdjSm15-Kft2IdlldgxYJTjOL3p1Mjw.js
352 ms
embed.js
165 ms
glyphicons-halflings-regular.woff
310 ms
fa-brands-400.woff
660 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
223 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
224 ms
Create
121 ms
collect
25 ms
rest.genenames.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
rest.genenames.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
rest.genenames.org SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rest.genenames.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 Rest.genenames.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.
rest.genenames.org
Open Graph description is not detected on the main page of REST Gene Names. 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: