2.7 sec in total
642 ms
1.7 sec
364 ms
Click here to check amazing Biostime content for China. Otherwise, check out these important facts you probably never knew about biostime.com
Help develop a healthy digestive system for better nutrient absorption for your infant with Biostime's probiotics for babies.
Visit biostime.comWe analyzed Biostime.com page load time and found that the first response time was 642 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
biostime.com performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value4.6 s
35/100
25%
Value5.4 s
57/100
10%
Value1,460 ms
14/100
30%
Value0.004
100/100
15%
Value15.2 s
7/100
10%
642 ms
338 ms
54 ms
36 ms
42 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Biostime.com, 36% (21 requests) were made to Biostime.us and 20% (12 requests) were made to Images.prismic.io. The less responsive or slowest element that took the longest time to load (642 ms) belongs to the original domain Biostime.com.
Page size can be reduced by 278.2 kB (33%)
838.8 kB
560.6 kB
In fact, the total size of Biostime.com main page is 838.8 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. 65% of websites need less resources to load. HTML takes 378.3 kB which makes up the majority of the site volume.
Potential reduce by 277.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. 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 277.3 kB or 73% of the original size.
Potential reduce by 433 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. Biostime images are well optimized though.
Potential reduce by 186 B
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 251 B
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. Biostime.com has all CSS files already compressed.
Number of requests can be reduced by 38 (76%)
50
12
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Biostime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
biostime.com
642 ms
biostime.us
338 ms
bundle.theme.css
54 ms
bundle.index.css
36 ms
rs-styles.css
42 ms
preloads.js
52 ms
load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js
42 ms
storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js
35 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
93 ms
W43aoZLcUWj66cCBidtF3A
132 ms
bundle.theme.js
83 ms
bundle.index.js
82 ms
jquery.min.js
96 ms
gtm.js
144 ms
otSDKStub.js
105 ms
trekkie.storefront.dd626a6a6fbdab104f8779acc4331c330134c832.min.js
81 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
80 ms
shopify-boomerang-1.0.0.min.js
79 ms
7453234d-bd30-40ec-a084-9e63bba1743e_homepage+mobile+banner.png
128 ms
bc4a17ed-daaa-4d41-bf63-4b3b7e14fc36_child.svg
113 ms
4BCCF17B-60A0-4933-A623-B18F6B98DAAC.png
138 ms
instagram-icon.png
157 ms
50929244-9AF2-4146-A672-DB05E7D3435D.png
210 ms
3968ef8d-3013-40a8-86ac-38b48d1533a9_hero+banner.png
157 ms
c08a7cbf-219f-4a60-aad6-d0f8d09cdaba_Biostime_Seamless_Eating_2yo_Boy_882.png
105 ms
ee088903-83ea-45fb-8601-11289313a8ec_Biostime_AsSeenIn_1980x140_NEW_pinklogos-02.jpg
210 ms
6ac569b8-9aaf-45ed-a977-318491f195f9_Biostime_Seamless_6moBoy_VitD-1204x1250.png
106 ms
71c3c988-0b10-4324-aebe-a5983026aa1f_Girl_w_immuneDefense_824x1208.png
106 ms
a7460bcc-e517-4199-9423-31989f762c67_VitaminD_KidPacket_1204x1250.png
109 ms
9104aac3-64f6-44f7-940a-89590c2acd64_Biostime_Lifestyle_Kitchen_Vit-D_Mom-2mo-Boy_274._72dpi.jpg
209 ms
667c12fd-40b7-44ce-acff-f2a2fe45cdb7_Biostime_Lifestyle_On-the-Go_HMO_Mom-7mo-Girl_844.png
110 ms
3e0e27b2-bf4d-4ce0-9744-91d6a010fc07_Biostime_Lifestyle_Overhead_3mo-Boyandfather_9005.png
109 ms
aa631e1f-b321-4f0c-8105-c7de51d2480b_Biostime_Lifestyle_Vit-D_Kitchen_Mom-4yo-Girl_813.png
456 ms
18efb3b4-f9fa-47b2-92a0-ffffb2ffcb62_video+img.png
132 ms
Lato-Regular.ttf
72 ms
Lato-Light.ttf
88 ms
Lato-Bold.ttf
82 ms
app.js
135 ms
c0e50b95-d5c8-4fb2-83fd-20999bae4bfb.json
51 ms
location
117 ms
destination
62 ms
IBMPlexSans-Bold.ttf
48 ms
IBMPlexSans-Medium.ttf
55 ms
IBMPlexSans-Regular.ttf
48 ms
IBMPlexSans-Light.ttf
47 ms
otBannerSdk.js
34 ms
en.json
55 ms
otFlat.json
15 ms
otPcCenter.json
22 ms
otCommonStyles.css
23 ms
loader.js
112 ms
W43aoZLcUWj66cCBidtF3A.js
177 ms
19038.js
41 ms
deduplication.js
86 ms
device.js
49 ms
cart.js
59 ms
spr-0e683603bfa450170bff33e7fbad64e7dfe9585e1caeb951bbe283e5a2306523.js
23 ms
spr-07102fd76ff4bc22a3e0c32f0cca9ee51c77c34bbc4bdac79abb48f698de10dd.css
38 ms
jquery.min.js
4 ms
biostime.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
biostime.com 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
Browser errors were logged to the console
biostime.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
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 Biostime.com 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 Biostime.com 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.
biostime.com
Open Graph description is not detected on the main page of Biostime. 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: