1.2 sec in total
86 ms
983 ms
160 ms
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.bioWe analyzed Be.bio page load time and found that the first response time was 86 ms and then it took 1.1 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.
be.bio performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value5.9 s
14/100
25%
Value5.1 s
61/100
10%
Value710 ms
42/100
30%
Value0.001
100/100
15%
Value10.0 s
26/100
10%
86 ms
109 ms
22 ms
182 ms
42 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 88% of them (63 requests) were addressed to the original Be.bio, 6% (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 (475 ms) belongs to the original domain Be.bio.
Page size can be reduced by 61.6 kB (7%)
900.2 kB
838.7 kB
In fact, the total size of Be.bio main page is 900.2 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 554.5 kB which makes up the majority of the site volume.
Potential reduce by 51.5 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.5 kB or 78% of the original size.
Potential reduce by 0 B
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.
Potential reduce by 2.7 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.
Potential reduce by 7.3 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.
Number of requests can be reduced by 49 (83%)
59
10
The browser has sent 59 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 31 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
be.bio
86 ms
be.bio
109 ms
style.css
22 ms
wpr-hamburger.css
182 ms
wprmenu.css
42 ms
wpr-icons.css
44 ms
ivory-search.min.css
42 ms
css
53 ms
stylesheet.css
179 ms
dashicons.min.css
46 ms
slick.css
47 ms
slick-theme.css
54 ms
front-end.css
141 ms
frontend-lite.min.css
54 ms
swiper.min.css
60 ms
post-9.css
66 ms
frontend-lite.min.css
70 ms
post-16.css
176 ms
style.css
84 ms
css
63 ms
jquery.min.js
82 ms
jquery-migrate.min.js
93 ms
modernizr.custom.js
99 ms
touchSwipe.js
104 ms
wprmenu.js
120 ms
js
77 ms
ivory-ajax-search.min.css
118 ms
animations.min.css
131 ms
page-scroll-to-id.min.js
135 ms
hoverIntent.min.js
397 ms
superfish.min.js
151 ms
superfish.args.min.js
148 ms
skip-links.min.js
159 ms
slick.min.js
55 ms
e47830bbf6.js
139 ms
scripts.js
162 ms
responsive-menus.min.js
173 ms
scripts.js
337 ms
ivory-search.min.js
338 ms
ivory-ajax-search.min.js
338 ms
webpack-pro.runtime.min.js
441 ms
webpack.runtime.min.js
475 ms
frontend-modules.min.js
340 ms
wp-polyfill-inert.min.js
338 ms
regenerator-runtime.min.js
338 ms
wp-polyfill.min.js
326 ms
hooks.min.js
307 ms
i18n.min.js
305 ms
frontend.min.js
307 ms
waypoints.min.js
304 ms
core.min.js
291 ms
frontend.min.js
289 ms
elements-handlers.min.js
285 ms
logo-line-pink.svg
170 ms
spinner.gif
207 ms
logo.svg
196 ms
illustrator-01.png
155 ms
hero-photo-01.png
401 ms
hero-photo-03.png
155 ms
hero-photo-03.webp
173 ms
SofiaProRegular.woff
130 ms
SofiaProMedium.woff
252 ms
SofiaProSemiBold.woff
201 ms
SofiaProBold.woff
251 ms
SofiaProBlack.woff
250 ms
SofiaProMedium-Italic.woff
254 ms
SofiaProRegular-Italic.woff
252 ms
SofiaProSemiBold-Italic.woff
370 ms
SofiaProBold-Italic.woff
356 ms
SofiaProBlack-Italic.woff
337 ms
Prompt-Medium.woff
328 ms
ajax-loader.gif
49 ms
be.bio accessibility score
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
be.bio 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
be.bio SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 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.
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: