1.5 sec in total
62 ms
1.1 sec
341 ms
Click here to check amazing Fobfamily content. Otherwise, check out these important facts you probably never knew about fobfamily.com
A Christ-centered & Spirit-filled Non-Denominational Church, serving the Sarasota community for over 38 years
Visit fobfamily.comWe analyzed Fobfamily.com page load time and found that the first response time was 62 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
fobfamily.com performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value23.1 s
0/100
25%
Value8.0 s
21/100
10%
Value4,470 ms
0/100
30%
Value0.022
100/100
15%
Value23.8 s
1/100
10%
62 ms
60 ms
114 ms
161 ms
29 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 56% of them (73 requests) were addressed to the original Fobfamily.com, 25% (32 requests) were made to Fonts.gstatic.com and 6% (8 requests) were made to Fobfamily.churchcenter.com. The less responsive or slowest element that took the longest time to load (716 ms) relates to the external source Api.reftagger.com.
Page size can be reduced by 572.0 kB (24%)
2.4 MB
1.8 MB
In fact, the total size of Fobfamily.com main page is 2.4 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. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 393.0 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 393.0 kB or 84% of the original size.
Potential reduce by 17.7 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. Obviously, Fobfamily needs image optimization as it can save up to 17.7 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 161.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. This website has mostly compressed JavaScripts.
Potential reduce by 220 B
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. Fobfamily.com has all CSS files already compressed.
Number of requests can be reduced by 76 (84%)
91
15
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fobfamily. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
fobfamily.com
62 ms
fobfamily.com
60 ms
css
114 ms
js
161 ms
asp-pro-frontend.css
29 ms
asp-frontend.css
33 ms
all.css
47 ms
asp-media-player.css
41 ms
cookie-law-info-public.css
45 ms
cookie-law-info-gdpr.css
40 ms
front.min.css
43 ms
algolia-autocomplete.css
31 ms
jquery.qtip.min.css
41 ms
default-calendar-grid.min.css
44 ms
default-calendar-list.min.css
39 ms
style.css
39 ms
smartslider.min.css
42 ms
jquery.min.js
104 ms
jquery-migrate.min.js
57 ms
nfpluginsettings.js
56 ms
frontend-gtag.min.js
58 ms
cookie-law-info-public.js
59 ms
ie-compat.min.js
55 ms
tracker.js
58 ms
v1
54 ms
et-core-unified-30178.min.css
59 ms
n2.min.js
87 ms
smartslider-frontend.min.js
103 ms
ss-simple.min.js
88 ms
mediaelementplayer-legacy.min.css
87 ms
wp-mediaelement.min.css
87 ms
dashicons.min.css
101 ms
display-opinions-light.css
100 ms
font-awesome.min.css
98 ms
display-structure.css
98 ms
cookie-law-info-table.css
107 ms
front.min.js
107 ms
scripts.min.js
143 ms
smoothscroll.js
107 ms
jquery.fitvids.js
107 ms
easypiechart.js
106 ms
salvattore.js
130 ms
underscore.min.js
126 ms
wp-util.min.js
120 ms
algoliasearch-lite.umd.js
118 ms
autocomplete.min.js
117 ms
autocomplete-noconflict.js
149 ms
jquery.qtip.min.js
149 ms
default-calendar.min.js
144 ms
common.js
143 ms
litepicker.js
142 ms
asp-frontend.js
142 ms
fbevents.js
70 ms
imagesloaded.pkgd.min.js
139 ms
mediaelement-and-player.min.js
140 ms
mediaelement-migrate.min.js
136 ms
wp-mediaelement.min.js
135 ms
backbone.min.js
134 ms
front-end-deps.js
134 ms
front-end.js
147 ms
calendar
269 ms
embed
532 ms
reftagger.js
716 ms
widget.js
500 ms
et-divi-dynamic-tb-239107-tb-239108-30178-late.css
118 ms
front-end.js
171 ms
front-end.js
170 ms
full-logo-black-512.png
111 ms
cropped-corepic.jpg
233 ms
S6uyw4BMUTPHjxAwWA.woff
98 ms
S6uyw4BMUTPHjxAwWw.ttf
111 ms
S6u9w4BMUTPHh7USSwaPHw.woff
229 ms
S6u9w4BMUTPHh7USSwaPHA.ttf
235 ms
S6u8w4BMUTPHh30AUi-s.woff
234 ms
S6u8w4BMUTPHh30AUi-v.ttf
232 ms
S6u9w4BMUTPHh6UVSwaPHw.woff
236 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
230 ms
S6u9w4BMUTPHh50XSwaPHw.woff
233 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
235 ms
cropped-Globe-copy3-1.png
227 ms
app-icon-church-center-400.png
226 ms
Renewing-His-House.webp
229 ms
World-Views-copy-590x332.webp
222 ms
DSC00276-copy.webp
228 ms
app-icon-church-center-400-1.png
222 ms
logo-cookieyes.svg
222 ms
js
284 ms
church_center_web-2776d2302fe900b85c016dbc2fb8213e47c4b76cdd04dc391b5ac90500614d2b.css
243 ms
js
401 ms
api.js
357 ms
runtime-55a88b281efb71d77ca0.js
314 ms
180-0c7d4917b762b0ab27c9.js
283 ms
826-1a4468bfcdf5327a296f.js
353 ms
617-7e039223ccd37d7daea0.js
407 ms
971-690ba2b3a960e16b3d5a.js
282 ms
application-43967307293ff13be37a.js
375 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
251 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
251 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
251 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
250 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
250 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
250 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff
313 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf
311 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
312 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
311 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
311 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
311 ms
modules.woff
279 ms
fa-solid-900.woff
279 ms
fontawesome-webfont.woff
277 ms
fa-brands-400.woff
278 ms
fa-regular-400.woff
248 ms
S6u8w4BMUTPHjxsAUi-s.woff
354 ms
S6u8w4BMUTPHjxsAUi-v.ttf
354 ms
S6u_w4BMUTPHjxsI9w2_FQfr.woff
353 ms
S6u_w4BMUTPHjxsI9w2_FQfo.ttf
353 ms
S6u-w4BMUTPHjxsIPx-mPCQ.woff
352 ms
S6u-w4BMUTPHjxsIPx-mPCc.ttf
353 ms
S6u_w4BMUTPHjxsI5wq_FQfr.woff
373 ms
S6u_w4BMUTPHjxsI5wq_FQfo.ttf
373 ms
S6u_w4BMUTPHjxsI3wi_FQfr.woff
373 ms
S6u_w4BMUTPHjxsI3wi_FQfo.ttf
373 ms
js
313 ms
widget_app_base_1706274798459.js
96 ms
analytics.js
216 ms
js
116 ms
log
89 ms
recaptcha__en.js
88 ms
collect
78 ms
fobfamily.com accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fobfamily.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
fobfamily.com 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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fobfamily.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 Fobfamily.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.
fobfamily.com
Open Graph data is detected on the main page of Fobfamily. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: