Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

daytonhistoricdepot.org

Dayton Historical Depot Society - Museums in Dayton

Page Load Speed

1.4 sec in total

First Response

18 ms

Resources Loaded

953 ms

Page Rendered

431 ms

About Website

Click here to check amazing Dayton Historic Depot content. Otherwise, check out these important facts you probably never knew about daytonhistoricdepot.org

The Dayton Historical Depot Society is charged with maintaining two unique museums, as well as the Newland/Pioneer Cemetery.

Visit daytonhistoricdepot.org

Key Findings

We analyzed Daytonhistoricdepot.org page load time and found that the first response time was 18 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

daytonhistoricdepot.org performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.145

77/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

daytonhistoricdepot.org

18 ms

www.daytonhistoricdepot.org

49 ms

formidableforms.css

16 ms

select2.min.css

26 ms

iconfonts.css

39 ms

Our browser made a total of 146 requests to load all elements on the main page. We found that 92% of them (135 requests) were addressed to the original Daytonhistoricdepot.org, 3% (4 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (258 ms) belongs to the original domain Daytonhistoricdepot.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 283.2 kB (12%)

Content Size

2.4 MB

After Optimization

2.1 MB

In fact, the total size of Daytonhistoricdepot.org main page is 2.4 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 995.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 66.4 kB

  • Original 83.2 kB
  • After minification 81.2 kB
  • After compression 16.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 66.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 11 B

  • Original 995.0 kB
  • After minification 995.0 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. Dayton Historic Depot images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 133.3 kB

  • Original 827.1 kB
  • After minification 827.1 kB
  • After compression 693.8 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 133.3 kB or 16% of the original size.

CSS Optimization

-19%

Potential reduce by 83.5 kB

  • Original 445.1 kB
  • After minification 444.4 kB
  • After compression 361.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. Daytonhistoricdepot.org needs all CSS files to be minified and compressed as it can save up to 83.5 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 123 (88%)

Requests Now

139

After Optimization

16

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

Accessibility Review

daytonhistoricdepot.org accessibility score

78

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

daytonhistoricdepot.org SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

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

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

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