Access quackerywatch.com. Quackery Watch - Protecting the public when the government fails to take action against bogus produc...

quackerywatch.com screenshot

46

Performance

Renders faster than
65% of other websites
26

Accessibility

Visual factors better than
that of 18% of websites
58

Best Practices

More advanced features
available than in
19% of websites
50

SEO

Google-friendlier than
18% of websites

First Response

114 ms

Resources Loaded

10.3 sec

Page Rendered

5.2 sec

quackerywatch.com screenshot

About Website

Click here to check amazing Quackery Watch content. Otherwise, check out these important facts you probably never knew about quackerywatch.com

Protect yourself from quacks. Let QuackeryWatch helps you sift through the advertisements, the bad practitioners, and more.

Visit quackerywatch.com

Key Findings

We analyzed Quackerywatch.com page load time and found that the first response time was 114 ms and then it took 15.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value11.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

quackerywatch.com

114 ms

link-enhancer-common.js

9 ms

q

10 ms

QuackeryWatch%205.jpeg

187 ms

cm

187 ms

Our browser made a total of 205 requests to load all elements on the main page. We found that 9% of them (18 requests) were addressed to the original Quackerywatch.com, 44% (91 requests) were made to Rcm-na.amazon-adsystem.com and 24% (50 requests) were made to Fls-na.amazon-adsystem.com. The less responsive or slowest element that took the longest time to load (10 sec) relates to the external source Pigpills.com.

Content Size

777.7 kB

After Optimization

467.1 kB

In fact, the total size of Quackerywatch.com main page is 777.7 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. 45% of websites need less resources to load. Images take 388.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 294.8 kB

Original 388.8 kB
After minification 385.0 kB
After compression 94.0 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 294.8 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 15.8 kB

Original 388.9 kB
After minification 373.1 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. Quackery Watch images are well optimized though.

Requests Now

92

After Optimization

40

The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Quackery Watch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Quackerywatch.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 Quackerywatch.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

quackerywatch.com

Open Graph description is not detected on the main page of Quackery Watch. 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: