11.1 sec in total
228 ms
10.3 sec
520 ms
Welcome to visittemplesquare.com homepage info - get ready to check Visittemplesquare best content right away, or after learning these important things about visittemplesquare.com
Salt Lake City's premier event space, located in the heart of Salt Lake City. The atmosphere at the Joseph Smith Memorial Building is impossible to match.
Visit visittemplesquare.comWe analyzed Visittemplesquare.com page load time and found that the first response time was 228 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
visittemplesquare.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value11.1 s
0/100
25%
Value7.7 s
24/100
10%
Value610 ms
49/100
30%
Value0.21
59/100
15%
Value11.6 s
18/100
10%
228 ms
1891 ms
58 ms
251 ms
303 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Visittemplesquare.com, 83% (99 requests) were made to Templesquare.com and 7% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source Templesquare.com.
Page size can be reduced by 1.3 MB (6%)
21.3 MB
20.0 MB
In fact, the total size of Visittemplesquare.com main page is 21.3 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. 60% of websites need less resources to load. Images take 20.3 MB which makes up the majority of the site volume.
Potential reduce by 69.3 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 69.3 kB or 85% of the original size.
Potential reduce by 592.3 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. Visittemplesquare images are well optimized though.
Potential reduce by 391.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 391.6 kB or 70% of the original size.
Potential reduce by 261.6 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. Visittemplesquare.com needs all CSS files to be minified and compressed as it can save up to 261.6 kB or 76% of the original size.
Number of requests can be reduced by 56 (54%)
104
48
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Visittemplesquare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
visittemplesquare.com
228 ms
www.templesquare.com
1891 ms
wp-emoji-release.min.js
58 ms
widget.css
251 ms
share.css
303 ms
genericons.css
1255 ms
style.css
1315 ms
jquery.fancybox-1.3.4.css
1259 ms
slick.css
109 ms
css
45 ms
css
62 ms
css
65 ms
dashicons.min.css
213 ms
temple-square-hospitality
267 ms
jquery.mmenu.all.css
302 ms
open-table-widget.min.css
324 ms
wpp.css
351 ms
wp-about-author.css
353 ms
jquery.js
425 ms
jquery-migrate.min.js
404 ms
jquery.sharrre.min.js
405 ms
core.min.js
456 ms
widget.min.js
457 ms
position.min.js
478 ms
mouse.min.js
510 ms
sortable.min.js
510 ms
datepicker.min.js
531 ms
menu.min.js
563 ms
autocomplete.min.js
563 ms
resizable.min.js
584 ms
draggable.min.js
616 ms
button.min.js
614 ms
dialog.min.js
636 ms
events-manager.js
669 ms
jquery.mmenu.min.all.js
668 ms
datepicker.min.js
688 ms
jquery.bootstrap-dropdown.min.js
720 ms
jquery.bootstrap-select.min.js
721 ms
open-table-widget.min.js
740 ms
jquery-ui.css
6 ms
css
78 ms
jquery-ui.js
11 ms
soliloquy.css
769 ms
comment-reply.min.js
769 ms
jquery.fancybox-1.3.4.pack.js
780 ms
fancybox-init.js
729 ms
slick.min.js
623 ms
slick-init.js
641 ms
623 ms
general.js
590 ms
tracking.js
635 ms
wp-embed.min.js
614 ms
soliloquy-min.js
591 ms
gfplaceholderaddon.js
640 ms
analytics.js
76 ms
logo.png
471 ms
collect
160 ms
temple-square.png
121 ms
temple-square-mini.png
121 ms
imageoverlay.png
122 ms
sliderimage2.jpg
388 ms
holder.gif
120 ms
bg-home-banner.jpg
172 ms
home-banner-salt-lake-city.png
173 ms
TSH-guide-ipad-216x300.png
386 ms
home-expore-slide-11-1600x486_c.jpg
775 ms
TempleSquare_1077-1600x486_c.jpg
651 ms
JSMB.jpg
535 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
73 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
163 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
107 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
113 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
113 ms
6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==
6 ms
G0-tvBxd4eQRdwFKB8dRkXMiQ8bx8R67TKBblDxZ-bQ.ttf
109 ms
9MkijrV-dEJ0-_NWV7E6N218GKU_F_kIyfK-gGC-Yzs.ttf
110 ms
2NBgzUtEeyB-Xtpr9bm1Cczai8e7xzqnKiVb1EwOy0E.ttf
108 ms
facebook.png
427 ms
twitter.png
425 ms
youtube.png
451 ms
googleplus.png
487 ms
instagram.png
485 ms
collect
93 ms
preloader.gif
452 ms
collect
243 ms
northVisitorCenter.jpg
242 ms
josephSmithMemorialBuilding.jpg
247 ms
conferenceCenter.jpg
366 ms
churchOfficeBuilding.jpg
327 ms
churchHistoryMuseum.jpg
571 ms
assemblyHall.jpg
699 ms
tabernacle.jpg
6385 ms
nativity.jpg
385 ms
southVisitorsCenter.jpg
652 ms
reflectingPool.jpg
593 ms
theRoof.jpg
956 ms
theGarden.jpg
645 ms
nauvooCafe.jpg
733 ms
lionHouse.jpg
719 ms
thePedestal.jpg
1563 ms
fancybox-x.png
749 ms
fancybox.png
772 ms
fancybox-y.png
784 ms
blank.gif
799 ms
AV100907cah0052-11.jpg
844 ms
451-1600x486_c.jpg
994 ms
sliderimage71.jpg
1005 ms
Y3V93602-1600x486_c.jpg
977 ms
Family-at-FHL-3662.jpg
1137 ms
sliderimage62.jpg
1046 ms
slider-dots.png
1037 ms
left-arrow.png
1032 ms
right-arrow.png
1049 ms
Pantry-1600x486_c.jpg
1144 ms
TempleSquare_623-1600x486_c.jpg
1307 ms
TempleSquare_857-1600x486_c.jpg
1071 ms
Lion-House-1600x486_c.png
2419 ms
TempleSquare_392-1600x486_c.jpg
1133 ms
Business-Events-1600x486_c.jpg
1212 ms
visittemplesquare.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
visittemplesquare.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
Missing source maps for large first-party JavaScript
visittemplesquare.com SEO score
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 Visittemplesquare.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 Visittemplesquare.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.
visittemplesquare.com
Open Graph data is detected on the main page of Visittemplesquare. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: