Tools & Wizards About Us
parkcityhistory.org screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

parkcityhistory.org

Park City Museum | Preserving, protecting and promoting Park City's history & heritage.

Page Load Speed

2.5 sec in total

First Response

179 ms

Resources Loaded

1.3 sec

Page Rendered

1.1 sec

parkcityhistory.org screenshot

About Website

Click here to check amazing Park City History content for United States. Otherwise, check out these important facts you probably never knew about parkcityhistory.org

Discover Park City’s fascinating past at the Park City Museum. Plan Your Visit › See All Events Current Tozer Gallery Exhibit February 3, 2021 – April 4…

Visit parkcityhistory.org

Key Findings

We analyzed Parkcityhistory.org page load time and found that the first response time was 179 ms and then it took 2.4 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

parkcityhistory.org performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

parkcityhistory.org

179 ms

index.css

77 ms

tribe-events-pro-mini-calendar-block.min.css

92 ms

dashicons.min.css

118 ms

variables-skeleton.min.css

92 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 78% of them (62 requests) were addressed to the original Parkcityhistory.org, 8% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (531 ms) belongs to the original domain Parkcityhistory.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 187.7 kB (6%)

Content Size

3.1 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Parkcityhistory.org main page is 3.1 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. 70% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 171.5 kB

  • Original 257.3 kB
  • After minification 251.9 kB
  • After compression 85.8 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 171.5 kB or 67% of the original size.

Image Optimization

-1%

Potential reduce by 16.0 kB

  • Original 2.8 MB
  • After minification 2.7 MB

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. Park City History images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 122 B

  • Original 36.7 kB
  • After minification 36.7 kB
  • After compression 36.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.

Requests Breakdown

Number of requests can be reduced by 53 (73%)

Requests Now

73

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Park City History. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

parkcityhistory.org

parkcityhistory.org

179 ms

index.css

index.css

77 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

92 ms

dashicons.min.css

dashicons.min.css

118 ms

variables-skeleton.min.css

variables-skeleton.min.css

92 ms

variables-full.min.css

variables-full.min.css

95 ms

common-skeleton.min.css

common-skeleton.min.css

96 ms

common-full.min.css

common-full.min.css

100 ms

tickets.min.css

tickets.min.css

113 ms

rsvp-v1.min.css

rsvp-v1.min.css

116 ms

tickets.min.css

tickets.min.css

120 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

121 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

123 ms

2-layout.css

2-layout.css

135 ms

wdgk-front-style.css

wdgk-front-style.css

142 ms

screen.css

screen.css

142 ms

css

css

67 ms

sv-wc-payment-gateway-payment-form.min.css

sv-wc-payment-gateway-payment-form.min.css

156 ms

rsvp.min.css

rsvp.min.css

157 ms

wootickets.min.css

wootickets.min.css

159 ms

animate.min.css

animate.min.css

159 ms

css

css

85 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

165 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

166 ms

wp-polyfill.min.js

wp-polyfill.min.js

167 ms

hooks.min.js

hooks.min.js

168 ms

w.js

w.js

47 ms

jquery.min.js

jquery.min.js

172 ms

jquery-migrate.min.js

jquery-migrate.min.js

185 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

189 ms

add-to-cart.min.js

add-to-cart.min.js

188 ms

js.cookie.min.js

js.cookie.min.js

189 ms

woocommerce.min.js

woocommerce.min.js

190 ms

s-202422.js

s-202422.js

46 ms

jquery.payment.min.js

jquery.payment.min.js

191 ms

sv-wc-payment-gateway-payment-form.js

sv-wc-payment-gateway-payment-form.js

201 ms

wc-first-data-payeezy-gateway-payment-form.min.js

wc-first-data-payeezy-gateway-payment-form.min.js

203 ms

6a7cb3278e.js

6a7cb3278e.js

100 ms

wc-blocks.css

wc-blocks.css

207 ms

rsvp.min.js

rsvp.min.js

278 ms

ticket-details.min.js

ticket-details.min.js

279 ms

e-202422.js

e-202422.js

3 ms

jquery.deparam.js

jquery.deparam.js

278 ms

jquery.cookie.min.js

jquery.cookie.min.js

264 ms

attendees-list.min.js

attendees-list.min.js

249 ms

meta.min.js

meta.min.js

247 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

245 ms

js_cookie.js

js_cookie.js

242 ms

2-layout.js

2-layout.js

238 ms

wdgk-front-script.js

wdgk-front-script.js

282 ms

sourcebuster.min.js

sourcebuster.min.js

278 ms

order-attribution.min.js

order-attribution.min.js

282 ms

app.js

app.js

275 ms

wc-quantity-increment.js

wc-quantity-increment.js

279 ms

g.gif

g.gif

21 ms

analytics.js

analytics.js

140 ms

search-white.svg

search-white.svg

144 ms

MegaMine.jpg

MegaMine.jpg

438 ms

pcm-video-placeholder.jpg

pcm-video-placeholder.jpg

351 ms

library_optimized.jpg

library_optimized.jpg

434 ms

oral-history_optimized.jpg

oral-history_optimized.jpg

436 ms

archives_optimized.jpg

archives_optimized.jpg

531 ms

speed-limit.jpg

speed-limit.jpg

436 ms

Digi-2-6006-714x1024.jpg

Digi-2-6006-714x1024.jpg

436 ms

IMG_0241-480x300.jpg

IMG_0241-480x300.jpg

435 ms

2002-26-206-480x300.jpg

2002-26-206-480x300.jpg

529 ms

2004-19-2220-480x300.jpg

2004-19-2220-480x300.jpg

528 ms

boilerpoint-gondola-1024x860.jpg

boilerpoint-gondola-1024x860.jpg

529 ms

MuckersandMillionaires2.jpg

MuckersandMillionaires2.jpg

531 ms

restauranttaxlogo2_201505071437422364-scaled.jpg

restauranttaxlogo2_201505071437422364-scaled.jpg

529 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilXs1UgIfM0qi1e.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilXs1UgIfM0qi1e.ttf

430 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVilXs1UgIfM0qi1e.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GVilXs1UgIfM0qi1e.ttf

379 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5Xs1UgIfM0qi1e.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5Xs1UgIfM0qi1e.ttf

379 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqh8ndeY9Z4.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqh8ndeY9Z4.ttf

306 ms

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mfWc3ZyRTQ.ttf

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mfWc3ZyRTQ.ttf

255 ms

pe1kMImSLYBIv1o4X1M8cce4OdVisMz5nZRqy6cmmmU3t2FQWEAEOvV9wNvrwlNstMKW3Y6K5WMwXeVy3GboJ0kTHmqP92UnK_cWrgVc85s.ttf

pe1kMImSLYBIv1o4X1M8cce4OdVisMz5nZRqy6cmmmU3t2FQWEAEOvV9wNvrwlNstMKW3Y6K5WMwXeVy3GboJ0kTHmqP92UnK_cWrgVc85s.ttf

290 ms

collect

collect

186 ms

g.gif

g.gif

175 ms

collect

collect

61 ms

js

js

109 ms

Accessibility Review

parkcityhistory.org accessibility score

86

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

parkcityhistory.org best practices score

92

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

Page has valid source maps

SEO Factors

parkcityhistory.org SEO score

90

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

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

High

Tap targets are not sized appropriately

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 Parkcityhistory.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 Parkcityhistory.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.

Social Sharing Optimization

parkcityhistory.org

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