Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

fpasf.org

Financial Planning Association of San Francisco Bay Area

Page Load Speed

4.4 sec in total

First Response

606 ms

Resources Loaded

3 sec

Page Rendered

804 ms

fpasf.org screenshot

About Website

Visit fpasf.org now to see the best up-to-date Fpasf content and also check out these interesting facts you probably never knew about fpasf.org

The Financial Planning Association (FPA) is the membership association for nearly 30,000 CFP® professionals, financial planners, investment specialists and associated professionals. FPA of San Francis...

Visit fpasf.org

Key Findings

We analyzed Fpasf.org page load time and found that the first response time was 606 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

fpasf.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.366

29/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

www.fpasf.org

606 ms

ctf-styles.min.css

184 ms

wp_head.css

188 ms

events-manager.min.css

321 ms

cff-style.min.css

258 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 55% of them (45 requests) were addressed to the original Fpasf.org, 28% (23 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (606 ms) belongs to the original domain Fpasf.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 422.4 kB (22%)

Content Size

1.9 MB

After Optimization

1.5 MB

In fact, the total size of Fpasf.org main page is 1.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 663.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 408.1 kB

  • Original 468.3 kB
  • After minification 457.3 kB
  • After compression 60.2 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 408.1 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 10.3 kB

  • Original 663.4 kB
  • After minification 653.1 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. Fpasf images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.9 kB

  • Original 598.9 kB
  • After minification 598.9 kB
  • After compression 596.1 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 1.2 kB

  • Original 161.2 kB
  • After minification 161.1 kB
  • After compression 160.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. Fpasf.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (75%)

Requests Now

57

After Optimization

14

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

Accessibility Review

fpasf.org accessibility score

73

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

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

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

fpasf.org best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fpasf.org SEO score

78

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

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 Fpasf.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 Fpasf.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 Fpasf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: