Tools & Wizards About Us
daytonhistoricdepot.org screenshot

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

daytonhistoricdepot.org screenshot

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 312.3 kB (13%)

Content Size

2.4 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

-19%

Potential reduce by 162.4 kB

  • Original 856.2 kB
  • After minification 856.2 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 162.4 kB or 19% 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

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

daytonhistoricdepot.org

daytonhistoricdepot.org

18 ms

www.daytonhistoricdepot.org

www.daytonhistoricdepot.org

49 ms

formidableforms.css

formidableforms.css

16 ms

select2.min.css

select2.min.css

26 ms

iconfonts.css

iconfonts.css

39 ms

frontend.min.css

frontend.min.css

62 ms

tooltip.css

tooltip.css

35 ms

tooltipster-sideTip-shadow.min.css

tooltipster-sideTip-shadow.min.css

55 ms

featherlight.css

featherlight.css

35 ms

css

css

59 ms

lity.min.css

lity.min.css

34 ms

mec-general-calendar.css

mec-general-calendar.css

41 ms

superfish.css

superfish.css

47 ms

jquery.qtip.css

jquery.qtip.css

43 ms

style.css

style.css

44 ms

event_template.css

event_template.css

171 ms

responsive.css

responsive.css

57 ms

css

css

51 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

54 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

50 ms

style.css

style.css

88 ms

font-awesome.min.css

font-awesome.min.css

94 ms

style.min.css

style.min.css

89 ms

style.css

style.css

156 ms

dripicons.css

dripicons.css

91 ms

kiko-all.css

kiko-all.css

97 ms

font-awesome-5.min.css

font-awesome-5.min.css

98 ms

stylesheet.min.css

stylesheet.min.css

106 ms

print.css

print.css

158 ms

timetable-schedule.min.css

timetable-schedule.min.css

156 ms

timetable-schedule-responsive.min.css

timetable-schedule-responsive.min.css

159 ms

style_dynamic.css

style_dynamic.css

188 ms

responsive.min.css

responsive.min.css

159 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

157 ms

js_composer.min.css

js_composer.min.css

170 ms

css

css

82 ms

core-dashboard.min.css

core-dashboard.min.css

166 ms

qode-quick-links.min.css

qode-quick-links.min.css

168 ms

jquery.min.js

jquery.min.js

207 ms

jquery-migrate.min.js

jquery-migrate.min.js

217 ms

js

js

257 ms

rs6.css

rs6.css

218 ms

mec-general-calendar.js

mec-general-calendar.js

216 ms

tooltip.js

tooltip.js

207 ms

frontend.js

frontend.js

199 ms

events.js

events.js

197 ms

rbtools.min.js

rbtools.min.js

198 ms

rs6.min.js

rs6.min.js

198 ms

core.min.js

core.min.js

192 ms

datepicker.min.js

datepicker.min.js

214 ms

jquery.typewatch.js

jquery.typewatch.js

212 ms

featherlight.js

featherlight.js

221 ms

select2.full.min.js

select2.full.min.js

207 ms

lity.min.js

lity.min.js

206 ms

colorbrightness.min.js

colorbrightness.min.js

206 ms

owl.carousel.min.js

owl.carousel.min.js

205 ms

tabs.min.js

tabs.min.js

176 ms

jquery.qtip.min.js

jquery.qtip.min.js

172 ms

jquery.ba-bbq.min.js

jquery.ba-bbq.min.js

172 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

257 ms

timetable.js

timetable.js

258 ms

accordion.min.js

accordion.min.js

251 ms

menu.min.js

menu.min.js

204 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

197 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

197 ms

wp-polyfill.min.js

wp-polyfill.min.js

198 ms

dom-ready.min.js

dom-ready.min.js

198 ms

hooks.min.js

hooks.min.js

198 ms

i18n.min.js

i18n.min.js

194 ms

a11y.min.js

a11y.min.js

192 ms

autocomplete.min.js

autocomplete.min.js

191 ms

controlgroup.min.js

controlgroup.min.js

190 ms

checkboxradio.min.js

checkboxradio.min.js

175 ms

button.min.js

button.min.js

158 ms

mouse.min.js

mouse.min.js

147 ms

resizable.min.js

resizable.min.js

145 ms

draggable.min.js

draggable.min.js

145 ms

dialog.min.js

dialog.min.js

144 ms

droppable.min.js

droppable.min.js

144 ms

progressbar.min.js

progressbar.min.js

144 ms

selectable.min.js

selectable.min.js

145 ms

sortable.min.js

sortable.min.js

142 ms

slider.min.js

slider.min.js

143 ms

spinner.min.js

spinner.min.js

121 ms

tooltip.min.js

tooltip.min.js

121 ms

effect.min.js

effect.min.js

121 ms

effect-blind.min.js

effect-blind.min.js

121 ms

effect-bounce.min.js

effect-bounce.min.js

120 ms

effect-clip.min.js

effect-clip.min.js

120 ms

effect-drop.min.js

effect-drop.min.js

123 ms

effect-explode.min.js

effect-explode.min.js

122 ms

effect-fade.min.js

effect-fade.min.js

118 ms

effect-fold.min.js

effect-fold.min.js

119 ms

effect-highlight.min.js

effect-highlight.min.js

117 ms

ga.js

ga.js

161 ms

effect-pulsate.min.js

effect-pulsate.min.js

77 ms

effect-size.min.js

effect-size.min.js

76 ms

effect-scale.min.js

effect-scale.min.js

72 ms

effect-shake.min.js

effect-shake.min.js

80 ms

effect-slide.min.js

effect-slide.min.js

73 ms

effect-transfer.min.js

effect-transfer.min.js

71 ms

doubletaptogo.js

doubletaptogo.js

117 ms

modernizr.min.js

modernizr.min.js

72 ms

jquery.appear.js

jquery.appear.js

73 ms

hoverIntent.min.js

hoverIntent.min.js

74 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

70 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

73 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

73 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

72 ms

jquery.waitforimages.js

jquery.waitforimages.js

70 ms

jquery.form.min.js

jquery.form.min.js

107 ms

waypoints.min.js

waypoints.min.js

67 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

67 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

66 ms

jquery.isotope.min.js

jquery.isotope.min.js

104 ms

skrollr.js

skrollr.js

102 ms

TweenLite.min.js

TweenLite.min.js

102 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

101 ms

smoothPageScroll.min.js

smoothPageScroll.min.js

105 ms

default_dynamic.js

default_dynamic.js

104 ms

default.min.js

default.min.js

102 ms

comment-reply.min.js

comment-reply.min.js

102 ms

js_composer_front.min.js

js_composer_front.min.js

100 ms

qode-like.min.js

qode-like.min.js

103 ms

jquery.mCustomScrollbar.min.js

jquery.mCustomScrollbar.min.js

100 ms

qode-quick-links.min.js

qode-quick-links.min.js

101 ms

dhds_logo_transWHT.png

dhds_logo_transWHT.png

112 ms

dhds_logo_darkSM.png

dhds_logo_darkSM.png

99 ms

dhds_logo_lightSM.png

dhds_logo_lightSM.png

109 ms

dhds_logo_transSM.png

dhds_logo_transSM.png

108 ms

font

font

136 ms

font

font

150 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

102 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

114 ms

boldman_home_banner.jpg

boldman_home_banner.jpg

66 ms

dummy.png

dummy.png

76 ms

boldman_sign-1.jpg

boldman_sign-1.jpg

97 ms

dayton_guard.jpg

dayton_guard.jpg

97 ms

cemetary_headstone-1.jpg

cemetary_headstone-1.jpg

95 ms

dhds_logo_darkSM_WHT.png

dhds_logo_darkSM_WHT.png

95 ms

top-footer-overlay.png

top-footer-overlay.png

106 ms

__utm.gif

__utm.gif

53 ms

font

font

114 ms

font

font

58 ms

fbevents.js

fbevents.js

149 ms

footer-top-overlay-1.png

footer-top-overlay-1.png

33 ms

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

daytonhistoricdepot.org

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: