Tools & Wizards About Us
fmbr.org screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

fmbr.org

Home - FMBR

Page Load Speed

1.4 sec in total

First Response

150 ms

Resources Loaded

494 ms

Page Rendered

770 ms

fmbr.org screenshot

About Website

Visit fmbr.org now to see the best up-to-date FMBR content for United States and also check out these interesting facts you probably never knew about fmbr.org

FMBR is a non-profit organization exploring cutting-edge theories around matter, energy, the nature of the universe and consciousness.

Visit fmbr.org

Key Findings

We analyzed Fmbr.org page load time and found that the first response time was 150 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster. This domain responded with an error, which can significantly jeopardize Fmbr.org rating and web reputation

Performance Metrics

fmbr.org performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value4.5 s

83/100

10%

Network Requests Diagram

fmbr.org

150 ms

nr-1123.min.js

176 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Fmbr.org, 50% (1 request) were made to Js-agent.newrelic.com. The less responsive or slowest element that took the longest time to load (176 ms) relates to the external source Js-agent.newrelic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.0 kB (46%)

Content Size

28.2 kB

After Optimization

15.2 kB

  • HTML
  • JavaScript

In fact, the total size of Fmbr.org main page is 28.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 18.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 13.0 kB

  • Original 18.9 kB
  • After minification 18.9 kB
  • After compression 5.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. 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 13.0 kB or 69% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 9.3 kB
  • After minification 9.3 kB
  • After compression 9.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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

  • JavaScript

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FMBR. According to our analytics all requests are already optimized.

Network Requests Diagram

fmbr.org

fmbr.org

150 ms

nr-1123.min.js

nr-1123.min.js

176 ms

Accessibility Review

fmbr.org accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Best Practices

fmbr.org best practices score

83

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

Browser errors were logged to the console

SEO Factors

fmbr.org SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fmbr.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fmbr.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

fmbr.org

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