Website review, no card needed

cherokee.org logo

cherokee.org website review

Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 77 checks

This review found 38 issues worth fixing on cherokee.org, 13 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.2 s1.8 sSep 5Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
118 ms98 msSep 5Oct 24114 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 2026100 ms
Sep 12, 2026105 ms
Sep 19, 2026112 ms
Sep 26, 2026113 ms
Oct 3, 2026116 ms
Oct 10, 2026115 ms
Oct 17, 2026112 ms
Oct 24, 2026114 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of cherokee.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cherokee.org at 0.8 s0.8 s
  2. cherokee.org at 1.7 s1.7 s
  3. cherokee.org at 2.5 s2.5 s
  4. cherokee.org at 3.4 s3.4 s
  5. cherokee.org at 4.2 s4.2 s
  6. cherokee.org at 5.1 s5.1 s
  7. cherokee.org at 5.9 s5.9 s
  8. cherokee.org at 6.7 s6.7 s

Speed

9 to fix46
  • Use efficient cache lifetimes

    9.3 s · 4.8 MB

    18 files are served with short cache lifetimes, so returning visitors download them again (4.8 MB).

  • Improve image delivery

    4.1 s · 3.2 MB

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

  • Reduce unused JavaScript

    3.5 s · 726 KiB

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

  • Mobile performance score: 46

    46/100

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 675 KiB and 731 ms of main-thread time.

  • Google Tag Manager adds 731 ms

    731 ms

    Google Tag Manager costs a phone 731 ms of main-thread work and 673 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.

  • Reduce unused CSS

    460 ms · 88 KiB

    About 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • Document request latency

    305 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 8 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Minify JavaScript

    57 KiB

    57 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 803 ms of it running JavaScript. That is comfortably low.

  • Server response: 130 ms

    130 ms

    Your server sent the HTML in 130 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 29.6 s

    29.6 s

    Your largest element takes 29.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Osiyo! The Cherokee Nation is the largest sovereign tribal …”.

  • Time to Interactive: 30.4 s

    30.4 s

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

  • Speed Index: 14.2 s

    14.2 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Real-user LCP: 2.8 s

    2.8 s

    Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user TTFB: 925 ms

    925 ms

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

  • Total Blocking Time: 411 ms

    411 ms

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

  • 1 image without width and height

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

  • Largest content (LCP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 117 ms

    117 ms

    Real visitors wait 117 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix25
  • Page weight: 7.2 MB in 41 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 41 requests on a phone: images 5.1 MB (21), scripts 1.2 MB (9) and HTML 456 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

  • 12 images in older formats

    12 images (4.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.

  • An image on the first screen is lazy-loaded

    parade.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 4 images far larger than shown

    339 KiB

    4 images are downloaded at several times the size a phone draws them, for example parade.jpg at 1,280 px wide, shown at 390 px. Resized copies would save about 339 KiB.

  • About 2.0 g of CO₂ per visit

    2.03 g

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

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 9270
  • Title is short (29 characters)

    Your title is only 29 characters: “Cherokee Nation: cherokee.gov”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Osiyo!”, “Osiyo!” and “Osiyo!”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.cherokee.gov/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at cherokee.gov/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 5 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 119 internal links, 57 external

    The homepage links to 119 pages on cherokee.org and 57 external pages.

2 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “The Cherokee Nation is the federally-recognized government of the Cherokee people and has inherent sovereign status rec…”.

  • Canonical URL set

    The canonical URL is https://www.cherokee.gov/.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.cherokee.gov/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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,319 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 5 linked pages hidden from search

    https://www.cherokee.gov/life-events, https://www.cherokee.gov/departments, https://www.cherokee.gov/all-contacts, https://www.cherokee.gov/all-public-notices and https://www.cherokee.gov/all-events are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.cherokee.gov/employment/cherokee-nation-human-resources/human-resources, https://www.cherokee.gov/life-events, https://www.cherokee.gov/departments, https://www.cherokee.gov/all-contacts, https://www.cherokee.gov/all-public-notices and https://www.cherokee.gov/all-events have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://www.cherokee.gov/departments and https://www.cherokee.gov/about-the-nation/maps took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    44 of 47 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

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

  • About 850 words of copy

    The homepage carries about 850 words of visible text.

2 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “How do I apply to become a citizen?”, “Cherokee Gift Shop” and “Join the celebration (opens in new tab)”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 3 cookies set on arrival

    3

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

  • No consent tool detected

    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.

  • 2 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at cherokee.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Cherokee Web
Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager
Hosting
Cherokee Nation Gov

Company

Founded
1839
Headquarters
Tahlequah

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on cherokee.org, including 18 speed issues, 8 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25