5.7 sec in total
45 ms
4.4 sec
1.2 sec
Visit cityteam.org now to see the best up-to-date City Team content for United States and also check out these interesting facts you probably never knew about cityteam.org
CityTeam is a community united by the belief that God has called us to love our neighbors as ourselves. It’s a place where all are welcome, and where everyone from volunteers to donors and staff all p...
Visit cityteam.orgWe analyzed Cityteam.org page load time and found that the first response time was 45 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cityteam.org performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value15.1 s
0/100
25%
Value9.4 s
12/100
10%
Value2,860 ms
3/100
30%
Value0.806
5/100
15%
Value22.8 s
1/100
10%
45 ms
78 ms
2253 ms
76 ms
58 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Cityteam.org, 25% (31 requests) were made to Cdn.prod.website-files.com and 10% (12 requests) were made to Uploads-ssl.webflow.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Cityteam.org.
Page size can be reduced by 159.9 kB (1%)
15.0 MB
14.9 MB
In fact, the total size of Cityteam.org main page is 15.0 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. Only a small number of websites need less resources to load. Images take 14.2 MB which makes up the majority of the site volume.
Potential reduce by 103.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 103.4 kB or 84% of the original size.
Potential reduce by 43.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. City Team images are well optimized though.
Potential reduce by 10.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 2.5 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. Cityteam.org has all CSS files already compressed.
Number of requests can be reduced by 63 (66%)
96
33
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of City Team. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
cityteam.org
45 ms
cityteam.org
78 ms
www.cityteam.org
2253 ms
cityteam-main.webflow.db800b36f.css
76 ms
webfont.js
58 ms
js
105 ms
js
158 ms
jquery-3.5.1.min.dc5e7f18c8.js
60 ms
webflow.0046dea99.js
152 ms
js.cookie.min.js
70 ms
cmslibrary-v1.8.js
68 ms
jquery.pjax.min.js
99 ms
css
147 ms
488acf20-fddb-48af-8a99-1c925261e272.js
401 ms
65428a73db8e12303ff72be1_CT_Logo_White.svg
267 ms
6415c390b071a7dffb6b0e63_CT-Heart-2.svg
270 ms
6417930ebabae40ac1f713f1_CT-Web-43.jpg
404 ms
6417b56c61e2deb2171d3d17_Play%20Button.svg
319 ms
6417b4b221beabbf37e3da76_CT-Web-34.jpg
406 ms
6413babd50fd806ffed0a67c_Food.svg
313 ms
6413babdeb1179b684ec9b1e_Cycle.svg
320 ms
653eaec48967ec186557236e_Clothing-2.svg
317 ms
641b82abc347050f969142d6_down%20arrow-2.svg
329 ms
641901827798d684f3bbe396_arrow_2.svg
328 ms
6418f60bd9d751c4714ae9c9_CT-Web-26.png
343 ms
651c538ea26cc0e306db823e_51744042695_ce21dd785f_o%20(1).png
344 ms
6418f60aca3dd1ec919e62c6_CT-Web-14.png
397 ms
6418f60be5bc0a7e7b10a6a4_CT-Web-7.png
401 ms
641f32071971459b881abccc_Pin-orange.svg
374 ms
6504e4d4ffd1d227c09fa7ca_Select_a_city._SJ_GET_HELP.jpg
400 ms
641baed986e019523b5f6c83_CT-Web-44.png
405 ms
641b9c10683a58ac0aa9dc3f_CT-Web-50.png
545 ms
641b9c23945322cf7598a7e4_CT-Web-52.png
551 ms
641b8b47834f154a5a449562_CT-Web-group%202-16.jpg
540 ms
641f0e817a03b9cfc86adbaa_CT-Web-group-2-10.png
553 ms
641f0f12b0bfffb90ee61199_CT-Web-group-2-26sq.png
546 ms
6415bd49f4c83f0573eebb37_CityTeam%20Logo-blue.svg
541 ms
66a962383e48e29d1c5efcef_453143791_1275853216722297_376106028459228132_n.jpeg
549 ms
66a179d56210bcb9f76fe862_452073351_926440409248556_7994035782228602608_n.jpeg
555 ms
669ed964b0de449368b6ec34_452061962_903535978200909_2980699333963392775_n.jpeg
556 ms
6698070f6a58511b7b51f822_451106045_998752785080005_440789320289165200_n.jpeg
559 ms
652c7c60e51ee095a897a73d_logo.svg
554 ms
background-image.svg
159 ms
641f09aaa274e515f9348de3_CT-Web-41-crop.png
343 ms
6413855a61522a5499cfb05c_ClarityCity-Regular.otf
114 ms
6413852f6a913b324ab04d82_ClarityCity-Bold.otf
114 ms
64126a85104a840dd6558c9c_line-square-icons.woff
127 ms
64126a85104a84a1c4558c5a_line-rounded-icons.woff
124 ms
641384977a0f905242bef9f8_futura-pt-bold-589e44b6aacd3.otf
155 ms
641384e892dd4d4043fa670d_futura-pt-heavy-589a6dd12187e.otf
174 ms
641385030e9aba3012f2e312_futura-pt-medium-589e45b956de4.otf
151 ms
641384f95a0db4de28e70d2f_futura-pt-light-589a6e187563a.otf
152 ms
64138467f7351255decfe08c_futura-condensed-pt-medium-589e44ed1e3a5.otf
176 ms
xfu00W3wXn3QLUJXhzq42AHivA.ttf
122 ms
xfu20W3wXn3QLUJXhzq42ATSu5_a.ttf
146 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRSW3z.ttf
177 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxRSW3z.ttf
178 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZtRSW3z.ttf
176 ms
64126a85104a840008558c6e_social-icon-font.woff
114 ms
smiXUvwGScmz.js
247 ms
fbevents.js
162 ms
track.js
565 ms
ppms.js
71 ms
264 ms
rudder-analytics.min.js
200 ms
telemetry.js
157 ms
core.js
197 ms
up_loader.1.1.0.js
192 ms
669145eda0c274d3ef5db3e8_ctm-fye-homepage.jpg
136 ms
script.js
359 ms
events.js
265 ms
js
104 ms
ndp.js
412 ms
zcpt.js
190 ms
uwt.js
191 ms
tfa.js
209 ms
669145c27b094877156b0dea_cctm-fye-desktop.jpg
181 ms
ppms.php
72 ms
71 ms
json
51 ms
trackpoint-async.js
105 ms
adsct
106 ms
adsct
151 ms
main.MTc2ZTRjM2Y4MA.js
18 ms
65 ms
cds-pips.js
51 ms
eid.es5.js
52 ms
pips.taboola.com
26 ms
13 ms
17 ms
pixels
47 ms
339 ms
user-registering
233 ms
29729
306 ms
usermatch.gif
20 ms
pixel
258 ms
Pug
249 ms
cs
311 ms
um
254 ms
1536774609659206262
527 ms
285 ms
put
226 ms
33302
359 ms
match
38 ms
gdpr_consent=
46 ms
generic
39 ms
rum
59 ms
xuid
39 ms
match
58 ms
164 ms
pixel
39 ms
152 ms
match
34 ms
match
30 ms
sd
20 ms
pixel.gif
151 ms
38 ms
v1
34 ms
setuid
34 ms
pixel.gif
297 ms
pixel
20 ms
11 ms
generic
5 ms
13 ms
p
70 ms
3.gif
95 ms
cityteam.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
cityteam.org 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
cityteam.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Cityteam.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 Cityteam.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.
cityteam.org
Open Graph data is detected on the main page of City Team. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: