Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

evidence-of-harm.com

Evidence of Harm - The Hazards of Dental Mercury Amalgam Fillings - Evidence of Harm - The Hazards of Dental Mercury Amalgam Fillings

Page Load Speed

5.3 sec in total

First Response

617 ms

Resources Loaded

3.5 sec

Page Rendered

1.2 sec

evidence-of-harm.com screenshot

About Website

Click here to check amazing Evidence Of Harm content. Otherwise, check out these important facts you probably never knew about evidence-of-harm.com

Evidence of Harm examines the hazards of toxic mercury amalgam dental fillings to patients, dental staff and the global environment.

Visit evidence-of-harm.com

Key Findings

We analyzed Evidence-of-harm.com page load time and found that the first response time was 617 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

evidence-of-harm.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value16.6 s

0/100

10%

TBT (Total Blocking Time)

Value29,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.325

35/100

15%

TTI (Time to Interactive)

Value41.0 s

0/100

10%

Network Requests Diagram

evidence-of-harm.com

617 ms

04f132085c1cebb0bea7981fb933ebd3.css

1071 ms

pJO1C_ELvKc

119 ms

NBFee_FKXTA

755 ms

rocket-loader.min.js

33 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 11% of them (2 requests) were addressed to the original Evidence-of-harm.com, 39% (7 requests) were made to Youtube.com and 17% (3 requests) were made to 45jc291u4iuhx3nun1a264k1-wpengine.netdna-ssl.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 388.1 kB (64%)

Content Size

605.6 kB

After Optimization

217.5 kB

In fact, the total size of Evidence-of-harm.com main page is 605.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 484.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 52.1 kB

  • Original 63.4 kB
  • After minification 63.1 kB
  • After compression 11.3 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 52.1 kB or 82% of the original size.

JavaScript Optimization

-42%

Potential reduce by 24.3 kB

  • Original 57.9 kB
  • After minification 57.9 kB
  • After compression 33.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 24.3 kB or 42% of the original size.

CSS Optimization

-64%

Potential reduce by 311.7 kB

  • Original 484.2 kB
  • After minification 484.0 kB
  • After compression 172.6 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. Evidence-of-harm.com needs all CSS files to be minified and compressed as it can save up to 311.7 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (53%)

Requests Now

15

After Optimization

7

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evidence Of Harm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

evidence-of-harm.com accessibility score

65

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

evidence-of-harm.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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

evidence-of-harm.com SEO score

90

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

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

High

Tap targets are not sized appropriately

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 Evidence-of-harm.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 Evidence-of-harm.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 Evidence Of Harm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: