5.8 sec in total
196 ms
5.5 sec
133 ms
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.comWe analyzed Evidence-of-harm.com page load time and found that the first response time was 196 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
evidence-of-harm.com performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value13.1 s
0/100
25%
Value11.5 s
5/100
10%
Value2,500 ms
4/100
30%
Value0.008
100/100
15%
Value16.2 s
5/100
10%
196 ms
51 ms
62 ms
59 ms
66 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Evidence-of-harm.com, 56% (22 requests) were made to Evidenceofharm.wpenginepowered.com and 15% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (432 ms) relates to the external source Youtube.com.
Page size can be reduced by 63.6 kB (14%)
465.5 kB
401.9 kB
In fact, the total size of Evidence-of-harm.com main page is 465.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. 50% of websites need less resources to load. CSS take 176.7 kB which makes up the majority of the site volume.
Potential reduce by 60.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 60.3 kB or 79% of the original size.
Potential reduce by 398 B
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. Evidence Of Harm images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 343 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. Evidence-of-harm.com has all CSS files already compressed.
Number of requests can be reduced by 15 (48%)
31
16
The browser has sent 31 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 5 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
evidence-of-harm.com
196 ms
style.min.css
51 ms
front_end_style.css
62 ms
dashicons.min.css
59 ms
desktop_style.css
66 ms
frontend.min.css
56 ms
plugins.css
171 ms
main.css
70 ms
media.css
78 ms
style.css
81 ms
ytprefs.min.css
80 ms
lity.min.css
82 ms
pJO1C_ELvKc
116 ms
NBFee_FKXTA
432 ms
www-player.css
13 ms
www-embed-player.js
29 ms
base.js
80 ms
bg.jpg
240 ms
nav-shadow.png
239 ms
nb-dots.png
240 ms
play-regular-webfont.woff
325 ms
play-bold-webfont.woff
325 ms
ad_status.js
279 ms
UCY5Klx_0fJhMytIltuKLUwnjJON9GWedkq6jjIrpW0.js
157 ms
embed.js
73 ms
OpenSans-Regular-webfont.woff
200 ms
OpenSans-Semibold-webfont.woff
118 ms
OpenSans-Bold-webfont.woff
201 ms
id
48 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
56 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
57 ms
Create
92 ms
Create
94 ms
0.jpg
226 ms
EOH-75x113.jpg
218 ms
stacy-case-FP-sm-90x60.jpg
340 ms
MSU-SHOWING-FLYER-PIC_V3-90x60.jpg
146 ms
GenerateIT
19 ms
GenerateIT
20 ms
evidence-of-harm.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
evidence-of-harm.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
evidence-of-harm.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Tap targets are not sized appropriately
EN
EN
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.
evidence-of-harm.com
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: