cskt.org website review

12 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.3 s faster on a phone.

About 489 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

Your mobile performance score is 45 (desktop: 74). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

4 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Google Fonts and others), adding 1.2 MB and 1.0 s of main-thread time.

Google Tag Manager costs a phone 716 ms of main-thread work and 1.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

FontAwesome CDN costs a phone 327 ms of main-thread work and 143 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,663 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

2 files are served with short cache lifetimes, so returning visitors download them again (12 KiB).

13 long tasks block the main thread while loading, the longest for 128 ms. During a long task the page ignores taps.

About 51 KiB of CSS is downloaded but never applied on this page.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Desktop scores 74 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 43.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Flathead Indian Reservation is home to three tribes, th…”.

The page becomes fully interactive after 44.4 s. Good is under 3.8 s.

Visually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.7 s on a phone. Good is under 1.8 s.

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 92 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 952 ms for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 469 ms in total while the page loads. Good is under 200 ms.

2 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 10.2 MB in 165 requests on a phone: images 7.7 MB (56), scripts 1.4 MB (66) and other files 831 KiB (10). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example Landscape-18-scaled.jpg at 2,560 px wide, shown at 358 px. Resized copies would save about 1.7 MB.

15 images (3.0 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

23 images further down the page (3.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.89 g of CO₂e: 346.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 frame has no title, so screen-reader users cannot tell what it contains.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

12 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 185 pages on cskt.org and 55 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/category/natural-resources-nrd/wildlife/cwd is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/category/natural-resources-nrd/wildlife/cwd has no meta description, so Google writes the search snippet from whatever text it finds.

/sqcc, /ksanka-culture-committee, /contact, /our-priorities, /dhrd and /early-childhood-services and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 65 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,272 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 5 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.