Tools & Wizards About Us
forome.org screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

forome.org

Forome Association | Undiagnosed Diseases Genomics Platform

Page Load Speed

9.4 sec in total

First Response

2.5 sec

Resources Loaded

6.2 sec

Page Rendered

803 ms

forome.org screenshot

About Website

Visit forome.org now to see the best up-to-date Forome content and also check out these interesting facts you probably never knew about forome.org

Scientifically proven crowdsourcing program and bioinformatics tools improve greatly new genes discovery for rare undiagnosed conditions. Join us in developing the tools and open source community.

Visit forome.org

Key Findings

We analyzed Forome.org page load time and found that the first response time was 2.5 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

forome.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value1.298

1/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

forome.org

2473 ms

svgs-attachment.css

41 ms

css

40 ms

animate.min.css

96 ms

font-awesome.min.css

151 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 67% of them (39 requests) were addressed to the original Forome.org, 28% (16 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Forome.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.1 kB (3%)

Content Size

3.7 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forome.org main page is 3.7 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. 60% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 34.4 kB

  • Original 42.7 kB
  • After minification 34.2 kB
  • After compression 8.3 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 8.5 kB, which is 20% 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 34.4 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 50.0 kB

  • Original 3.4 MB
  • After minification 3.3 MB

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. Forome images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 15.7 kB

  • Original 261.3 kB
  • After minification 261.3 kB
  • After compression 245.6 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.

CSS Optimization

-38%

Potential reduce by 13.0 kB

  • Original 34.4 kB
  • After minification 34.3 kB
  • After compression 21.4 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. Forome.org needs all CSS files to be minified and compressed as it can save up to 13.0 kB or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (50%)

Requests Now

40

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forome.org

forome.org

2473 ms

svgs-attachment.css

svgs-attachment.css

41 ms

css

css

40 ms

animate.min.css

animate.min.css

96 ms

font-awesome.min.css

font-awesome.min.css

151 ms

bootstrap.min.css

bootstrap.min.css

212 ms

style.css

style.css

270 ms

lightgallery.css

lightgallery.css

301 ms

onepress-plus.css

onepress-plus.css

337 ms

jquery.js

jquery.js

380 ms

jquery-migrate.min.js

jquery-migrate.min.js

412 ms

wpforms-base.css

wpforms-base.css

537 ms

plugins.js

plugins.js

549 ms

bootstrap.min.js

bootstrap.min.js

569 ms

theme.js

theme.js

588 ms

owl.carousel.min.js

owl.carousel.min.js

650 ms

slider.js

slider.js

863 ms

onepress-plus.js

onepress-plus.js

905 ms

wp-embed.min.js

wp-embed.min.js

937 ms

jquery.validate.min.js

jquery.validate.min.js

971 ms

wpforms.js

wpforms.js

1002 ms

api.js

api.js

44 ms

Forome_Association_Logo_svg.svg

Forome_Association_Logo_svg.svg

643 ms

hero_new.jpg

hero_new.jpg

835 ms

association.png

association.png

901 ms

project.png

project.png

815 ms

joinus.png

joinus.png

743 ms

HMS.svg

HMS.svg

710 ms

BWH.svg

BWH.svg

700 ms

image004.png

image004.png

733 ms

Quantori-Logo-Horizontal.svg

Quantori-Logo-Horizontal.svg

740 ms

Strand-front-vector.svg

Strand-front-vector.svg

937 ms

undiagnosed_bg_2-e1540368493929.jpg

undiagnosed_bg_2-e1540368493929.jpg

870 ms

scheme4.svg

scheme4.svg

798 ms

Shamil300p-300x300.jpg

Shamil300p-300x300.jpg

827 ms

Joel300p-300x300.jpg

Joel300p-300x300.jpg

844 ms

Dana300p-300x300.png

Dana300p-300x300.png

890 ms

Misha300p.jpg

Misha300p.jpg

867 ms

Dima300p-300x300.png

Dima300p-300x300.png

989 ms

map-3.jpg

map-3.jpg

1005 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVcUwaEQXjM.ttf

46 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVcUwaEQXjM.ttf

105 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVcUwaEQXjM.ttf

46 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVcUwaEQXjM.ttf

58 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQVIT9d4cw.ttf

45 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQVIT9d4cw.ttf

57 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQVIT9d4cw.ttf

60 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQVIT9d4cw.ttf

61 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQVIT9d4cw.ttf

59 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQVIT9d4cw.ttf

61 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQVIT9d4cw.ttf

59 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQVIT9d4cw.ttf

98 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exYMUdjFnmg.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exYMUdjFnmg.ttf

104 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exYMUdjFnmg.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exYMUdjFnmg.ttf

97 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exYMUdjFnmg.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exYMUdjFnmg.ttf

102 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exYMUdjFnmg.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exYMUdjFnmg.ttf

96 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

808 ms

recaptcha__en.js

recaptcha__en.js

26 ms

Accessibility Review

forome.org accessibility score

94

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

Low

No form fields have multiple labels

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

Best Practices

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

SEO Factors

forome.org SEO score

100

Search Engine Optimization Advices

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 Forome.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 Forome.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

forome.org

Open Graph data is detected on the main page of Forome. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: