3.3 sec in total
113 ms
2.2 sec
934 ms
Visit cedarcity.org now to see the best up-to-date Cedar City content for United States and also check out these interesting facts you probably never knew about cedarcity.org
In Cedar City, you will discover a unique community complete with world-renowned theatricals, astounding beauty, and unbelievable outdoor recreation.
Visit cedarcity.orgWe analyzed Cedarcity.org page load time and found that the first response time was 113 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cedarcity.org performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value33.9 s
0/100
25%
Value12.0 s
4/100
10%
Value3,160 ms
2/100
30%
Value0.179
68/100
15%
Value26.9 s
0/100
10%
113 ms
513 ms
54 ms
86 ms
133 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cedarcity.org, 33% (48 requests) were made to Static.cdninstagram.com and 30% (44 requests) were made to Cedarcityut.gov. The less responsive or slowest element that took the longest time to load (651 ms) relates to the external source Instagram.com.
Page size can be reduced by 143.8 kB (17%)
858.1 kB
714.3 kB
In fact, the total size of Cedarcity.org main page is 858.1 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. Only a small number of websites need less resources to load. Images take 583.9 kB which makes up the majority of the site volume.
Potential reduce by 112.2 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 112.2 kB or 79% of the original size.
Potential reduce by 15.4 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. Cedar City images are well optimized though.
Potential reduce by 14.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 14.2 kB or 11% of the original size.
Potential reduce by 1.9 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. Cedarcity.org needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 23% of the original size.
Number of requests can be reduced by 113 (79%)
143
30
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cedar City. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 92 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
cedarcity.org
113 ms
www.cedarcityut.gov
513 ms
gtm.js
54 ms
gtm.js
86 ms
antiforgery
133 ms
jquery-2.2.4.min.js
155 ms
jQuery-migrate-1.4.1.js
276 ms
-1542169068.css
302 ms
12034019.css
285 ms
248816995.js
318 ms
ai.0.js
16 ms
jquery.ui.autocomplete.min.js
273 ms
Search.js
277 ms
jquery-ui.css
282 ms
mlink2.php
189 ms
PausePlay.css
244 ms
1700977764.js
244 ms
Calendar.js
292 ms
jquery.urlToLink.min.js
291 ms
Carousel.jquery.js
292 ms
Easing.1.3.jquery.js
297 ms
widgets.js
149 ms
embed.js
127 ms
745732998.css
296 ms
APIClient.js
296 ms
Moment.min.js
379 ms
SplashModalRender.js
296 ms
-858844687.js
436 ms
monsido-script.js
123 ms
analytics.js
71 ms
js
49 ms
collect
90 ms
js
57 ms
Document
142 ms
Document
98 ms
Document
99 ms
Document
104 ms
Document
105 ms
Document
107 ms
Document
107 ms
Document
107 ms
Document
310 ms
Document
140 ms
Document
49 ms
Document
51 ms
Document
47 ms
Document
51 ms
Document
53 ms
Document
101 ms
Document
103 ms
Document
66 ms
page.php
138 ms
Document
48 ms
Document
50 ms
Document
47 ms
Document
51 ms
collect
22 ms
gtm.js
34 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
78 ms
651 ms
js
67 ms
Print.css
126 ms
FJBBthOOAnu.css
112 ms
EqENHDXc2ev.css
114 ms
VWDhCULazb5.js
117 ms
o1ndYS2og_B.js
113 ms
vxmlpLbAeCj.js
115 ms
Q-X-GXL_I_5.js
116 ms
_02W6YRik00.js
147 ms
p55HfXW__mM.js
147 ms
k_PjgALRjoR.js
149 ms
qJoe20iyDr0.js
150 ms
fbevents.js
191 ms
settings
241 ms
426388702_782919223880523_3136186125583852631_n.jpg
104 ms
245370750_234276395411478_3786288677549351802_n.jpg
100 ms
WvH29DbxtUI.js
59 ms
fsm1s6qUIdq.js
55 ms
qGoWo6gBwwP.png
56 ms
UXtr_j2Fwe-.png
54 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
23 ms
CedarCityUtah
59 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
23 ms
runtime-b1c52fd0a13ead5fcf6b.js
52 ms
modules-96ebc7ac3ad66d681a3d.js
75 ms
main-babd9234dc048fb47339.js
102 ms
_app-a9c9f1a99e4414675fb1.js
143 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
149 ms
_buildManifest.js
170 ms
_ssgManifest.js
169 ms
8526.0c32a8f0cfc5749221a3.js
23 ms
1755.07a49c40b12af4f75780.js
25 ms
8283.f3e5048cca7cef5eed7f.js
84 ms
3077.44bfeb00af01bc4020f6.js
86 ms
1362.42d432e02f7980bca032.js
84 ms
4956.c4e51ef593974b9db0bb.js
87 ms
5893.d500bd2a89ded806aa73.js
82 ms
XfNeoZ5rLk5.css
129 ms
VMdAky0tAYv.css
130 ms
ejCEEXst_lB.css
137 ms
OiPeUzjk3eY.css
150 ms
iOoFyEcGiMu.css
184 ms
lJsOCCfQB6_.css
149 ms
gm6v-wH2arK.css
148 ms
VWDhCULazb5.js
200 ms
JQEezzWid0-.js
15 ms
b8CBH3vdRbb.js
16 ms
qBOOjqn3JEw.js
15 ms
6mK5jwJ8oW7.js
17 ms
ZhQbWskHrxZ.js
18 ms
NU0ncUkttO1.js
18 ms
9lDiey1l9HS.js
19 ms
xIz98kCGgaY.js
19 ms
AqpJ2CmwRes.js
19 ms
SGr8zWOpJr7.js
21 ms
uFKL0y74aSV.js
21 ms
VMyzOV6gaWh.js
22 ms
kvRC87by9y5.js
22 ms
0yactC7tM6g.js
22 ms
x2riMh8tM9-.js
23 ms
jVvSDzaDazm.js
23 ms
SKdtG5PJSFi.js
23 ms
vi9cwTOL_Fz.js
64 ms
wGjokElNWDx.js
66 ms
ka9Hk6JvQfW.js
66 ms
ptMtj4pCDXT.js
66 ms
yT01VTZcHQ8.js
65 ms
exN2WIfEGm6.js
66 ms
xuRAzaLbJq0.js
67 ms
Zt0P0Kz5jRk.js
68 ms
J1VbMx8qJ8X.js
68 ms
_EtwxcySHCl.js
66 ms
WsNeyXWOlCI.js
67 ms
kUjETTwgpPt.js
68 ms
NI6i4mbNvFF.js
69 ms
DBI9VK4fP0I.js
72 ms
5-CNhD1hzUM.js
69 ms
HDiX03ZTkcn.js
68 ms
dNCX_imkiHA.js
71 ms
w6Umr3PkLo-.js
72 ms
BCQzaBLfyGr.js
65 ms
IbEU6o3x0eh.js
62 ms
KyCDJh5Z2FZ.js
63 ms
KJ_0RRuntSq.js
63 ms
wFyxcb5a_CA.png
62 ms
cedarcity.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-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
cedarcity.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
cedarcity.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Cedarcity.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 Cedarcity.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.
cedarcity.org
Open Graph description is not detected on the main page of Cedar City. 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: