Website review, no card needed

320ranch.com logo

320ranch.com website review

Visit site (opens in a new tab)Reviewed 12 November 202615 issues · 75 checks

This review found 15 issues worth fixing on 320ranch.com, 3 of them high impact, across 75 checks. The most urgent: 10 text elements with low contrast. 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.7 s1.7 sMay 23Nov 72.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.6 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.3 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Nov 7, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
108 ms95 msMay 23Nov 7104 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026105 ms
May 30, 2026106 ms
Jun 6, 2026105 ms
Jun 13, 2026104 ms
Jun 20, 2026103 ms
Jun 27, 202697 ms
Jul 4, 202699 ms
Jul 11, 202696 ms
Jul 18, 202697 ms
Jul 25, 202699 ms
Aug 1, 202697 ms
Aug 8, 202699 ms
Aug 15, 202698 ms
Aug 22, 202697 ms
Aug 29, 2026103 ms
Sep 5, 2026104 ms
Sep 12, 2026104 ms
Sep 19, 2026105 ms
Sep 26, 2026104 ms
Oct 3, 2026104 ms
Oct 10, 2026104 ms
Oct 17, 2026104 ms
Oct 24, 2026104 ms
Oct 31, 2026103 ms
Nov 7, 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 320ranch.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix76
  • Mobile performance score: 76

    76/100

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

  • Google CDN adds 335 ms

    335 ms

    Google CDN costs a phone 335 ms of main-thread work and 743 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 JavaScript

    375 KiB

    About 375 KiB of JavaScript is downloaded but never used on this page.

  • 1,794 HTML elements

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 991 KiB and 369 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    56 KiB

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

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

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 59 ms

    59 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 10.5 s

    10.5 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Hero_Section”.

  • Cumulative Layout Shift: 0.199

    0.199

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 113 ms

    113 ms

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

  • Real-user CLS: 0.09

    0.09

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 743 ms

    743 ms

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.0 s

    2.0 s

    Visually, the page fills in at 2.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 85 ms

    85 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.4 MB in 26 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 26 requests on a phone: images 916 KiB (9), scripts 716 KiB (7) and other files 352 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.67 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 80.3 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

3 to fixGoogle 9497
  • 10 text elements with low contrast

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 131 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (164 characters)

    Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 126 internal links, 13 external

    The homepage links to 126 pages on 320ranch.com and 13 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “A Montana Guest Ranchon the Gallatin River”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “320 Guest Ranch | Montana Ranch Near Yellowstone & Big Sky”.

  • Canonical URL set

    The canonical URL is https://320ranch.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://320ranch.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://320ranch.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 (1,796 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    26 of 32 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

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

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Click here to book Sleigh Ride” and “BOOK YOUR STAY”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Click here to book Sleigh Ride”, “Book a stay” and “BOOK YOUR STAY”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 320ranch.com, 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 Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 15 issues on 320ranch.com, including 7 speed issues, 1 SEO issue and 2 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