Tools & Wizards About Us
familyplace.org screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

familyplace.org

Home

Page Load Speed

3.2 sec in total

First Response

724 ms

Resources Loaded

2.1 sec

Page Rendered

389 ms

familyplace.org screenshot

About Website

Click here to check amazing Familyplace content for Thailand. Otherwise, check out these important facts you probably never knew about familyplace.org

Visit familyplace.org

Key Findings

We analyzed Familyplace.org page load time and found that the first response time was 724 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster. This domain responded with an error, which can significantly jeopardize Familyplace.org rating and web reputation

Performance Metrics

familyplace.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

familyplace.org

724 ms

jquery-1.7.2.min.js

379 ms

jquery.js

431 ms

menu.js

160 ms

usv3zsy.js

233 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 93% of them (53 requests) were addressed to the original Familyplace.org, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (993 ms) belongs to the original domain Familyplace.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 860.9 kB (39%)

Content Size

2.2 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Familyplace.org main page is 2.2 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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 96.6 kB

  • Original 131.1 kB
  • After minification 128.4 kB
  • After compression 34.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 96.6 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 26.8 kB

  • Original 1.0 MB
  • After minification 1.0 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. Familyplace images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 657.4 kB

  • Original 932.3 kB
  • After minification 900.2 kB
  • After compression 274.9 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 657.4 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 80.0 kB

  • Original 93.3 kB
  • After minification 70.4 kB
  • After compression 13.3 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. Familyplace.org needs all CSS files to be minified and compressed as it can save up to 80.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (53%)

Requests Now

55

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

familyplace.org

familyplace.org

724 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

379 ms

jquery.js

jquery.js

431 ms

menu.js

menu.js

160 ms

usv3zsy.js

usv3zsy.js

233 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

130 ms

common.css

common.css

207 ms

component.css

component.css

179 ms

ContentEditor.css

ContentEditor.css

199 ms

form.css

form.css

218 ms

slideshow.css

slideshow.css

238 ms

style.css

style.css

244 ms

style1.css

style1.css

256 ms

WebResource.axd

WebResource.axd

271 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

371 ms

ScriptResource.axd

ScriptResource.axd

289 ms

ScriptResource.axd

ScriptResource.axd

266 ms

ScriptResource.axd

ScriptResource.axd

313 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

550 ms

usv3zsy-d.css

usv3zsy-d.css

56 ms

p.gif

p.gif

132 ms

bag.png

bag.png

110 ms

capitalcampaign.png

capitalcampaign.png

250 ms

main_logo.png

main_logo.png

251 ms

circle_up.png

circle_up.png

167 ms

the-family-place-safety-shelter-and-hope-start-here.jpg

the-family-place-safety-shelter-and-hope-start-here.jpg

127 ms

2015-tfp-legacy-campaign628B73BC8729.jpg

2015-tfp-legacy-campaign628B73BC8729.jpg

334 ms

2013-fore-gof-and-tennis-tournament.jpg

2013-fore-gof-and-tennis-tournament.jpg

993 ms

thumb_04.gif

thumb_04.gif

253 ms

dot.gif

dot.gif

276 ms

unitedway.gif

unitedway.gif

379 ms

charity_logo.png

charity_logo.png

438 ms

twitter.gif

twitter.gif

455 ms

facebook.gif

facebook.gif

478 ms

connect.gif

connect.gif

499 ms

proximanova-reg-webfont.woff

proximanova-reg-webfont.woff

342 ms

button_bg_small.gif

button_bg_small.gif

384 ms

top_band2_bg.gif

top_band2_bg.gif

362 ms

home-banner2.jpg

home-banner2.jpg

507 ms

search_bg.gif

search_bg.gif

364 ms

dot_big.gif

dot_big.gif

385 ms

banner_bg.jpg

banner_bg.jpg

429 ms

home-banner1.jpg

home-banner1.jpg

455 ms

more2_bg.png

more2_bg.png

401 ms

stripe_bg.png

stripe_bg.png

415 ms

black.png

black.png

427 ms

more_bg.png

more_bg.png

443 ms

footer_light_bg.gif

footer_light_bg.gif

489 ms

submit_bg.png

submit_bg.png

468 ms

footer2_bg.gif

footer2_bg.gif

468 ms

home-banner3.jpg

home-banner3.jpg

341 ms

home-banner4.jpg

home-banner4.jpg

379 ms

home-banner5.jpg

home-banner5.jpg

347 ms

chaparralpro-regular-webfont.woff

chaparralpro-regular-webfont.woff

514 ms

ga.js

ga.js

7 ms

chaparralpro-bold-webfont.woff

chaparralpro-bold-webfont.woff

487 ms

__utm.gif

__utm.gif

64 ms

Accessibility Review

familyplace.org accessibility score

73

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

familyplace.org best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

familyplace.org SEO score

77

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familyplace.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Familyplace.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

familyplace.org

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