Tools & Wizards About Us
casewatch.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

casewatch.org

Casewatch | Quackwatch

Page Load Speed

962 ms in total

First Response

161 ms

Resources Loaded

568 ms

Page Rendered

233 ms

casewatch.org screenshot

About Website

Welcome to casewatch.org homepage info - get ready to check Casewatch best content for United States right away, or after learning these important things about casewatch.org

About Casewatch About Us Mission Statement Frequently Asked Questions General Information Strengths and Weaknesses of Our Laws (link to Quackwatch) Enforcement Actions Criminal Prosecutions FDA Warnin...

Visit casewatch.org

Key Findings

We analyzed Casewatch.org page load time and found that the first response time was 161 ms and then it took 801 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

casewatch.org performance score

0

Network Requests Diagram

casewatch.org

161 ms

quackwatch.css

27 ms

buttons.js

6 ms

HONConduct305115_s.gif

377 ms

getAllAppDefault.esi

108 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 24% of them (5 requests) were addressed to the original Casewatch.org, 10% (2 requests) were made to Wd-edge.sharethis.com and 10% (2 requests) were made to T.sharethis.com. The less responsive or slowest element that took the longest time to load (377 ms) relates to the external source Honcode.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.3 kB (69%)

Content Size

191.5 kB

After Optimization

59.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Casewatch.org main page is 191.5 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. Only 10% of websites need less resources to load. Javascripts take 148.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 16.0 kB

  • Original 21.9 kB
  • After minification 20.4 kB
  • After compression 5.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. 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 16.0 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 23 B

  • Original 18.4 kB
  • After minification 18.4 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. Casewatch images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 114.4 kB

  • Original 148.7 kB
  • After minification 148.7 kB
  • After compression 34.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 114.4 kB or 77% of the original size.

CSS Optimization

-73%

Potential reduce by 1.9 kB

  • Original 2.5 kB
  • After minification 2.0 kB
  • After compression 676 B

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. Casewatch.org needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (39%)

Requests Now

18

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Casewatch. 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.

Network Requests Diagram

casewatch.org

casewatch.org

161 ms

quackwatch.css

quackwatch.css

27 ms

buttons.js

buttons.js

6 ms

HONConduct305115_s.gif

HONConduct305115_s.gif

377 ms

getAllAppDefault.esi

getAllAppDefault.esi

108 ms

duck.jpg

duck.jpg

17 ms

fp_logotype.gif

fp_logotype.gif

18 ms

Count.cgi

Count.cgi

59 ms

getSegment.php

getSegment.php

10 ms

checkOAuth.esi

checkOAuth.esi

5 ms

t.dhj

t.dhj

9 ms

t.dhj

t.dhj

14 ms

cm

cm

42 ms

s-3271.xgi

s-3271.xgi

26 ms

hbpix

hbpix

27 ms

7 ms

10 ms

pixel

pixel

23 ms

xrefid.xgi

xrefid.xgi

10 ms

pixel

pixel

19 ms

2981

2981

22 ms

SEO Factors

casewatch.org SEO score

0

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 Casewatch.org 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 Casewatch.org 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

casewatch.org

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