Tools & Wizards About Us
historiclondontown.org screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

historiclondontown.org

History Museum & Gardens | Historic London Town and Gardens | Edgewater Maryland

Page Load Speed

1.4 sec in total

First Response

91 ms

Resources Loaded

1.2 sec

Page Rendered

62 ms

historiclondontown.org screenshot

About Website

Visit historiclondontown.org now to see the best up-to-date Historic London Town content and also check out these interesting facts you probably never knew about historiclondontown.org

Just outside of Annapolis, MD, Historic London Town and Gardens reveals the "lost" colonial town of London and shares a garden sanctuary on the South River.

Visit historiclondontown.org

Key Findings

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

Performance Metrics

historiclondontown.org performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

www.historiclondontown.org

91 ms

minified.js

37 ms

focus-within-polyfill.js

35 ms

polyfill.min.js

34 ms

thunderbolt-commons.60ed9a5a.bundle.min.js

168 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Historiclondontown.org, 42% (22 requests) were made to Static.parastorage.com and 28% (15 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (361 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (64%)

Content Size

1.8 MB

After Optimization

640.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Historiclondontown.org main page is 1.8 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. 50% of websites need less resources to load. HTML takes 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 1.1 MB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 271.2 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 1.1 MB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 3.0 kB

  • Original 131.9 kB
  • After minification 128.8 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. Historic London Town images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.2 kB

  • Original 245.0 kB
  • After minification 244.9 kB
  • After compression 240.7 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 10 (34%)

Requests Now

29

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.historiclondontown.org

www.historiclondontown.org

91 ms

minified.js

minified.js

37 ms

focus-within-polyfill.js

focus-within-polyfill.js

35 ms

polyfill.min.js

polyfill.min.js

34 ms

thunderbolt-commons.60ed9a5a.bundle.min.js

thunderbolt-commons.60ed9a5a.bundle.min.js

168 ms

main.dda15fae.bundle.min.js

main.dda15fae.bundle.min.js

169 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

153 ms

lodash.min.js

lodash.min.js

168 ms

react.production.min.js

react.production.min.js

152 ms

react-dom.production.min.js

react-dom.production.min.js

155 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

168 ms

5618%20new.jpg

5618%20new.jpg

108 ms

bundle.min.js

bundle.min.js

90 ms

7a0d45_61e6cd256c1642c5afbfd67f9a4d4325~mv2.jpg

7a0d45_61e6cd256c1642c5afbfd67f9a4d4325~mv2.jpg

299 ms

7a0d45_1bfe2f1578cd46f68ba802a7bc325c70~mv2.jpg

7a0d45_1bfe2f1578cd46f68ba802a7bc325c70~mv2.jpg

223 ms

NastassiaParker_PromoPhoto.jpeg

NastassiaParker_PromoPhoto.jpeg

49 ms

IMG_20190322_125917.jpg

IMG_20190322_125917.jpg

361 ms

bar%20pic.jpg

bar%20pic.jpg

304 ms

7a0d45_e0dd976ae807486b87a7def774b95e56~mv2.jpg

7a0d45_e0dd976ae807486b87a7def774b95e56~mv2.jpg

197 ms

7a0d45_57297522844d469884aecdd12612148d~mv2.webp

7a0d45_57297522844d469884aecdd12612148d~mv2.webp

86 ms

7a0d45_57297522844d469884aecdd12612148d~mv2.webp

7a0d45_57297522844d469884aecdd12612148d~mv2.webp

87 ms

7a0d45_d3f416fc5023494bb9e6110a5f39eaa3~mv2.webp

7a0d45_d3f416fc5023494bb9e6110a5f39eaa3~mv2.webp

86 ms

7a0d45_d3f416fc5023494bb9e6110a5f39eaa3~mv2.webp

7a0d45_d3f416fc5023494bb9e6110a5f39eaa3~mv2.webp

87 ms

9e1553_c48a538df9e24705848f4c05b80c22a4~mv2.webp

9e1553_c48a538df9e24705848f4c05b80c22a4~mv2.webp

88 ms

9e1553_c48a538df9e24705848f4c05b80c22a4~mv2.webp

9e1553_c48a538df9e24705848f4c05b80c22a4~mv2.webp

89 ms

candid-seal-gold-2022.png

candid-seal-gold-2022.png

243 ms

128 ms

135 ms

130 ms

134 ms

128 ms

131 ms

164 ms

167 ms

165 ms

174 ms

172 ms

169 ms

file.woff

file.woff

192 ms

c5749443-93da-4592-b794-42f28d62ef72.woff

c5749443-93da-4592-b794-42f28d62ef72.woff

19 ms

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

20 ms

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

19 ms

aDjpMND83pDErGXlVEr-SRsxEYwM7FgeyaSgU71cLG0.woff

aDjpMND83pDErGXlVEr-SRsxEYwM7FgeyaSgU71cLG0.woff

8 ms

9VWMTeb5jtXkNoTv949NpRsxEYwM7FgeyaSgU71cLG0.woff

9VWMTeb5jtXkNoTv949NpRsxEYwM7FgeyaSgU71cLG0.woff

18 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

19 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

19 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

20 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

14 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

5 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

Accessibility Review

historiclondontown.org accessibility score

98

Accessibility Issues

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.

Best Practices

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

historiclondontown.org SEO score

89

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

historiclondontown.org

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