4 sec in total
33 ms
3.2 sec
758 ms
Visit citylifesf.com now to see the best up-to-date City Life SF content and also check out these interesting facts you probably never knew about citylifesf.com
Visit citylifesf.comWe analyzed Citylifesf.com page load time and found that the first response time was 33 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
citylifesf.com performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value110.6 s
0/100
25%
Value34.8 s
0/100
10%
Value730 ms
41/100
30%
Value0.01
100/100
15%
Value61.7 s
0/100
10%
33 ms
2782 ms
10 ms
14 ms
27 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 93% of them (69 requests) were addressed to the original Citylifesf.com, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Citylifesf.com.
Page size can be reduced by 191.2 kB (7%)
2.6 MB
2.4 MB
In fact, the total size of Citylifesf.com main page is 2.6 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 103.9 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 103.9 kB or 84% of the original size.
Potential reduce by 54.9 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. City Life SF images are well optimized though.
Potential reduce by 16.6 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 15.8 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. Citylifesf.com needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 15% of the original size.
Number of requests can be reduced by 46 (68%)
68
22
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of City Life SF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
citylifesf.com
33 ms
citylifesf.com
2782 ms
grid.min.css
10 ms
helper-parts.min.css
14 ms
main.min.css
27 ms
style.min.css
21 ms
theme.min.css
20 ms
frontend-lite.min.css
40 ms
post-5.css
25 ms
elementor-icons.min.css
17 ms
swiper.min.css
24 ms
frontend-lite.min.css
49 ms
global.css
22 ms
post-11.css
49 ms
post-233.css
52 ms
post-872.css
47 ms
general.min.css
51 ms
fontawesome.min.css
52 ms
solid.min.css
62 ms
brands.min.css
61 ms
jquery.min.js
60 ms
jquery-migrate.min.js
58 ms
js
164 ms
widget-nav-menu.min.css
59 ms
widget-carousel.min.css
98 ms
widget-icon-list.min.css
100 ms
post-509.css
96 ms
animations.min.css
98 ms
core.min.js
116 ms
main.min.js
122 ms
hello-frontend.min.js
118 ms
general.min.js
120 ms
jquery.smartmenus.min.js
118 ms
imagesloaded.min.js
120 ms
webpack.runtime.min.js
128 ms
frontend-modules.min.js
129 ms
waypoints.min.js
128 ms
frontend.min.js
132 ms
wp-polyfill-inert.min.js
130 ms
regenerator-runtime.min.js
133 ms
wp-polyfill.min.js
131 ms
hooks.min.js
121 ms
i18n.min.js
121 ms
elementor.js
121 ms
webpack-pro.runtime.min.js
117 ms
frontend.min.js
133 ms
elements-handlers.min.js
134 ms
fbevents.js
115 ms
City-Life-Church-Primary-Logo-Horizontal-White-RGB-800px@144ppi.png
102 ms
webvideo2022.gif
311 ms
2-1024x576.jpg
103 ms
Untitled-design-1024x576.jpeg
107 ms
Preachers-THUMBS-copy-1024x576.jpg
104 ms
City-Life-Church-Stories-1024x682.jpg
106 ms
City-Life-Church-Outreach-1024x682.jpg
176 ms
City-Life-Families-Home-Page-1024x683.jpg
109 ms
City-Life-Church-Groups-1024x682.jpg
110 ms
City-Life-Church-Logo-Lockup-3-White-RGB-800px@144ppi-1.png
109 ms
Get-Baptized-at-City-Life-Church-1024x1024.jpg
91 ms
Get-Involved-at-City-Life-Church-1024x1024.jpg
92 ms
Join-a-Group-at-City-Life-Church-1024x1024.jpg
155 ms
Visit-City-Life-Church-1024x1024.jpg
94 ms
City-Life-Kids-1024x1024.jpg
154 ms
Get-Prayer-at-City-Life-Church-1024x1024.jpg
155 ms
Next-Steps-at-City-Life-Church-1024x1024.jpg
154 ms
City-Life-Youth-1024x1024.jpg
156 ms
LED-Wall-final-.png
154 ms
oakes-grotesk-regular.woff
141 ms
oakes-grotesk-light.woff
142 ms
oakes-grotesk-bold.woff
144 ms
js
87 ms
analytics.js
80 ms
fa-brands-400.woff
48 ms
collect
20 ms
citylifesf.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
Links do not have a discernible name
citylifesf.com 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
citylifesf.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 Citylifesf.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 Citylifesf.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.
citylifesf.com
Open Graph description is not detected on the main page of City Life SF. 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: