Tools & Wizards About Us
gasp-pgh.org screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

gasp-pgh.org

Group Against Smog and Pollution | Allegheny County Air Quality | Pennsylvania

Page Load Speed

1.1 sec in total

First Response

127 ms

Resources Loaded

925 ms

Page Rendered

57 ms

gasp-pgh.org screenshot

About Website

Click here to check amazing Gasp Pgh content for United States. Otherwise, check out these important facts you probably never knew about gasp-pgh.org

Group Against Smog and Pollution (GASP) is a non-profit in southwestern PA working for a healthy, sustainable environment. Founded in 1969, GASP has been a diligent watchdog, educator, litigator & pol...

Visit gasp-pgh.org

Key Findings

We analyzed Gasp-pgh.org page load time and found that the first response time was 127 ms and then it took 982 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

gasp-pgh.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value1,910 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

www.gasp-pgh.org

127 ms

minified.js

43 ms

focus-within-polyfill.js

42 ms

polyfill.min.js

78 ms

7444.chunk.min.js

39 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gasp-pgh.org, 51% (29 requests) were made to Static.parastorage.com and 21% (12 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (355 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (62%)

Content Size

1.8 MB

After Optimization

670.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Gasp-pgh.org main page is 1.8 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. 55% of websites need less resources to load. HTML takes 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 1.0 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 231.4 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 1.0 MB or 82% of the original size.

Image Optimization

-12%

Potential reduce by 23.2 kB

  • Original 191.2 kB
  • After minification 168.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. Obviously, Gasp Pgh needs image optimization as it can save up to 23.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 48.1 kB

  • Original 319.0 kB
  • After minification 319.0 kB
  • After compression 270.8 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 48.1 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (45%)

Requests Now

31

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.gasp-pgh.org

www.gasp-pgh.org

127 ms

minified.js

minified.js

43 ms

focus-within-polyfill.js

focus-within-polyfill.js

42 ms

polyfill.min.js

polyfill.min.js

78 ms

7444.chunk.min.js

7444.chunk.min.js

39 ms

4261.chunk.min.js

4261.chunk.min.js

40 ms

576.chunk.min.js

576.chunk.min.js

71 ms

Calendar.chunk.min.js

Calendar.chunk.min.js

72 ms

thunderbolt-commons.60ed9a5a.bundle.min.js

thunderbolt-commons.60ed9a5a.bundle.min.js

149 ms

main.dda15fae.bundle.min.js

main.dda15fae.bundle.min.js

149 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

43 ms

lodash.min.js

lodash.min.js

44 ms

react.production.min.js

react.production.min.js

44 ms

react-dom.production.min.js

react-dom.production.min.js

150 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

149 ms

GASP_logo_Pantone_4color.jpg

GASP_logo_Pantone_4color.jpg

299 ms

bundle.min.js

bundle.min.js

81 ms

11062b_6da09ea096de408fa7bedf7cf31d71f3f000.jpg

11062b_6da09ea096de408fa7bedf7cf31d71f3f000.jpg

160 ms

be24dd_2a519333b9ea42e3a8755a661e01586b~mv2.webp

be24dd_2a519333b9ea42e3a8755a661e01586b~mv2.webp

219 ms

be24dd_d6fc4e02bfc04c5d92bc72e79cce55bc~mv2.webp

be24dd_d6fc4e02bfc04c5d92bc72e79cce55bc~mv2.webp

237 ms

be24dd_d6fc4e02bfc04c5d92bc72e79cce55bc~mv2.webp

be24dd_d6fc4e02bfc04c5d92bc72e79cce55bc~mv2.webp

193 ms

11062b_2954ecce9e6c4a4d9536bdf082a6f95f~mv2.webp

11062b_2954ecce9e6c4a4d9536bdf082a6f95f~mv2.webp

78 ms

11062b_2954ecce9e6c4a4d9536bdf082a6f95f~mv2.webp

11062b_2954ecce9e6c4a4d9536bdf082a6f95f~mv2.webp

192 ms

f3af33_d425e2174b4847439ec94759d43ad15b~mv2.webp

f3af33_d425e2174b4847439ec94759d43ad15b~mv2.webp

355 ms

b565ccc1941f4cdfb608c69b9cdb5f37.webp

b565ccc1941f4cdfb608c69b9cdb5f37.webp

192 ms

b565ccc1941f4cdfb608c69b9cdb5f37.webp

b565ccc1941f4cdfb608c69b9cdb5f37.webp

269 ms

11062b_153ac557900f4321a1f0d40beb96ee05~mv2.webp

11062b_153ac557900f4321a1f0d40beb96ee05~mv2.webp

193 ms

11062b_153ac557900f4321a1f0d40beb96ee05~mv2.webp

11062b_153ac557900f4321a1f0d40beb96ee05~mv2.webp

193 ms

139 ms

135 ms

136 ms

136 ms

134 ms

132 ms

190 ms

161 ms

164 ms

168 ms

187 ms

159 ms

c5749443-93da-4592-b794-42f28d62ef72.woff

c5749443-93da-4592-b794-42f28d62ef72.woff

26 ms

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

25 ms

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

12 ms

4021a3b9-f782-438b-aeb4-c008109a8b64.woff

4021a3b9-f782-438b-aeb4-c008109a8b64.woff

26 ms

b56b944e-bbe0-4450-a241-de2125d3e682.woff

b56b944e-bbe0-4450-a241-de2125d3e682.woff

26 ms

6f8d1983-4d34-4fa4-9110-988f6c495757.woff

6f8d1983-4d34-4fa4-9110-988f6c495757.woff

26 ms

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

26 ms

LuloCleanW05-OneBold.woff

LuloCleanW05-OneBold.woff

27 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

26 ms

AvenirLTW05-35Light.woff

AvenirLTW05-35Light.woff

26 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

20 ms

deprecation-style.v5.css

deprecation-style.v5.css

3 ms

right-arrow.svg

right-arrow.svg

14 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

4 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

Accessibility Review

gasp-pgh.org accessibility score

81

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-*] attributes do not match their roles

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

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

gasp-pgh.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

gasp-pgh.org SEO score

83

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

Links do not have descriptive text

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 Gasp-pgh.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 Gasp-pgh.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

gasp-pgh.org

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