Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

planning.org

American Planning Association

Page Load Speed

1.8 sec in total

First Response

53 ms

Resources Loaded

1.2 sec

Page Rendered

572 ms

planning.org screenshot

About Website

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

The largest membership organization of professional planners and planning resources available. Your leading authority on making great communities for all!

Visit planning.org

Key Findings

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

planning.org performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value5,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value31.4 s

0/100

10%

Network Requests Diagram

planning.org

53 ms

planning.org

134 ms

gtm.js

136 ms

adsbygoogle.js

245 ms

modernizr.js

53 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 37% of them (30 requests) were addressed to the original Planning.org, 23% (19 requests) were made to Planning-org-uploaded-media.s3.amazonaws.com and 14% (11 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (475 ms) relates to the external source Planning-org-uploaded-media.s3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 757.7 kB (26%)

Content Size

2.9 MB

After Optimization

2.1 MB

In fact, the total size of Planning.org main page is 2.9 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. Only a small number of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 126.4 kB

  • Original 142.9 kB
  • After minification 83.7 kB
  • After compression 16.5 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 59.2 kB, which is 41% 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 126.4 kB or 88% of the original size.

Image Optimization

-3%

Potential reduce by 43.4 kB

  • Original 1.6 MB
  • After minification 1.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. Planning images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 214.5 kB

  • Original 594.1 kB
  • After minification 578.6 kB
  • After compression 379.5 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 214.5 kB or 36% of the original size.

CSS Optimization

-77%

Potential reduce by 373.4 kB

  • Original 486.9 kB
  • After minification 485.1 kB
  • After compression 113.5 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. Planning.org needs all CSS files to be minified and compressed as it can save up to 373.4 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (54%)

Requests Now

71

After Optimization

33

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

Accessibility Review

planning.org accessibility score

89

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.

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

Links do not have a discernible name

Best Practices

planning.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

High

Page has valid source maps

SEO Factors

planning.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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planning.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 Planning.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 Planning. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: