1.7 sec in total
346 ms
929 ms
417 ms
Click here to check amazing Fructose Mercola content for United States. Otherwise, check out these important facts you probably never knew about fructose.mercola.com
Read articles about fructose and educate yourself on the health risks linked to high fructose corn syrup (HFCS), a common cause of obesity.
Visit fructose.mercola.comWe analyzed Fructose.mercola.com page load time and found that the first response time was 346 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
fructose.mercola.com performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value8.8 s
1/100
25%
Value6.1 s
45/100
10%
Value1,140 ms
22/100
30%
Value0.453
20/100
15%
Value9.6 s
29/100
10%
346 ms
147 ms
77 ms
78 ms
108 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 11% of them (8 requests) were addressed to the original Fructose.mercola.com, 71% (50 requests) were made to Media.mercola.com and 3% (2 requests) were made to Privacy-policy.truste.com. The less responsive or slowest element that took the longest time to load (346 ms) belongs to the original domain Fructose.mercola.com.
Page size can be reduced by 884.8 kB (61%)
1.5 MB
569.2 kB
In fact, the total size of Fructose.mercola.com main page is 1.5 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 834.9 kB which makes up the majority of the site volume.
Potential reduce by 95.9 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 25.8 kB, which is 23% 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 95.9 kB or 84% of the original size.
Potential reduce by 16.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. Fructose Mercola images are well optimized though.
Potential reduce by 629.2 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 629.2 kB or 75% of the original size.
Potential reduce by 143.2 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. Fructose.mercola.com needs all CSS files to be minified and compressed as it can save up to 143.2 kB or 80% of the original size.
Number of requests can be reduced by 33 (49%)
68
35
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fructose Mercola. 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 12 to 1 for CSS and as a result speed up the page load time.
fructose.mercola.com
346 ms
jquery_all_min.js
147 ms
jquery.mmenu.min.all.js
77 ms
responsivescriptscs.js
78 ms
MercolaScript.js
108 ms
FBShare.js
84 ms
html5reset.css
84 ms
global.css
105 ms
mercola-common.css
105 ms
jquery-ui.css
110 ms
fbshare.css
107 ms
contentsearch.js
129 ms
mercola-blog.min.css
129 ms
mercola_s_code.js
223 ms
WebResource.axd
58 ms
WebResource.axd
91 ms
WebResource.axd
108 ms
WebResource.axd
69 ms
mercolascript.js
202 ms
asc
24 ms
getgeotrustsslseal
202 ms
1024.css
30 ms
image.gif
31 ms
text.gif
32 ms
js_visitor_settings.php
9 ms
768.css
51 ms
ga.js
42 ms
loadingDotDot.gif
44 ms
blue-seal-120-61-mercola-health-resources-llc-22002555.png
75 ms
23.gif
81 ms
seal
39 ms
v.gif
36 ms
loadingDotDot.gif
43 ms
loading6.gif
43 ms
loading1.gif
41 ms
mercola-logo-responsive.png
69 ms
menuicon.png
38 ms
search-icon.png
39 ms
613269.jpg
40 ms
spinach-egg-potato-recipe.jpg
65 ms
761420.jpg
65 ms
762086.jpg
66 ms
758454.jpg
66 ms
760121.jpg
66 ms
fructose.jpg
194 ms
742346.jpg
87 ms
sugar-alzheimers.jpg
87 ms
712799.jpg
97 ms
high-sugar-diet.jpg
99 ms
691863.jpg
100 ms
cancer-treatment.jpg
110 ms
669916.jpg
125 ms
beer-belly.jpg
126 ms
sucralose.jpg
127 ms
sugar-heart-disease.jpg
140 ms
fructose.png
191 ms
privacy-policy.gif
142 ms
__utm.gif
15 ms
Loginwww.aspx
83 ms
social_16.png
76 ms
nav-bg.gif
83 ms
cssprites.png
99 ms
s56053462924901
53 ms
partners-footer.png
47 ms
footerbg.png
48 ms
GetCSS.aspx
80 ms
cart-arrow.png
30 ms
480.css
30 ms
jquery.mmenu.all.css
29 ms
common_print.css
29 ms
fructose.mercola.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
[role]s are not contained by their required parent element
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
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.
fructose.mercola.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
Page has valid source maps
fructose.mercola.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fructose.mercola.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 Fructose.mercola.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.
fructose.mercola.com
Open Graph data is detected on the main page of Fructose Mercola. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: