Tools & Wizards About Us
olmsted200.org screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

olmsted200.org

Olmsted Network

Page Load Speed

2.4 sec in total

First Response

112 ms

Resources Loaded

1.1 sec

Page Rendered

1.2 sec

olmsted200.org screenshot

About Website

Click here to check amazing Olmsted 200 content. Otherwise, check out these important facts you probably never knew about olmsted200.org

We are a diverse coalition of design professionals, historic property and park managers, scholars, citizen activists and representatives of numerous organizations around the United States dedicated to...

Visit olmsted200.org

Key Findings

We analyzed Olmsted200.org page load time and found that the first response time was 112 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

olmsted200.org performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value5.6 s

54/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.212

59/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

olmsted200.org

112 ms

olmsted.org

207 ms

style.min.css

33 ms

mediaelementplayer-legacy.min.css

37 ms

wp-mediaelement.min.css

51 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Olmsted200.org, 86% (37 requests) were made to Olmsted.org and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (448 ms) relates to the external source Olmsted.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 950.4 kB (5%)

Content Size

18.4 MB

After Optimization

17.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Olmsted200.org main page is 18.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 18.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 114.8 kB

  • Original 130.1 kB
  • After minification 94.8 kB
  • After compression 15.3 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. This page needs HTML code to be minified as it can gain 35.3 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 114.8 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 828.6 kB

  • Original 18.0 MB
  • After minification 17.2 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. Olmsted 200 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 525 B

  • Original 186.1 kB
  • After minification 186.1 kB
  • After compression 185.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.

CSS Optimization

-12%

Potential reduce by 6.5 kB

  • Original 53.0 kB
  • After minification 53.0 kB
  • After compression 46.5 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. Olmsted200.org needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (24%)

Requests Now

41

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

olmsted200.org

olmsted200.org

112 ms

olmsted.org

olmsted.org

207 ms

style.min.css

style.min.css

33 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

37 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

51 ms

pagenavi-css.css

pagenavi-css.css

44 ms

index.min.css

index.min.css

51 ms

glide.core.min.css

glide.core.min.css

57 ms

jetpack.css

jetpack.css

44 ms

index.min.js

index.min.js

80 ms

js

js

103 ms

e-202410.js

e-202410.js

41 ms

gtm.js

gtm.js

66 ms

logo.svg

logo.svg

32 ms

logo-green.svg

logo-green.svg

22 ms

search.svg

search.svg

27 ms

2020-May-6-Sheep-on-Pasture-SMW-1-Sarah-Webb.jpg

2020-May-6-Sheep-on-Pasture-SMW-1-Sarah-Webb.jpg

90 ms

Downing-gallery-2.jpg

Downing-gallery-2.jpg

28 ms

2-The-Italian-Garden-at-Coe-Hall.jpg

2-The-Italian-Garden-at-Coe-Hall.jpg

87 ms

s3.jpg

s3.jpg

50 ms

HillSideParkMap2-1.jpg

HillSideParkMap2-1.jpg

45 ms

Wentworth.Workday.Back-Bay-Fens-scaled-1.jpg

Wentworth.Workday.Back-Bay-Fens-scaled-1.jpg

88 ms

Slideshow_Hero_NoOverlay-scaled-1-1960x1060.jpg

Slideshow_Hero_NoOverlay-scaled-1-1960x1060.jpg

368 ms

Frederick_Law_Olmsted_National_Historical_Site_August_2005.jpg

Frederick_Law_Olmsted_National_Historical_Site_August_2005.jpg

92 ms

summerhouse_us_capitol.jpg

summerhouse_us_capitol.jpg

96 ms

stanford_oval_palm.jpg

stanford_oval_palm.jpg

99 ms

niagara_falls_state_park.jpg

niagara_falls_state_park.jpg

100 ms

Yosemite.jpg

Yosemite.jpg

94 ms

Biltmore.jpg

Biltmore.jpg

102 ms

transitional-wave.svg

transitional-wave.svg

104 ms

bg-trees.png

bg-trees.png

120 ms

FLO-Illustration-969x1024.png

FLO-Illustration-969x1024.png

103 ms

bg-topography.png

bg-topography.png

448 ms

Legacy_1160-1024x1024.jpg

Legacy_1160-1024x1024.jpg

118 ms

bg-trees-light.png

bg-trees-light.png

122 ms

ericallixrogers-naop-washpkmdw-32.jpg

ericallixrogers-naop-washpkmdw-32.jpg

119 ms

celebrate-advocate.svg

celebrate-advocate.svg

122 ms

share-your-story.svg

share-your-story.svg

124 ms

bg-topography-cream.png

bg-topography-cream.png

126 ms

Olmsted-Network_LAND_Main-2-2.png

Olmsted-Network_LAND_Main-2-2.png

126 ms

ON-awards_announce_02-980x700.jpg

ON-awards_announce_02-980x700.jpg

127 ms

Olmsted-birthday202_03-980x700.jpg

Olmsted-birthday202_03-980x700.jpg

128 ms

js

js

44 ms

Accessibility Review

olmsted200.org accessibility score

76

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

Best Practices

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

SEO Factors

olmsted200.org SEO score

92

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

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

olmsted200.org

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