Tools & Wizards About Us
clarylake.org screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

clarylake.org

Clary Lake Association | Preserving and Protecting Clary Lake

Page Load Speed

3 sec in total

First Response

171 ms

Resources Loaded

2.5 sec

Page Rendered

297 ms

clarylake.org screenshot

About Website

Click here to check amazing Clary Lake content. Otherwise, check out these important facts you probably never knew about clarylake.org

Preserving and Protecting Clary Lake

Visit clarylake.org

Key Findings

We analyzed Clarylake.org page load time and found that the first response time was 171 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

clarylake.org performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value550 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

clarylake.org

171 ms

clarylake.org

1684 ms

sgr.css

197 ms

cv.css

269 ms

style.min.css

33 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 54% of them (57 requests) were addressed to the original Clarylake.org, 10% (11 requests) were made to C0.wp.com and 8% (8 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Clarylake.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 221.7 kB (13%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Clarylake.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 87.8 kB

  • Original 114.4 kB
  • After minification 112.9 kB
  • After compression 26.6 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 87.8 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 77.1 kB

  • Original 1.1 MB
  • After minification 1.0 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. Clary Lake images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 32.8 kB

  • Original 383.1 kB
  • After minification 383.1 kB
  • After compression 350.3 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

-16%

Potential reduce by 24.1 kB

  • Original 148.0 kB
  • After minification 147.4 kB
  • After compression 123.9 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. Clarylake.org needs all CSS files to be minified and compressed as it can save up to 24.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (69%)

Requests Now

95

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clary 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 37 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

clarylake.org

clarylake.org

171 ms

clarylake.org

clarylake.org

1684 ms

sgr.css

sgr.css

197 ms

cv.css

cv.css

269 ms

style.min.css

style.min.css

33 ms

utilities.css

utilities.css

71 ms

styles.css

styles.css

468 ms

page-list.css

page-list.css

194 ms

extendify-utilities.css

extendify-utilities.css

211 ms

wpsc-front-end-styles.css

wpsc-front-end-styles.css

260 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

262 ms

style.css

style.css

281 ms

font-open-sans.css

font-open-sans.css

326 ms

style.css

style.css

328 ms

blocks.css

blocks.css

341 ms

style.css

style.css

27 ms

instagram.css

instagram.css

28 ms

tablepress-combined.min.css

tablepress-combined.min.css

345 ms

animate.css

animate.css

412 ms

styles.css

styles.css

402 ms

trigger_buttons.css

trigger_buttons.css

406 ms

pagination_style.css

pagination_style.css

413 ms

nextgen_basic_thumbnails.css

nextgen_basic_thumbnails.css

475 ms

display.css

display.css

482 ms

sharing.css

sharing.css

27 ms

social-logos.min.css

social-logos.min.css

32 ms

sgr.js

sgr.js

476 ms

utilities.js

utilities.js

69 ms

jquery.min.js

jquery.min.js

32 ms

jquery-migrate.min.js

jquery-migrate.min.js

32 ms

ajax.min.js

ajax.min.js

479 ms

navigation.js

navigation.js

535 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

622 ms

custom.js

custom.js

565 ms

nextgen_basic_thumbnails.js

nextgen_basic_thumbnails.js

566 ms

css

css

48 ms

utilities.css

utilities.css

36 ms

utilities.js

utilities.js

47 ms

mailpoet-public.2e4711f8.css

mailpoet-public.2e4711f8.css

84 ms

css

css

18 ms

css

css

24 ms

css

css

27 ms

script.js

script.js

70 ms

hooks.min.js

hooks.min.js

3 ms

i18n.min.js

i18n.min.js

4 ms

index.js

index.js

101 ms

index.js

index.js

207 ms

cv.js

cv.js

207 ms

common.js

common.js

207 ms

lightbox_context.js

lightbox_context.js

208 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

209 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

210 ms

nextgen_fancybox_init.js

nextgen_fancybox_init.js

209 ms

facebook-embed.min.js

facebook-embed.min.js

2 ms

api.js

api.js

35 ms

wp-polyfill.min.js

wp-polyfill.min.js

3 ms

index.js

index.js

209 ms

e-202445.js

e-202445.js

16 ms

api.js

api.js

54 ms

public.js

public.js

322 ms

465802655_1808197376609674_7526131752964545817_n.jpg

465802655_1808197376609674_7526131752964545817_n.jpg

256 ms

463984059_526766563651982_7340127151520586161_n.jpg

463984059_526766563651982_7340127151520586161_n.jpg

290 ms

cropped-Azalea-6-01-2019-banner-2.jpg

cropped-Azalea-6-01-2019-banner-2.jpg

82 ms

loon-logo7-non-t-PPCL.png

loon-logo7-non-t-PPCL.png

336 ms

campic_20241106-060000-300x169.jpg

campic_20241106-060000-300x169.jpg

110 ms

Clary-Lake-Water-Level-October-2024-300x192.png

Clary-Lake-Water-Level-October-2024-300x192.png

172 ms

20130630-0533-200x300.jpg

20130630-0533-200x300.jpg

172 ms

20130630-0643-200x300.webp

20130630-0643-200x300.webp

173 ms

Comet-Atlas-John-Meader1-300x200.jpg

Comet-Atlas-John-Meader1-300x200.jpg

227 ms

ISS071-E-676484-300x200.jpg

ISS071-E-676484-300x200.jpg

227 ms

donate3.gif

donate3.gif

228 ms

thumbs_Vincentsen-shoreline.jpg

thumbs_Vincentsen-shoreline.jpg

230 ms

thumbs_September-Bloom-20240916_123135.jpg

thumbs_September-Bloom-20240916_123135.jpg

297 ms

thumbs_gate-20240912_113956.jpg

thumbs_gate-20240912_113956.jpg

317 ms

thumbs_20240820_152503-Medium.jpg

thumbs_20240820_152503-Medium.jpg

263 ms

thumbs_20240820_152437-Medium.jpg

thumbs_20240820_152437-Medium.jpg

291 ms

thumbs_20240820_152402-Medium.jpg

thumbs_20240820_152402-Medium.jpg

298 ms

camsample.jpg

camsample.jpg

333 ms

465085585_517075814499805_5946232940390548825_n.jpg

465085585_517075814499805_5946232940390548825_n.jpg

291 ms

464768251_8940871822700781_7206135556582317123_n.jpg

464768251_8940871822700781_7206135556582317123_n.jpg

410 ms

463645748_439192992114014_1434214329623856454_n.jpg

463645748_439192992114014_1434214329623856454_n.jpg

309 ms

463350226_1774566273291902_8308393094245328890_n.jpg

463350226_1774566273291902_8308393094245328890_n.jpg

358 ms

open-sans-all-400-normal.woff

open-sans-all-400-normal.woff

362 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

31 ms

open-sans-all-700-normal.woff

open-sans-all-700-normal.woff

319 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

336 ms

sdk.js

sdk.js

31 ms

recaptcha__en.js

recaptcha__en.js

46 ms

sdk.js

sdk.js

62 ms

anchor

anchor

71 ms

styles__ltr.css

styles__ltr.css

21 ms

recaptcha__en.js

recaptcha__en.js

24 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

24 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf

38 ms

page.php

page.php

132 ms

PnTf5OtFzsP.css

PnTf5OtFzsP.css

22 ms

Xk_-iR0gDYt.js

Xk_-iR0gDYt.js

48 ms

0bWEtGbW7yi.js

0bWEtGbW7yi.js

70 ms

KQ9hZo1cCms.js

KQ9hZo1cCms.js

71 ms

jSnkebxg-Sx.js

jSnkebxg-Sx.js

68 ms

p55HfXW__mM.js

p55HfXW__mM.js

68 ms

305575046_455726436589258_1588896211027272032_n.jpg

305575046_455726436589258_1588896211027272032_n.jpg

32 ms

307856976_455726433255925_897234212285936389_n.jpg

307856976_455726433255925_897234212285936389_n.jpg

31 ms

JfNyoodUUhk.js

JfNyoodUUhk.js

8 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

8 ms

Accessibility Review

clarylake.org accessibility score

88

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.

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

clarylake.org best practices score

83

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

Browser errors were logged to the console

SEO Factors

clarylake.org SEO score

62

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

clarylake.org

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