Website review, no card needed

jamestowntribe.org logo

jamestowntribe.org website review

Visit site (opens in a new tab)Reviewed 6 November 202645 issues · 91 checks

This review found 45 issues worth fixing on jamestowntribe.org, 14 of them high impact, across 91 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
4.2 s1.7 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.9 s
Jun 13, 20263.2 s
Jun 20, 20263.7 s
Jun 27, 20263.9 s
Jul 4, 20263.6 s
Jul 11, 20263.3 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.7 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.5 s
Oct 10, 20262.6 s
Oct 17, 20262.3 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
134 ms97 msMay 16Oct 31104 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026128 ms
May 23, 2026120 ms
May 30, 2026113 ms
Jun 6, 2026113 ms
Jun 13, 2026108 ms
Jun 20, 2026108 ms
Jun 27, 2026101 ms
Jul 4, 2026104 ms
Jul 11, 2026121 ms
Jul 18, 2026120 ms
Jul 25, 2026121 ms
Aug 1, 2026121 ms
Aug 8, 2026112 ms
Aug 15, 2026112 ms
Aug 22, 2026116 ms
Aug 29, 2026112 ms
Sep 5, 2026116 ms
Sep 12, 2026119 ms
Sep 19, 2026114 ms
Sep 26, 2026122 ms
Oct 3, 2026130 ms
Oct 10, 2026130 ms
Oct 17, 2026119 ms
Oct 24, 2026113 ms
Oct 31, 2026104 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 jamestowntribe.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jamestowntribe.org at 1.0 s1.0 s
  2. jamestowntribe.org at 2.1 s2.1 s
  3. jamestowntribe.org at 3.1 s3.1 s
  4. jamestowntribe.org at 4.2 s4.2 s
  5. jamestowntribe.org at 5.2 s5.2 s
  6. jamestowntribe.org at 6.3 s6.3 s
  7. jamestowntribe.org at 7.3 s7.3 s
  8. jamestowntribe.org at 8.4 s8.4 s

Speed

11 to fix64
  • Use efficient cache lifetimes

    3.0 s · 2.4 MB

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

  • Reduce unused JavaScript

    1.6 s · 875 KiB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    750 ms · 128 KiB

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

  • Improve image delivery

    650 ms · 167 KiB

    6 images could be 167 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, elocallink.tv and Google Maps and others), adding 2.4 MB and 444 ms of main-thread time.

  • Minify JavaScript

    466 KiB

    466 KiB could be saved by minifying JavaScript.

  • Main-thread work: 3.8 s

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

  • Google Tag Manager adds 256 ms

    256 ms

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

  • elocallink.tv adds 96 ms

    96 ms

    elocallink.tv costs a phone 96 ms of main-thread work and 848 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.

  • Font display

    200 ms

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

  • Minify CSS

    140 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • 3 long tasks on the main thread

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

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

  • Forced reflow

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

1 checks passed
  • Server response: 22 ms

    22 ms

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

Core Web Vitals

10 to fix0
  • 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: 10.2 s

    10.2 s

    Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Strong People “S’Klallam” is a Salish term for “The Str…”.

  • Time to Interactive: 14.4 s

    14.4 s

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

  • Speed Index: 9.4 s

    9.4 s

    Visually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 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 CLS: 0.13

    0.13

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 1 image without width and height

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

4 checks passed
  • Tap response (INP) got 12% faster for real visitors

    -12%

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 7 ms

    7 ms

    Scripts block the page for only 7 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 5.8 MB in 96 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 96 requests on a phone: images 3.0 MB (21), scripts 2.0 MB (26) and fonts 553 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.66 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 7283
  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 9 images without alt text

    9 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (24 elements)

    All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 19 links without text

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 31 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 4 links with vague text

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

  • 98 internal links, 45 external

    The homepage links to 98 pages on jamestowntribe.org and 45 external pages.

7 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “The Jamestown S’Klallam Tribe’s Mission is to seek to be self-sufficient and to provide governmental programs and servi…”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Jamestown S'Klallam Tribe - The Strong People - Blyn, WA”.

  • Canonical URL set

    The canonical URL is https://jamestowntribe.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, GovernmentOrganization, ImageObject, Organization and Place.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://jamestowntribe.org/sitemap_index.xml.

AI search readiness

100
3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

5 to fix76
  • 4 pages share 2 titles

    https://jamestowntribe.org/careers and https://jamestowntribe.org/program-staff/human-resources/careers all use the title “Career Opportunities - Jamestown S'Klallam Tribe”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://jamestowntribe.org/careers, https://jamestowntribe.org/program-staff/human-resources/careers, https://jamestowntribe.org/employee-benefits, https://jamestowntribe.org/human-resources, https://jamestowntribe.org/program-staff and https://jamestowntribe.org/programs-staff/office-of-the-ceo and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://jamestowntribe.org/program-staff/dungeness-river-nature-center and https://jamestowntribe.org/program-staff/natural-resources use the same meta description. A description written for each page earns more clicks.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://jamestowntribe.org/program-staff/human-resources/careers, whose canonical is https://jamestowntribe.org/careers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://jamestowntribe.org/careers, https://jamestowntribe.org/program-staff/human-resources/careers, https://jamestowntribe.org/employee-benefits, https://jamestowntribe.org/human-resources, https://jamestowntribe.org/programs-staff/office-of-the-ceo and https://jamestowntribe.org/program-staff/administration-operations and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://jamestowntribe.org/program-staff/administration-operations, https://jamestowntribe.org/program-staff/finance, https://jamestowntribe.org/program-staff/jst-information-systems and https://jamestowntribe.org/uncategorized/self-governance took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7389
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) The media could not be loaded, either because the server or networ…”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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.

  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 9 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No map or directions link

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

  • 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 1,044 words of copy

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

6 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “BOOK NOW” and “Contact Us >”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 jamestowntribe.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
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Sucuri

Company

Headquarters
Sequim

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on jamestowntribe.org, including 21 speed issues, 2 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