Tools & Wizards About Us
foundationsource.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

foundationsource.com

Your Partner in Giving - Foundation Source

Page Load Speed

4.5 sec in total

First Response

1.4 sec

Resources Loaded

2.6 sec

Page Rendered

449 ms

foundationsource.com screenshot

About Website

Click here to check amazing Foundation Source content for United States. Otherwise, check out these important facts you probably never knew about foundationsource.com

Foundation Source is the nation’s largest provider of support services & foundation software for private foundations and charitable advisors.

Visit foundationsource.com

Key Findings

We analyzed Foundationsource.com page load time and found that the first response time was 1.4 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

foundationsource.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value7,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

www.foundationsource.com

1402 ms

events.css

62 ms

bbpress.css

167 ms

style.css

116 ms

font-awesome.min.css

7 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 27% of them (16 requests) were addressed to the original Foundationsource.com, 15% (9 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Foundationsource.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (54%)

Content Size

1.9 MB

After Optimization

898.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foundationsource.com 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. 55% of websites need less resources to load. Javascripts take 855.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 33.3 kB

  • Original 44.5 kB
  • After minification 38.8 kB
  • After compression 11.1 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.7 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.3 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 6.7 kB

  • Original 479.0 kB
  • After minification 472.3 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. Foundation Source images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 538.6 kB

  • Original 855.4 kB
  • After minification 854.3 kB
  • After compression 316.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 538.6 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 455.5 kB

  • Original 553.7 kB
  • After minification 544.8 kB
  • After compression 98.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. Foundationsource.com needs all CSS files to be minified and compressed as it can save up to 455.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (58%)

Requests Now

43

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.foundationsource.com

www.foundationsource.com

1402 ms

events.css

events.css

62 ms

bbpress.css

bbpress.css

167 ms

style.css

style.css

116 ms

font-awesome.min.css

font-awesome.min.css

7 ms

css

css

25 ms

app.min.css

app.min.css

323 ms

jquery.min.js

jquery.min.js

218 ms

app.min.js

app.min.js

449 ms

fs-E10DoubleLookup_v2.js

fs-E10DoubleLookup_v2.js

101 ms

conversion.js

conversion.js

17 ms

loader.js

loader.js

74 ms

js_visitor_settings.php

js_visitor_settings.php

6 ms

dc.js

dc.js

67 ms

logo.png

logo.png

150 ms

chess1b.png

chess1b.png

220 ms

chess2b.png

chess2b.png

218 ms

logo_no_tag.png

logo_no_tag.png

143 ms

v.gif

v.gif

9 ms

gtm.js

gtm.js

65 ms

uAA9b29aBCI

uAA9b29aBCI

142 ms

iBanner.jpg

iBanner.jpg

225 ms

iBg1.gif

iBg1.gif

141 ms

iBg2.gif

iBg2.gif

143 ms

mountainBg.jpg

mountainBg.jpg

214 ms

generic

generic

61 ms

impl-1_22.js

impl-1_22.js

56 ms

__utm.gif

__utm.gif

39 ms

dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf

dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf

58 ms

y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf

y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf

102 ms

dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf

dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf

119 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

119 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

143 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

42 ms

gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf

gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf

142 ms

gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf

gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf

143 ms

bat.js

bat.js

42 ms

ytc.js

ytc.js

117 ms

112 ms

gtm.js

gtm.js

68 ms

uAA9b29aBCI

uAA9b29aBCI

96 ms

8Lo5MSPUdQw

8Lo5MSPUdQw

151 ms

elqCfg.min.js

elqCfg.min.js

91 ms

wcm

wcm

102 ms

analytics.js

analytics.js

49 ms

iframe_api

iframe_api

47 ms

60 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

86 ms

www-embed-player.js

www-embed-player.js

103 ms

svrGP

svrGP

127 ms

svrGP

svrGP

181 ms

appnexus

appnexus

15 ms

collect

collect

13 ms

www-widgetapi.js

www-widgetapi.js

48 ms

collect

collect

101 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

19 ms

ad_status.js

ad_status.js

62 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

67 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

78 ms

Accessibility Review

foundationsource.com accessibility score

69

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

foundationsource.com 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

foundationsource.com SEO score

82

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

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 Foundationsource.com 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 Foundationsource.com 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

foundationsource.com

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