Tools & Wizards About Us
be.bio screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

be.bio

Be Biopharma - Advancing our science with bold humanity

Page Load Speed

1.1 sec in total

First Response

127 ms

Resources Loaded

823 ms

Page Rendered

159 ms

be.bio screenshot

About Website

Click here to check amazing Be content. Otherwise, check out these important facts you probably never knew about be.bio

Be Bio is developing a proprietary class of engineered B cells as medicines that unleash the potential of cell therapies in applications beyond cytotoxicity.

Visit be.bio

Key Findings

We analyzed Be.bio page load time and found that the first response time was 127 ms and then it took 982 ms 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.

Performance Metrics

be.bio performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

be.bio

127 ms

be.bio

127 ms

style.css

31 ms

wpr-hamburger.css

59 ms

wprmenu.css

70 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 88% of them (64 requests) were addressed to the original Be.bio, 5% (4 requests) were made to Cdnjs.cloudflare.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (247 ms) belongs to the original domain Be.bio.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.3 kB (7%)

Content Size

819.0 kB

After Optimization

759.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Be.bio main page is 819.0 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. 70% of websites need less resources to load. Images take 523.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 51.4 kB

  • Original 65.8 kB
  • After minification 64.5 kB
  • After compression 14.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 51.4 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 523.6 kB
  • After minification 523.6 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. Be images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.5 kB

  • Original 148.1 kB
  • After minification 148.0 kB
  • After compression 146.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

-8%

Potential reduce by 6.4 kB

  • Original 81.5 kB
  • After minification 79.5 kB
  • After compression 75.1 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. Be.bio has all CSS files already compressed.

Requests Breakdown

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

Requests Now

60

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

be.bio

be.bio

127 ms

be.bio

be.bio

127 ms

style.css

style.css

31 ms

wpr-hamburger.css

wpr-hamburger.css

59 ms

wprmenu.css

wprmenu.css

70 ms

wpr-icons.css

wpr-icons.css

63 ms

ivory-search.min.css

ivory-search.min.css

80 ms

css

css

106 ms

stylesheet.css

stylesheet.css

62 ms

dashicons.min.css

dashicons.min.css

69 ms

slick.css

slick.css

117 ms

slick-theme.css

slick-theme.css

134 ms

front-end.css

front-end.css

95 ms

frontend.min.css

frontend.min.css

98 ms

swiper.min.css

swiper.min.css

95 ms

e-swiper.min.css

e-swiper.min.css

104 ms

post-9.css

post-9.css

103 ms

popup.min.css

popup.min.css

114 ms

fadeInUp.min.css

fadeInUp.min.css

115 ms

widget-text-editor.min.css

widget-text-editor.min.css

115 ms

fadeIn.min.css

fadeIn.min.css

145 ms

widget-image.min.css

widget-image.min.css

112 ms

zoomIn.min.css

zoomIn.min.css

125 ms

post-16.css

post-16.css

143 ms

style.css

style.css

140 ms

css

css

143 ms

jquery.min.js

jquery.min.js

147 ms

jquery-migrate.min.js

jquery-migrate.min.js

139 ms

modernizr.custom.js

modernizr.custom.js

169 ms

touchSwipe.js

touchSwipe.js

179 ms

wprmenu.js

wprmenu.js

173 ms

js

js

173 ms

ivory-ajax-search.min.css

ivory-ajax-search.min.css

174 ms

page-scroll-to-id.min.js

page-scroll-to-id.min.js

174 ms

hoverIntent.min.js

hoverIntent.min.js

174 ms

superfish.min.js

superfish.min.js

175 ms

superfish.args.min.js

superfish.args.min.js

175 ms

skip-links.min.js

skip-links.min.js

175 ms

slick.min.js

slick.min.js

170 ms

e47830bbf6.js

e47830bbf6.js

106 ms

scripts.js

scripts.js

169 ms

responsive-menus.min.js

responsive-menus.min.js

170 ms

scripts.js

scripts.js

233 ms

ivory-search.min.js

ivory-search.min.js

232 ms

ivory-ajax-search.min.js

ivory-ajax-search.min.js

233 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

218 ms

webpack.runtime.min.js

webpack.runtime.min.js

193 ms

frontend-modules.min.js

frontend-modules.min.js

187 ms

hooks.min.js

hooks.min.js

185 ms

i18n.min.js

i18n.min.js

238 ms

frontend.min.js

frontend.min.js

179 ms

core.min.js

core.min.js

163 ms

frontend.min.js

frontend.min.js

153 ms

elements-handlers.min.js

elements-handlers.min.js

148 ms

logo-line-pink.svg

logo-line-pink.svg

109 ms

spinner.gif

spinner.gif

91 ms

logo.svg

logo.svg

92 ms

illustrator-01.png

illustrator-01.png

147 ms

hero-photo-01.png

hero-photo-01.png

94 ms

hero-photo-03.png

hero-photo-03.png

95 ms

hero-photo-03.webp

hero-photo-03.webp

91 ms

SofiaProRegular.woff

SofiaProRegular.woff

123 ms

SofiaProMedium.woff

SofiaProMedium.woff

127 ms

SofiaProSemiBold.woff

SofiaProSemiBold.woff

122 ms

SofiaProBold.woff

SofiaProBold.woff

144 ms

SofiaProBlack.woff

SofiaProBlack.woff

54 ms

SofiaProMedium-Italic.woff

SofiaProMedium-Italic.woff

128 ms

SofiaProRegular-Italic.woff

SofiaProRegular-Italic.woff

144 ms

SofiaProSemiBold-Italic.woff

SofiaProSemiBold-Italic.woff

212 ms

SofiaProBold-Italic.woff

SofiaProBold-Italic.woff

222 ms

SofiaProBlack-Italic.woff

SofiaProBlack-Italic.woff

247 ms

Prompt-Medium.woff

Prompt-Medium.woff

234 ms

ajax-loader.gif

ajax-loader.gif

40 ms

Accessibility Review

be.bio accessibility score

85

Accessibility Issues

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

be.bio 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

SEO Factors

be.bio 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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Be.bio 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 Be.bio 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

be.bio

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