Tools & Wizards About Us
monolake.org screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

monolake.org

Mono Lake Committee | Keep Saving Mono Lake

Page Load Speed

1.5 sec in total

First Response

324 ms

Resources Loaded

1.1 sec

Page Rendered

126 ms

monolake.org screenshot

About Website

Welcome to monolake.org homepage info - get ready to check Mono Lake best content for United States right away, or after learning these important things about monolake.org

Since 1978 the non-profit Mono Lake Committee has worked to protect Mono Lake, restore its tributary streams and surrounding lands, and educate the next generation about wise water use. We invite you ...

Visit monolake.org

Key Findings

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

monolake.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.137

80/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

monolake.org

324 ms

jquery-1.11.3.min.js

274 ms

swfobject.js

123 ms

bootstrap.css

362 ms

default.css

125 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 91% of them (31 requests) were addressed to the original Monolake.org, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Longlive.monolake.org. The less responsive or slowest element that took the longest time to load (389 ms) belongs to the original domain Monolake.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 406.6 kB (39%)

Content Size

1.0 MB

After Optimization

622.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Monolake.org main page is 1.0 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. 20% of websites need less resources to load. Images take 626.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 18.4 kB

  • Original 23.6 kB
  • After minification 19.4 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 4.2 kB, which is 18% 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 18.4 kB or 78% of the original size.

Image Optimization

-15%

Potential reduce by 91.2 kB

  • Original 626.8 kB
  • After minification 535.6 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. Obviously, Mono Lake needs image optimization as it can save up to 91.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 168.7 kB

  • Original 230.2 kB
  • After minification 188.8 kB
  • After compression 61.5 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 168.7 kB or 73% of the original size.

CSS Optimization

-86%

Potential reduce by 128.3 kB

  • Original 148.9 kB
  • After minification 123.3 kB
  • After compression 20.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. Monolake.org needs all CSS files to be minified and compressed as it can save up to 128.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (15%)

Requests Now

33

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

monolake.org

monolake.org

324 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

274 ms

swfobject.js

swfobject.js

123 ms

bootstrap.css

bootstrap.css

362 ms

default.css

default.css

125 ms

urchin.js

urchin.js

4 ms

bootstrap.js

bootstrap.js

274 ms

luminateExtend.js

luminateExtend.js

234 ms

le-home.js

le-home.js

126 ms

search.gif

search.gif

80 ms

mlclogo.png

mlclogo.png

66 ms

i.gif

i.gif

79 ms

buttonmemberloginhomepageltblue.gif

buttonmemberloginhomepageltblue.gif

80 ms

levelprediversion.gif

levelprediversion.gif

67 ms

leveltarget.gif

leveltarget.gif

65 ms

level6381.gif

level6381.gif

114 ms

levellow.gif

levellow.gif

115 ms

rss.jpg

rss.jpg

125 ms

buttondonatehomepage.gif

buttondonatehomepage.gif

126 ms

buttonhomepagevisit.png

buttonhomepagevisit.png

127 ms

buttonhomepageseasonalupdatefall.png

buttonhomepageseasonalupdatefall.png

137 ms

buttonhomepagefieldseminars.png

buttonhomepagefieldseminars.png

170 ms

buttonhomepageguidedtrips.png

buttonhomepageguidedtrips.png

168 ms

buttonhomepageweatherandroads2010.png

buttonhomepageweatherandroads2010.png

186 ms

buttonhomepagewebcams2010.png

buttonhomepagewebcams2010.png

187 ms

iconfacebook.png

iconfacebook.png

187 ms

icontwitter.png

icontwitter.png

203 ms

print.gif

print.gif

223 ms

mlclogopsm.jpg

mlclogopsm.jpg

224 ms

hpimage2.jpg

hpimage2.jpg

389 ms

solid.png

solid.png

214 ms

email.gif

email.gif

215 ms

__utm.gif

__utm.gif

10 ms

CRConsAPI

CRConsAPI

313 ms

Accessibility Review

monolake.org accessibility score

96

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.

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

Links do not have a discernible name

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

monolake.org SEO score

97

Search Engine Optimization Advices

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

monolake.org

Open Graph description is not detected on the main page of Mono Lake. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: