Website review, no card needed

mountainhousefire.com logo

mountainhousefire.com website review

Visit site (opens in a new tab)Reviewed 17 November 202629 issues · 76 checks

This review found 29 issues worth fixing on mountainhousefire.com, 12 of them high impact, across 76 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

Full-page screenshot of mountainhousefire.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mountainhousefire.com at 0.4 s0.4 s
  2. mountainhousefire.com at 0.8 s0.8 s
  3. mountainhousefire.com at 1.1 s1.1 s
  4. mountainhousefire.com at 1.5 s1.5 s
  5. mountainhousefire.com at 1.9 s1.9 s
  6. mountainhousefire.com at 2.3 s2.3 s
  7. mountainhousefire.com at 2.6 s2.6 s
  8. mountainhousefire.com at 3.0 s3.0 s

Speed

11 to fix51
  • Use efficient cache lifetimes

    73.0 s · 14.0 MB

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

  • Render-blocking requests

    70.2 s

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

  • Reduce unused JavaScript

    1.4 s · 13.0 MB

    About 13.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Improve image delivery

    2.7 s · 492 KiB

    2 images could be 492 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, hcaptcha.com and Pendo and others), adding 14.2 MB and 226 ms of main-thread time.

  • specialdistrict.org adds 0 ms

    0 ms

    specialdistrict.org costs a phone 0 ms of main-thread work and 12.9 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.

  • Mobile performance score: 51

    51/100

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

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    330 ms · 86 KiB

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

  • Google CDN adds 79 ms

    79 ms

    Google CDN costs a phone 79 ms of main-thread work and 352 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.

  • imgix adds 0 ms

    0 ms

    imgix costs a phone 0 ms of main-thread work and 519 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

    150 ms

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

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

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

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

  • Server response: 75 ms

    75 ms

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

Core Web Vitals

6 to fix61
  • First Contentful Paint: 69.4 s

    69.4 s

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

  • Largest Contentful Paint: 76.0 s

    76.0 s

    Your largest element takes 76.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 69.4 s

    69.4 s

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

  • Time to Interactive: 76.0 s

    76.0 s

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

  • Cumulative Layout Shift: 0.126

    0.126

    The layout shifts by 0.126 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 4 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix70
  • Page weight: 15.0 MB in 36 requests

    15.0 MB

    Your homepage downloads 15.0 MB in 36 requests on a phone: scripts 13.8 MB (9), images 1.0 MB (10) and stylesheets 104 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.2 g of CO₂ per visit

    4.25 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9696
  • <svg> elements with an img or image role must have alternative text (4 elements)

    <svg> elements with an img or image role must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 9281
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • One H1 headline

    Your <h1> is empty.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 81 internal links, 3 external

    The homepage links to 81 pages on mountainhousefire.com and 3 external pages.

4 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “Homepage French Camp McKinley Fire District”.

  • Canonical URL set

    The canonical URL is https://www.frenchcampfire.com/.

  • 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://www.frenchcampfire.com/sitemap.xml.

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.frenchcampfire.com/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

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without a meta description

    https://www.frenchcampfire.com/about-special-districts, https://www.frenchcampfire.com/employment-opportunities and https://www.frenchcampfire.com/governance have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    21 of 25 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • 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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 216 words

    The homepage has only about 216 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join our Team!” and “REQUEST A REPORT”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Request an Incident Report”, “Contact Us” and “Join our Team!”.

  • 2 short forms

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

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 12 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 mountainhousefire.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
AWS

Hiring

Hiring
2 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on mountainhousefire.com, including 17 speed issues, 3 SEO issues and 4 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