Tools & Wizards About Us

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fructose.mercola.com

Fructose - Sweeteners and its Deadly Risks | Mercola.com

Page Load Speed

1.7 sec in total

First Response

346 ms

Resources Loaded

929 ms

Page Rendered

417 ms

About Website

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.com

Key Findings

We 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.

Performance Metrics

fructose.mercola.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.453

20/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 884.8 kB (61%)

Content Size

1.5 MB

After Optimization

569.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-84%

Potential reduce by 95.9 kB

  • Original 114.7 kB
  • After minification 88.9 kB
  • After compression 18.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.

Image Optimization

-5%

Potential reduce by 16.5 kB

  • Original 326.0 kB
  • After minification 309.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.

JavaScript Optimization

-75%

Potential reduce by 629.2 kB

  • Original 834.9 kB
  • After minification 718.0 kB
  • After compression 205.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 629.2 kB or 75% of the original size.

CSS Optimization

-80%

Potential reduce by 143.2 kB

  • Original 178.4 kB
  • After minification 174.1 kB
  • After compression 35.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.

Requests Breakdown

Number of requests can be reduced by 33 (49%)

Requests Now

68

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

fructose.mercola.com accessibility score

72

Accessibility Issues

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

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fructose.mercola.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fructose.mercola.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: