4.3 sec in total
18 ms
3.6 sec
689 ms
Welcome to familyland.org homepage info - get ready to check Family Land best content right away, or after learning these important things about familyland.org
AFC: Our mission is providing Catholic family faith support by empowering you to create experiences that make the Faith come alive for your children.
Visit familyland.orgWe analyzed Familyland.org page load time and found that the first response time was 18 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
familyland.org performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value17.5 s
0/100
25%
Value17.1 s
0/100
10%
Value12,640 ms
0/100
30%
Value0.008
100/100
15%
Value22.0 s
1/100
10%
18 ms
158 ms
128 ms
55 ms
84 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Familyland.org, 75% (86 requests) were made to Afc.org and 12% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Koi-3qnioj0d1o.marketingautomation.services.
Page size can be reduced by 252.8 kB (22%)
1.2 MB
909.9 kB
In fact, the total size of Familyland.org main page is 1.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. 85% 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 468.4 kB which makes up the majority of the site volume.
Potential reduce by 188.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 188.4 kB or 86% of the original size.
Potential reduce by 5.0 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. Family Land images are well optimized though.
Potential reduce by 56.2 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 56.2 kB or 21% of the original size.
Potential reduce by 3.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. Familyland.org has all CSS files already compressed.
Number of requests can be reduced by 76 (82%)
93
17
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Family Land. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
familyland.org
18 ms
afc.org
158 ms
js
128 ms
wp-emoji-release.min.js
55 ms
select2.min.css
84 ms
iconfonts.css
89 ms
frontend.min.css
95 ms
tooltip.css
82 ms
tooltipster-sideTip-shadow.min.css
92 ms
featherlight.css
91 ms
css
167 ms
lity.min.css
176 ms
mec-general-calendar.css
163 ms
theme.css
167 ms
style.min.css
166 ms
wc-blocks-vendors-style.css
161 ms
wc-blocks-style.css
181 ms
deposit-form.min.css
177 ms
payment-plans.min.css
174 ms
front.min.css
174 ms
app.css
175 ms
integrity-light.css
187 ms
integrity-light.css
201 ms
style.css
208 ms
sv-wc-payment-gateway-payment-form.min.css
206 ms
wcwl_frontend.min.css
205 ms
dashicons.min.css
213 ms
frontend.css
215 ms
the-grid.css
208 ms
jquery.min.js
231 ms
jquery-migrate.min.js
229 ms
mec-general-calendar.js
399 ms
frontend.js
399 ms
events.js
399 ms
md5.js
250 ms
util.js
252 ms
frontend-gtag.min.js
400 ms
deposit-form.js
406 ms
js
66 ms
css
189 ms
imagesloaded.min.js
397 ms
masonry.min.js
362 ms
app.js
335 ms
email-decode.min.js
329 ms
core.min.js
330 ms
datepicker.min.js
330 ms
jquery.typewatch.js
295 ms
featherlight.js
447 ms
select2.full.min.js
442 ms
tooltip.js
441 ms
lity.min.js
440 ms
colorbrightness.min.js
437 ms
owl.carousel.min.js
433 ms
cs.6f62d0f.js
435 ms
jquery.blockUI.min.js
434 ms
add-to-cart.min.js
432 ms
js.cookie.min.js
433 ms
woocommerce.min.js
423 ms
cart-fragments.min.js
411 ms
x.js
410 ms
comment-reply.min.js
406 ms
jquery.payment.min.js
406 ms
sv-wc-payment-gateway-payment-form.js
404 ms
wc-authorize-net-cim.min.js
401 ms
wcwl_frontend.min.js
399 ms
wcwl_account.min.js
380 ms
effect.min.js
380 ms
the-grid-layout.js
363 ms
the-grid-slider.js
359 ms
js
352 ms
fbevents.js
461 ms
ss.js
1182 ms
analytics.js
920 ms
the-grid.js
355 ms
post-like.js
717 ms
wp-embed.min.js
353 ms
lazyload.min.js
353 ms
S6uyw4BMUTPHjxAwWw.ttf
842 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
1001 ms
fa-solid-900.woff
582 ms
fontawesome-webfont.woff
576 ms
fa-light-300.woff
838 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
1004 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
1003 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
1103 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
1103 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
1107 ms
S6u8w4BMUTPHjxsAUi-v.ttf
1103 ms
S6u_w4BMUTPHjxsI5wq_FQfo.ttf
1107 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
1102 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
1111 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
1112 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
1111 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
1110 ms
fa-brands-400.woff
577 ms
wARDj0u
6 ms
1799547910112443
447 ms
2022-AFC-Logo_Main_Whitev2.png
412 ms
Praying-Family-2.jpg
412 ms
HFF-crowd-nice2.jpg
411 ms
Mom-teaching-the-faith-to-her-kids-2.jpg
264 ms
mass-2.jpg
412 ms
Member-group-photov5.jpg
411 ms
mini-HFF-IL-thumbs-up.jpg
423 ms
4I5A5071-1-Alumni-Corps-and-Service-Corps-missionaries-at-Catholic-Familylandv3.jpg
531 ms
Webp.net-resizeimage-1.png
539 ms
HFLogo_500pxWide.png
533 ms
afc.org
1159 ms
collect
169 ms
2021-AFC-COVER-revised-final.jpg
273 ms
the_grid.ttf
270 ms
collect
282 ms
ga-audiences
61 ms
koi
82 ms
woocommerce-smallscreen.css
78 ms
familyland.org accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
familyland.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
familyland.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familyland.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 Familyland.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.
familyland.org
Open Graph data is detected on the main page of Family Land. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: