Tools & Wizards About Us
reports.ewg.org screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

reports.ewg.org

Environmental Working Group – Giving Tuesday | Environmental Working Group

Page Load Speed

1.4 sec in total

First Response

67 ms

Resources Loaded

858 ms

Page Rendered

493 ms

reports.ewg.org screenshot

About Website

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

The Environmental Working Group is a nonprofit, nonpartisan organization dedicated to helping you live your healthiest life.

Visit reports.ewg.org

Key Findings

We analyzed Reports.ewg.org page load time and found that the first response time was 67 ms and then it took 1.4 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

reports.ewg.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

reports.ewg.org

67 ms

www.ewg.org

74 ms

bLMY4IbeO5Zdzi60Vrh0H1RYRxE.js

24 ms

js

71 ms

google_tag.script.js

92 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Reports.ewg.org, 62% (29 requests) were made to Ewg.org and 13% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (299 ms) relates to the external source Stats.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.1 kB (8%)

Content Size

828.1 kB

After Optimization

763.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Reports.ewg.org main page is 828.1 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. 55% of websites need less resources to load. Images take 569.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 64.8 kB

  • Original 85.0 kB
  • After minification 85.0 kB
  • After compression 20.1 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 64.8 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 569.0 kB
  • After minification 569.0 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. Reports Ewg images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 213 B

  • Original 136.1 kB
  • After minification 136.1 kB
  • After compression 135.9 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.

CSS Optimization

-0%

Potential reduce by 66 B

  • Original 38.0 kB
  • After minification 38.0 kB
  • After compression 38.0 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. Reports.ewg.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (63%)

Requests Now

40

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reports Ewg. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

reports.ewg.org

reports.ewg.org

67 ms

www.ewg.org

www.ewg.org

74 ms

bLMY4IbeO5Zdzi60Vrh0H1RYRxE.js

bLMY4IbeO5Zdzi60Vrh0H1RYRxE.js

24 ms

js

js

71 ms

google_tag.script.js

google_tag.script.js

92 ms

css_HUtI12DgD3ReeUn8RgnY3NSBPIbGCY6iyB5yGQ6rZm8.css

css_HUtI12DgD3ReeUn8RgnY3NSBPIbGCY6iyB5yGQ6rZm8.css

60 ms

css_FDR7ASNmQ_YT9K-KPswWM4jK10nq-HhTTVQ4an3QXzY.css

css_FDR7ASNmQ_YT9K-KPswWM4jK10nq-HhTTVQ4an3QXzY.css

62 ms

css_3QFAHGw8U4ct5JaoBcRhswaMNaLAY91_j8z67vBi274.css

css_3QFAHGw8U4ct5JaoBcRhswaMNaLAY91_j8z67vBi274.css

36 ms

wyp4ngq.css

wyp4ngq.css

111 ms

css_rFlTgcju-NwyG8AudSk-4-0hMDehLuoSzE9Nm5Aw-p0.css

css_rFlTgcju-NwyG8AudSk-4-0hMDehLuoSzE9Nm5Aw-p0.css

47 ms

2024_front_page_button_link_for_hero-20a4edd06f099314e95dd2b6ee32c610.css

2024_front_page_button_link_for_hero-20a4edd06f099314e95dd2b6ee32c610.css

58 ms

js_heY7Wge7RiXrBHeB6rHO4N-HmKv9TmsZlPu2VX7ChgY.js

js_heY7Wge7RiXrBHeB6rHO4N-HmKv9TmsZlPu2VX7ChgY.js

64 ms

js_JYo7Sx97AwSg6ObMr7HG6qev3OdIcni9QSwMw46yFGw.js

js_JYo7Sx97AwSg6ObMr7HG6qev3OdIcni9QSwMw46yFGw.js

88 ms

js_iZpAZvjhqX732SIDAQyc8u6Ur4GTNV2CtOPBqP4hkqw.js

js_iZpAZvjhqX732SIDAQyc8u6Ur4GTNV2CtOPBqP4hkqw.js

89 ms

at.js

at.js

57 ms

js_28j6I7S65N3jMzv2MRUvSJMKivaaPuoAf7rqKaEuYG4.js

js_28j6I7S65N3jMzv2MRUvSJMKivaaPuoAf7rqKaEuYG4.js

87 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

88 ms

AKWZXHJB

AKWZXHJB

102 ms

New-RepBan_PFASWater_2018.jpg

New-RepBan_PFASWater_2018.jpg

62 ms

chris-ralston-water-lemon.jpg

chris-ralston-water-lemon.jpg

80 ms

SunscreenGuideBlog.jpg

SunscreenGuideBlog.jpg

85 ms

2023ShoppersGuideBlog.jpg

2023ShoppersGuideBlog.jpg

80 ms

Stocksy_cosmetics_skindeep_woman_cream.jpg

Stocksy_cosmetics_skindeep_woman_cream.jpg

97 ms

CleanersBlog_0.jpg

CleanersBlog_0.jpg

156 ms

EWG_Banner_EnergySage_Header_C01.jpg

EWG_Banner_EnergySage_Header_C01.jpg

84 ms

EWG_CTA_Podcast_C01.jpg

EWG_CTA_Podcast_C01.jpg

92 ms

js

js

88 ms

analytics.js

analytics.js

19 ms

js

js

128 ms

p.css

p.css

127 ms

collect

collect

51 ms

shutterstock_2040670028%201.jpg

shutterstock_2040670028%201.jpg

68 ms

james-sutton-strawberries.jpg

james-sutton-strawberries.jpg

69 ms

arrow-right.svg

arrow-right.svg

65 ms

icon-facebook.svg

icon-facebook.svg

66 ms

icon-twitter.svg

icon-twitter.svg

63 ms

icon-youtube.svg

icon-youtube.svg

64 ms

icon-instagram.svg

icon-instagram.svg

150 ms

collect

collect

299 ms

bullet.svg

bullet.svg

258 ms

d

d

171 ms

d

d

198 ms

d

d

222 ms

gtm.js

gtm.js

86 ms

d

d

67 ms

d

d

67 ms

main.js

main.js

23 ms

Accessibility Review

reports.ewg.org accessibility score

86

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

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

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

Links do not have a discernible name

Best Practices

reports.ewg.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

reports.ewg.org SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Reports.ewg.org 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 Reports.ewg.org 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

reports.ewg.org

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