Tools & Wizards About Us

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

pesticide.org

NCAP: Northwest Center for Alternatives to Pesticides

Page Load Speed

1.7 sec in total

First Response

86 ms

Resources Loaded

1.3 sec

Page Rendered

339 ms

About Website

Visit pesticide.org now to see the best up-to-date Pesticide content for United States and also check out these interesting facts you probably never knew about pesticide.org

Check out resources for alternatives to pesticides and join our campaigns to protect community and environmental health.

Visit pesticide.org

Key Findings

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

Performance Metrics

pesticide.org performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value2,400 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value1.056

2/100

15%

TTI (Time to Interactive)

Value26.3 s

0/100

10%

Network Requests Diagram

www.pesticide.org

86 ms

www.pesticide.org

201 ms

theme.scss

201 ms

tablet-and-desktop.scss

304 ms

jquery-ui.css

102 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 10% of them (5 requests) were addressed to the original Pesticide.org, 22% (11 requests) were made to Assets.nationbuilder.com and 18% (9 requests) were made to D3n8a8pro7vhmx.cloudfront.net. The less responsive or slowest element that took the longest time to load (452 ms) relates to the external source Platform.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.7 kB (3%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pesticide.org main page is 1.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 33.1 kB

  • Original 43.1 kB
  • After minification 37.6 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 5.4 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 33.1 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 13.7 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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. Pesticide images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 823 B

  • Original 322.1 kB
  • After minification 322.1 kB
  • After compression 321.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 110 B

  • Original 39.3 kB
  • After minification 39.3 kB
  • After compression 39.2 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. Pesticide.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (49%)

Requests Now

43

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

pesticide.org accessibility score

77

Accessibility Issues

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

Internationalization and localization

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

Impact

Issue

High

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

pesticide.org best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pesticide.org SEO score

86

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pesticide.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 Pesticide.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

Open Graph data is detected on the main page of Pesticide. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: