Tools & Wizards About Us
spokanefallstu.org screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

spokanefallstu.org

Spokane Falls Chapter - Trout Unlimited - Spokane Falls Trout Unlimited

Page Load Speed

3.7 sec in total

First Response

140 ms

Resources Loaded

3.2 sec

Page Rendered

293 ms

spokanefallstu.org screenshot

About Website

Visit spokanefallstu.org now to see the best up-to-date Spokane Falls Tu content and also check out these interesting facts you probably never knew about spokanefallstu.org

Spokane Falls Trout Unlimited Chapter advocates protecting, reconnecting, and sustaining the wild and native cold-water fisheries of the Inland Northwest.

Visit spokanefallstu.org

Key Findings

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

Performance Metrics

spokanefallstu.org performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

spokanefallstu.org

140 ms

spokanefallstu.org

215 ms

style.min.css

20 ms

slick.css

255 ms

wpls-public.css

33 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 96% of them (110 requests) were addressed to the original Spokanefallstu.org, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Spokanefallstu.org.

Page Optimization Overview & Recommendations

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

Content Size

2.9 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spokanefallstu.org main page is 2.9 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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 118.0 kB

  • Original 147.9 kB
  • After minification 144.1 kB
  • After compression 29.9 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 118.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 342 B

  • Original 2.3 MB
  • After minification 2.3 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. Spokane Falls Tu images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 21.7 kB

  • Original 311.6 kB
  • After minification 311.1 kB
  • After compression 289.9 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

-3%

Potential reduce by 5.3 kB

  • Original 150.8 kB
  • After minification 150.4 kB
  • After compression 145.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. Spokanefallstu.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 73 (70%)

Requests Now

104

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

spokanefallstu.org

spokanefallstu.org

140 ms

spokanefallstu.org

spokanefallstu.org

215 ms

style.min.css

style.min.css

20 ms

slick.css

slick.css

255 ms

wpls-public.css

wpls-public.css

33 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

195 ms

style.css

style.css

32 ms

grid-system.css

grid-system.css

34 ms

style.css

style.css

209 ms

header-layout-centered-logo-between-menu.css

header-layout-centered-logo-between-menu.css

48 ms

header-perma-transparent.css

header-perma-transparent.css

225 ms

element-icon-with-text.css

element-icon-with-text.css

259 ms

element-wpb-column-border.css

element-wpb-column-border.css

322 ms

element-recent-posts.css

element-recent-posts.css

215 ms

events-calendar.css

events-calendar.css

419 ms

fullpage.css

fullpage.css

373 ms

responsive.css

responsive.css

234 ms

select2.css

select2.css

246 ms

skin-original.css

skin-original.css

452 ms

menu-dynamic.css

menu-dynamic.css

263 ms

widget-nectar-posts.css

widget-nectar-posts.css

454 ms

style.min.css

style.min.css

456 ms

js_composer.min.css

js_composer.min.css

494 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

541 ms

style.css

style.css

425 ms

css

css

43 ms

jquery.min.js

jquery.min.js

596 ms

jquery-migrate.min.js

jquery-migrate.min.js

456 ms

js

js

80 ms

variables-skeleton.min.css

variables-skeleton.min.css

741 ms

common-skeleton.min.css

common-skeleton.min.css

742 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

463 ms

variables-full.min.css

variables-full.min.css

473 ms

common-full.min.css

common-full.min.css

484 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

495 ms

animate.min.css

animate.min.css

740 ms

style-non-critical.css

style-non-critical.css

740 ms

magnific.css

magnific.css

743 ms

core.css

core.css

871 ms

core.min.js

core.min.js

869 ms

menu.min.js

menu.min.js

877 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

852 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

719 ms

wp-polyfill.min.js

wp-polyfill.min.js

720 ms

dom-ready.min.js

dom-ready.min.js

709 ms

hooks.min.js

hooks.min.js

725 ms

i18n.min.js

i18n.min.js

705 ms

a11y.min.js

a11y.min.js

855 ms

autocomplete.min.js

autocomplete.min.js

859 ms

wpss-search-suggest.js

wpss-search-suggest.js

805 ms

jquery.easing.min.js

jquery.easing.min.js

673 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

672 ms

priority.js

priority.js

810 ms

transit.min.js

transit.min.js

