1.5 sec in total
423 ms
913 ms
181 ms
Click here to check amazing Botanical Safety content. Otherwise, check out these important facts you probably never knew about botanical-safety.com
USBSL is a non-profit botanical testing laboratory for natural products industry supply chain stakeholders.
Visit botanical-safety.comWe analyzed Botanical-safety.com page load time and found that the first response time was 423 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 20% of websites can load faster.
botanical-safety.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value11.2 s
0/100
25%
Value9.0 s
14/100
10%
Value2,040 ms
7/100
30%
Value0.041
99/100
15%
Value13.7 s
10/100
10%
423 ms
35 ms
133 ms
75 ms
170 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 93% of them (41 requests) were addressed to the original Botanical-safety.com, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (423 ms) belongs to the original domain Botanical-safety.com.
Page size can be reduced by 581.0 kB (41%)
1.4 MB
844.8 kB
In fact, the total size of Botanical-safety.com main page is 1.4 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. 40% of websites need less resources to load. Javascripts take 650.4 kB which makes up the majority of the site volume.
Potential reduce by 16.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 2.5 kB, which is 11% 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 16.3 kB or 75% of the original size.
Potential reduce by 45.3 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. Botanical Safety images are well optimized though.
Potential reduce by 420.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 420.3 kB or 65% of the original size.
Potential reduce by 99.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. Botanical-safety.com needs all CSS files to be minified and compressed as it can save up to 99.1 kB or 85% of the original size.
Number of requests can be reduced by 26 (60%)
43
17
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Botanical Safety. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
botanical-safety.com
423 ms
djimageslider.css
35 ms
mootools-core.js
133 ms
core.js
75 ms
mootools-more.js
170 ms
jquery.min.js
127 ms
jquery-noconflict.js
72 ms
jquery-migrate.min.js
74 ms
jquery.easing.min.js
103 ms
slider.js
109 ms
system.css
113 ms
general.css
130 ms
template.css
253 ms
template.responsive.css
152 ms
jquery.js
228 ms
script.js
230 ms
script.responsive.js
159 ms
styles.css
229 ms
accordion.css
226 ms
jquery.min.js
40 ms
jquery.noconflict.js
226 ms
jquery.accordionlight.min.js
227 ms
system.css
27 ms
ga.js
92 ms
header.jpg
188 ms
menuseparator.png
69 ms
loader.gif
68 ms
slide1.jpg
71 ms
slide2.jpg
107 ms
slide3.jpg
71 ms
slide4x.jpg
141 ms
slide5.jpg
103 ms
slide6.jpg
73 ms
prev.png
103 ms
next.png
104 ms
play.png
116 ms
pause.png
120 ms
greenarrow.png
127 ms
facebook.png
128 ms
twitter.png
141 ms
youtube.png
147 ms
linkedin.png
151 ms
rss.png
155 ms
__utm.gif
11 ms
botanical-safety.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
botanical-safety.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
botanical-safety.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
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Botanical-safety.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Botanical-safety.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.
botanical-safety.com
Open Graph description is not detected on the main page of Botanical Safety. 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: