Tools & Wizards About Us
piin.org screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

piin.org

Pennsylvania Interfaith Impact Network | Moving people of faith into action

Page Load Speed

990 ms in total

First Response

63 ms

Resources Loaded

778 ms

Page Rendered

149 ms

piin.org screenshot

About Website

Click here to check amazing Piin content. Otherwise, check out these important facts you probably never knew about piin.org

Welcome to the Pennsylvania Interfaith Impact Network (PIIN). Through the processes of community-building, working with politicians and policy makers, direct action, and negotiation, we transform our ...

Visit piin.org

Key Findings

We analyzed Piin.org page load time and found that the first response time was 63 ms and then it took 927 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

piin.org performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

piin.org

63 ms

piin.org

92 ms

www.piin.org

143 ms

A.style.css,qver=4.7.11.pagespeed.cf.IxVfHgt72m.css

111 ms

css

30 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 46% of them (16 requests) were addressed to the original Piin.org, 43% (15 requests) were made to Fonts.gstatic.com and 11% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (354 ms) belongs to the original domain Piin.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.1 kB (1%)

Content Size

2.8 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Piin.org main page is 2.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. 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. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 28.1 kB

  • Original 36.9 kB
  • After minification 34.7 kB
  • After compression 8.8 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 28.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

  • Original 2.7 MB
  • After minification 2.6 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. Piin images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 45.3 kB
  • After minification 45.3 kB
  • After compression 45.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

-1%

Potential reduce by 374 B

  • Original 51.2 kB
  • After minification 51.2 kB
  • After compression 50.8 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. Piin.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (44%)

Requests Now

16

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

piin.org

piin.org

63 ms

piin.org

piin.org

92 ms

www.piin.org

www.piin.org

143 ms

A.style.css,qver=4.7.11.pagespeed.cf.IxVfHgt72m.css

A.style.css,qver=4.7.11.pagespeed.cf.IxVfHgt72m.css

111 ms

css

css

30 ms

css

css

48 ms

css

css

52 ms

css

css

54 ms

A.shortcodes.css,qver=3.0.23.pagespeed.cf.YKOctm_d0n.css

A.shortcodes.css,qver=3.0.23.pagespeed.cf.YKOctm_d0n.css

83 ms

A.shortcodes_responsive.css,qver=3.0.23.pagespeed.cf.gfG_ljpb3h.css

A.shortcodes_responsive.css,qver=3.0.23.pagespeed.cf.gfG_ljpb3h.css

94 ms

A.magnific_popup.css,qver=3.0.23.pagespeed.cf.WnJCcUqpb8.css

A.magnific_popup.css,qver=3.0.23.pagespeed.cf.WnJCcUqpb8.css

100 ms

jquery.js,qver=1.12.4.pagespeed.jm.pPCPAKkkss.js

jquery.js,qver=1.12.4.pagespeed.jm.pPCPAKkkss.js

107 ms

jquery-migrate.min.js,qver=1.4.1.pagespeed.jm.C2obERNcWh.js

jquery-migrate.min.js,qver=1.4.1.pagespeed.jm.C2obERNcWh.js

354 ms

jquery.magnific-popup.js,qver=3.0.23.pagespeed.jm.JWu3Qc75-z.js

jquery.magnific-popup.js,qver=3.0.23.pagespeed.jm.JWu3Qc75-z.js

152 ms

PIIN-Logo_test.png

PIIN-Logo_test.png

82 ms

1.png

1.png

95 ms

3.png

3.png

105 ms

4.png

4.png

97 ms

6.png

6.png

95 ms

wlp2gwHKFkZgtmSR3NB0oRJfbwhW.ttf

wlp2gwHKFkZgtmSR3NB0oRJfbwhW.ttf

20 ms

wlppgwHKFkZgtmSR3NB0oRJXsCxGDNNV.ttf

wlppgwHKFkZgtmSR3NB0oRJXsCxGDNNV.ttf

26 ms

wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNV.ttf

wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNV.ttf

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

36 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

38 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

56 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

55 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

55 ms

modules.ttf

modules.ttf

75 ms

jizaRExUiTo99u79P0U.ttf

jizaRExUiTo99u79P0U.ttf

56 ms

jizfRExUiTo99u79B_mh4Ok.ttf

jizfRExUiTo99u79B_mh4Ok.ttf

60 ms

Accessibility Review

piin.org accessibility score

79

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

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

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

piin.org best practices score

83

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

SEO Factors

piin.org SEO score

85

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

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

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

piin.org

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