657 ms

waypoints.js

waypoints.js

615 ms

imagesLoaded.min.js

imagesLoaded.min.js

563 ms

hoverintent.min.js

hoverintent.min.js

673 ms

magnific.js

magnific.js

509 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

698 ms

nectar-full-page-rows.js

nectar-full-page-rows.js

754 ms

anime.min.js

anime.min.js

783 ms

superfish.js

superfish.js

819 ms

init.js

init.js

826 ms

touchswipe.min.js

touchswipe.min.js

794 ms

select2.min.js

select2.min.js

673 ms

app.min.js

app.min.js

680 ms

js_composer_front.min.js

js_composer_front.min.js

838 ms

slick.min.js

slick.min.js

821 ms

f36bb68330662e9fa8c7a7b1cc5913db

f36bb68330662e9fa8c7a7b1cc5913db

132 ms

wpls-public.js

wpls-public.js

748 ms

tribe-common.min.js

tribe-common.min.js

537 ms

query-string.min.js

query-string.min.js

706 ms

underscore-before.js

underscore-before.js

563 ms

underscore.min.js

underscore.min.js

742 ms

underscore-after.js

underscore-after.js

561 ms

manager.min.js

manager.min.js

566 ms

breakpoints.min.js

breakpoints.min.js

764 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

823 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

162 ms

OpenSans-Light.woff

OpenSans-Light.woff

727 ms

OpenSans-SemiBold.woff

OpenSans-SemiBold.woff

758 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

816 ms

Lovelo_Black.woff

Lovelo_Black.woff

773 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

861 ms

icomoon.woff

icomoon.woff

833 ms

sftu-logo-125h.png

sftu-logo-125h.png

896 ms

trout-abides-white-pink-stripe125.png

trout-abides-white-pink-stripe125.png

904 ms

sftu-logo-white-pink-redband125.png

sftu-logo-white-pink-redband125.png

921 ms

swoth-icon.png

swoth-icon.png

970 ms

sftu-home-takecw-snake1920x1280-100x100.jpg

sftu-home-takecw-snake1920x1280-100x100.jpg

983 ms

wild-salmon-100x100.jpg

wild-salmon-100x100.jpg

1018 ms

silverbow-logo2019.png

silverbow-logo2019.png

915 ms

trout-full-color-fade178.png

trout-full-color-fade178.png

954 ms

spokane-indians-redband178.png

spokane-indians-redband178.png

960 ms

foc_logo.png

foc_logo.png

991 ms

spokane-riverkeeper-logo178.png

spokane-riverkeeper-logo178.png

888 ms

dry-fly-distilling-logo178.png

dry-fly-distilling-logo178.png

966 ms

wdfw-logo.png

wdfw-logo.png

997 ms

watu-logo178.png

watu-logo178.png

1015 ms

cdat-logo178.png

cdat-logo178.png

978 ms

stoi-logo.png

stoi-logo.png

984 ms

camp-creative-logo178.png

camp-creative-logo178.png

987 ms

imaginary-trout-no-name-wht75.png

imaginary-trout-no-name-wht75.png

1004 ms

animated-sftu-logo1.gif

animated-sftu-logo1.gif

1050 ms

sftu-home-hero2048.jpg

sftu-home-hero2048.jpg

1152 ms

sftu-california-cr-home-hero2048.jpg

sftu-california-cr-home-hero2048.jpg

1299 ms

visintainer-spokane-redband5.jpg

visintainer-spokane-redband5.jpg

1154 ms

sftu-home-takecw-snake1920x1280.jpg

sftu-home-takecw-snake1920x1280.jpg

1273 ms

wild-salmon.jpg

wild-salmon.jpg

1236 ms

kelly-creek-idaho-2005.jpg

kelly-creek-idaho-2005.jpg

1237 ms

clearwater_river1600.jpg

clearwater_river1600.jpg

1324 ms

ajax-loader.gif

ajax-loader.gif

1204 ms

spokanefallstu.org

spokanefallstu.org

1232 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1057 ms

Accessibility Review

spokanefallstu.org accessibility score

85

Accessibility Issues

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 input fields do not have accessible names

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

High

Some elements have a [tabindex] value greater than 0

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

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

spokanefallstu.org SEO score

99

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

spokanefallstu.org

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