10.2 sec in total
3 sec
6.4 sec
852 ms
Click here to check amazing Standard Process content for United States. Otherwise, check out these important facts you probably never knew about standardprocess.com
Standard Process, from soil to supplement, creates high-quality, organic, whole food-based products for your body's nutritional needs.
Visit standardprocess.comWe analyzed Standardprocess.com page load time and found that the first response time was 3 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
standardprocess.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value24.0 s
0/100
25%
Value9.2 s
13/100
10%
Value2,560 ms
4/100
30%
Value0.051
99/100
15%
Value27.1 s
0/100
10%
2967 ms
620 ms
113 ms
151 ms
212 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 82% of them (59 requests) were addressed to the original Standardprocess.com, 6% (4 requests) were made to Google-analytics.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Standardprocess.com.
Page size can be reduced by 1.0 MB (52%)
2.0 MB
958.9 kB
In fact, the total size of Standardprocess.com main page is 2.0 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. 70% of websites need less resources to load. Javascripts take 819.7 kB which makes up the majority of the site volume.
Potential reduce by 49.8 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 12.8 kB, which is 20% 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 49.8 kB or 79% of the original size.
Potential reduce by 59.5 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. Standard Process images are well optimized though.
Potential reduce by 552.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 552.6 kB or 67% of the original size.
Potential reduce by 365.9 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. Standardprocess.com needs all CSS files to be minified and compressed as it can save up to 365.9 kB or 86% of the original size.
Number of requests can be reduced by 48 (72%)
67
19
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Standard Process. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
standardprocess.com
2967 ms
Home
620 ms
GetCSS.aspx
113 ms
GetResource.ashx
151 ms
ext-all-sp-theme.css
212 ms
ext-adjust.css
128 ms
font-awesome.min.css
155 ms
style.min.css
226 ms
MyFontsWebfontsKit.css
143 ms
modernizr.min.js
44 ms
ext.axd
649 ms
ext.axd
860 ms
ext.axd
714 ms
WebResource.axd
448 ms
ScriptResource.axd
450 ms
ScriptResource.axd
448 ms
jquery-1.6.2.min.js
416 ms
jquery-1.10.2.min.js
646 ms
jquery-ui-1.10.4-min.js
447 ms
jquery.fitvids.js
445 ms
hoverIntent.js
447 ms
transition.js
448 ms
tab.js
447 ms
collapse.js
448 ms
dropdown.js
457 ms
carousel.js
459 ms
modal.js
472 ms
affix.js
479 ms
rwd-table.js
478 ms
jquery.ezpz_hint.js
586 ms
jquery.textAreaCounter.js
599 ms
jquery.matchHeight-min.js
599 ms
jquery.easing.1.3.js
599 ms
jquery.touchSwipe.min.js
605 ms
responsive-tables.js
625 ms
snap.svg-min.js
641 ms
pizza.js
625 ms
app.js
610 ms
gyp7cxy.js
42 ms
jquery.blockUI.js
606 ms
2b3c3f
47 ms
ga.js
118 ms
__utm.gif
45 ms
analytics.js
186 ms
standard-process-quality-from-seed-to-supplement-w.png
63 ms
standard-process-quality-from-seed-to-supplement.png
58 ms
bottle-sp.png
354 ms
bottle-mh.png
777 ms
bottle-vet.png
1263 ms
GreenTier_rev_0k.png
57 ms
bbb-logo.png
139 ms
chooser-bg-featured3.jpg
452 ms
chooser-title-divide.gif
199 ms
chooser-bg-hcp.jpg
198 ms
chooser-bg-patients.jpg
280 ms
chooser-bg-pet-owners.jpg
275 ms
chooser-bg.png
189 ms
slider-triangle.png
273 ms
grid-rounded-rectangle.png
274 ms
collect
48 ms
2B3C3F_C_0.woff
333 ms
2B3C3F_8_0.woff
333 ms
fontawesome-webfont.woff
163 ms
fbds.js
96 ms
collect
90 ms
ts.js
224 ms
107 ms
tsr.js
231 ms
collect
219 ms
tip-sprite.gif
45 ms
tip-anchor-sprite.gif
41 ms
21 ms
standardprocess.com 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
[aria-*] attributes do not match their roles
[aria-*] attributes do not have valid values
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
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.
standardprocess.com 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
Missing source maps for large first-party JavaScript
standardprocess.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
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Standardprocess.com 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 Standardprocess.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.
standardprocess.com
Open Graph description is not detected on the main page of Standard Process. 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: