8.9 sec in total
1.8 sec
5.9 sec
1.3 sec
Welcome to cfci.net homepage info - get ready to check Cfci best content right away, or after learning these important things about cfci.net
Cape Fear Center For Inquiry Wilmington NC NOTE: FAMILY PICNIC & MOVIE NIGHT MOVED to 9/26 My Hot Lunchbox WELCOME TO CFCI The Cape Fear Center ...
Visit cfci.netWe analyzed Cfci.net page load time and found that the first response time was 1.8 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
cfci.net performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value10.1 s
0/100
25%
Value7.9 s
23/100
10%
Value3,110 ms
2/100
30%
Value0.322
36/100
15%
Value18.5 s
3/100
10%
1766 ms
169 ms
114 ms
168 ms
176 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 86% of them (51 requests) were addressed to the original Cfci.net, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Cfci.net.
Page size can be reduced by 547.5 kB (63%)
862.6 kB
315.1 kB
In fact, the total size of Cfci.net main page is 862.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. CSS take 477.3 kB which makes up the majority of the site volume.
Potential reduce by 36.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 36.4 kB or 77% of the original size.
Potential reduce by 2.8 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. Cfci images are well optimized though.
Potential reduce by 124.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 124.2 kB or 62% of the original size.
Potential reduce by 384.1 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. Cfci.net needs all CSS files to be minified and compressed as it can save up to 384.1 kB or 80% of the original size.
Number of requests can be reduced by 46 (87%)
53
7
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cfci. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
cfci.net
1766 ms
analytics.js
169 ms
wp-emoji-release.min.js
114 ms
style.min.css
168 ms
theme.min.css
176 ms
all.min.css
125 ms
v4-shims.min.css
132 ms
settings.css
102 ms
22204-layout.css
124 ms
styles.css
118 ms
bootstrap.min.css
132 ms
fusion-bootstrap.css
155 ms
fusion-core.css
176 ms
wpcmscf7-public.css
202 ms
style.min.css
201 ms
wp_shopping_cart_style.css
173 ms
0a471cdc0df460d1b8c68db28f135fe9-layout-bundle.css
175 ms
gallery.min.css
202 ms
dashicons.min.css
193 ms
thickbox.css
212 ms
jquery.magnificpopup.min.css
197 ms
skin-5e62973accecc.css
204 ms
style.css
202 ms
animate.min.css
214 ms
css
111 ms
frontend.min.js
232 ms
jquery.js
238 ms
jquery-migrate.min.js
229 ms
wpcmscf7-public.js
211 ms
script.min.js
223 ms
jquery.easy-ticker.min.js
224 ms
imagesloaded.min.js
226 ms
style.css
228 ms
css
127 ms
style.css
412 ms
22204-layout.js
288 ms
bootstrap.min.js
226 ms
modernizr-3.3.1-respond-1.4.2.min.js
286 ms
imagesloaded.pkgd.min.js
412 ms
api.js
190 ms
fusion-core.js
283 ms
collect
17 ms
jquery.ba-throttle-debounce.min.js
213 ms
c229fe74d9b75dc614880f7bcce822e4-layout-bundle.js
305 ms
script.js
305 ms
thickbox.js
188 ms
jquery.magnificpopup.min.js
310 ms
theme.min.js
299 ms
wp-embed.min.js
288 ms
logo-2.jpg
133 ms
pixel.png
132 ms
QGY2z_kZZAGCONcK2A4bGOj0I_1Y5tj1.woff
162 ms
fa-solid-900.woff
56 ms
fa-regular-400.woff
55 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff
161 ms
fa-brands-400.woff
57 ms
recaptcha__en.js
148 ms
body-bg.jpg
296 ms
loadingAnimation.gif
22 ms
cfci.net 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
cfci.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cfci.net 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
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 Cfci.net 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 Cfci.net 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.
cfci.net
Open Graph description is not detected on the main page of Cfci. 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: