Tools & Wizards About Us
templesquare.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

templesquare.com

Visit Historic Temple Square in Downtown Salt Lake City Utah

Page Load Speed

2.5 sec in total

First Response

181 ms

Resources Loaded

1.9 sec

Page Rendered

473 ms

templesquare.com screenshot

About Website

Welcome to templesquare.com homepage info - get ready to check Temple Square best content for United States right away, or after learning these important things about templesquare.com

Temple Square is a center of history and worship for The Church of Jesus Christ of Latter-day Saints. Come experience the gardens, architecture, and reverence of this iconic place.

Visit templesquare.com

Key Findings

We analyzed Templesquare.com page load time and found that the first response time was 181 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

templesquare.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

templesquare

181 ms

polyfills-c67a75d1b6f99dc8.js

17 ms

index.js

50 ms

ea88be26-43b75960b55a0567.js

34 ms

8581-9c4715ac732d1833.js

43 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Templesquare.com, 2% (1 request) were made to S.go-mpulse.net and 2% (1 request) were made to C.go-mpulse.net. The less responsive or slowest element that took the longest time to load (670 ms) relates to the external source Churchofjesuschrist.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.2 kB (44%)

Content Size

504.7 kB

After Optimization

284.5 kB

  • HTML
  • Images

In fact, the total size of Templesquare.com main page is 504.7 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. 50% of websites need less resources to load. Images take 253.1 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 220.1 kB

  • Original 251.6 kB
  • After minification 251.6 kB
  • After compression 31.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 220.1 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 56 B

  • Original 253.1 kB
  • After minification 253.1 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. Temple Square images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 29 (66%)

Requests Now

44

After Optimization

15

  • AJAX
  • Images
  • JavaScript

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Temple Square. 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.

Network Requests Diagram

templesquare

templesquare

181 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

17 ms

index.js

index.js

50 ms

ea88be26-43b75960b55a0567.js

ea88be26-43b75960b55a0567.js

34 ms

8581-9c4715ac732d1833.js

8581-9c4715ac732d1833.js

43 ms

1634-b830117cd7952369.js

1634-b830117cd7952369.js

32 ms

4148-63fedc5d66e24310.js

4148-63fedc5d66e24310.js

41 ms

6910-45ac18f3abbfb592.js

6910-45ac18f3abbfb592.js

41 ms

6671-af82fcc722d0bfc2.js

6671-af82fcc722d0bfc2.js

51 ms

3708-e6555ddc00515a5c.js

3708-e6555ddc00515a5c.js

47 ms

3054-1e9a586e5340c64c.js

3054-1e9a586e5340c64c.js

43 ms

992-0db989cb25996e7b.js

992-0db989cb25996e7b.js

46 ms

4855-a0279d4e6f0a104e.js

4855-a0279d4e6f0a104e.js

47 ms

1715-159344b5249770c6.js

1715-159344b5249770c6.js

46 ms

2025-2c86b8559c99465f.js

2025-2c86b8559c99465f.js

55 ms

1876-babb35c3564fbd8f.js

1876-babb35c3564fbd8f.js

54 ms

8292-b62f1b5ce4e8d272.js

8292-b62f1b5ce4e8d272.js

55 ms

6362-aa88c68e1bfa739d.js

6362-aa88c68e1bfa739d.js

60 ms

6253-83fca710904e4f11.js

6253-83fca710904e4f11.js

191 ms

6145-72bc5f315fe09bce.js

6145-72bc5f315fe09bce.js

59 ms

9733-744b1f9939486c9f.js

9733-744b1f9939486c9f.js

60 ms

9357-0c3e4597134fa145.js

9357-0c3e4597134fa145.js

63 ms

5256.998c4fb2f469379e.js

5256.998c4fb2f469379e.js

110 ms

webpack-d0530e54a42d3381.js

webpack-d0530e54a42d3381.js

79 ms

framework-5797de6f4a329144.js

framework-5797de6f4a329144.js

108 ms

main-d23531e3d8f4a5ef.js

main-d23531e3d8f4a5ef.js

81 ms

_app-c626706c5a6afdf3.js

_app-c626706c5a6afdf3.js

81 ms

router-451644a149da9850.js

router-451644a149da9850.js

101 ms

_buildManifest.js

_buildManifest.js

100 ms

_ssgManifest.js

_ssgManifest.js

99 ms

9UX54-L57TE-34QD8-DURP5-GFD2R

9UX54-L57TE-34QD8-DURP5-GFD2R

290 ms

default

default

278 ms

default

default

277 ms

default

default

277 ms

default

default

450 ms

default

default

428 ms

default

default

402 ms

default

default

277 ms

default

default

260 ms

default

default

268 ms

default

default

558 ms

default

default

268 ms

default

default

320 ms

default

default

670 ms

config.json

config.json

37 ms

Accessibility Review

templesquare.com accessibility score

94

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Definition list items are not wrapped in <dl> elements

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

[lang] attributes do not have a valid value

Best Practices

templesquare.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

templesquare.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Templesquare.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 Templesquare.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.

Social Sharing Optimization

templesquare.com

Open Graph data is detected on the main page of Temple Square. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: