Website review, no card needed

stfranciswinery.com logo

stfranciswinery.com website review

Visit site (opens in a new tab)Reviewed 23 October 202643 issues · 92 checks

This review found 43 issues worth fixing on stfranciswinery.com, 17 of them high impact, across 92 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.4 s1.8 sMay 2Oct 172.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.1 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
124 ms101 msMay 2Oct 17121 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026112 ms
May 9, 2026112 ms
May 16, 2026112 ms
May 23, 2026116 ms
May 30, 2026112 ms
Jun 6, 2026112 ms
Jun 13, 2026109 ms
Jun 20, 2026108 ms
Jun 27, 2026106 ms
Jul 4, 2026104 ms
Jul 11, 2026108 ms
Jul 18, 2026107 ms
Jul 25, 2026112 ms
Aug 1, 2026113 ms
Aug 8, 2026112 ms
Aug 15, 2026121 ms
Aug 22, 2026120 ms
Aug 29, 2026121 ms
Sep 5, 2026120 ms
Sep 12, 2026112 ms
Sep 19, 2026115 ms
Sep 26, 2026121 ms
Oct 3, 2026121 ms
Oct 10, 2026121 ms
Oct 17, 2026121 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 stfranciswinery.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stfranciswinery.com at 3.0 s3.0 s
  2. stfranciswinery.com at 6.0 s6.0 s
  3. stfranciswinery.com at 8.9 s8.9 s
  4. stfranciswinery.com at 11.9 s11.9 s
  5. stfranciswinery.com at 14.9 s14.9 s
  6. stfranciswinery.com at 17.9 s17.9 s
  7. stfranciswinery.com at 20.8 s20.8 s
  8. stfranciswinery.com at 23.8 s23.8 s

Speed

15 to fix29
  • Use efficient cache lifetimes

    1.6 s · 12.1 MB

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

  • Reduce unused JavaScript

    3.9 s · 1.6 MB

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

  • Improve image delivery

    1.6 s · 3.2 MB

    16 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 1.6 s faster on a phone.

  • Render-blocking requests

    4.4 s

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

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 7.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and commerce7.com and others), adding 3.2 MB and 2.4 s of main-thread time.

  • Reduce unused CSS

    880 ms · 127 KiB

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

  • Google CDN adds 783 ms

    783 ms

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

  • Google Tag Manager adds 682 ms

    682 ms

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

  • commerce7.com adds 491 ms

    491 ms

    commerce7.com costs a phone 491 ms of main-thread work and 758 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.

  • Legacy JavaScript

    400 ms · 78 KiB

    Polyfills for old browsers add 78 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • 1,547 HTML elements

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

  • redchirp.com adds 42 ms

    42 ms

    redchirp.com costs a phone 42 ms of main-thread work and 312 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

    150 ms · 13 KiB

    13 KiB could be saved by minifying CSS.

  • Minify JavaScript

    130 ms · 6 KiB

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

  • 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: 113 ms

    113 ms

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

Core Web Vitals

7 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: 26.9 s

    26.9 s

    Your largest element takes 26.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Voted Best Tasting Room in the Bay Area Empty heading”.

  • Time to Interactive: 31.6 s

    31.6 s

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

  • First Contentful Paint: 6.5 s

    6.5 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Real-user CLS: 0.15

    0.15

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

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 112 ms to 121 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-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 94 ms

    94 ms

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 745 ms

    745 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix64
  • Page weight: 21.7 MB in 232 requests

    21.7 MB

    Your homepage downloads 21.7 MB in 232 requests on a phone: media 11.1 MB (1), images 6.2 MB (34) and scripts 2.9 MB (78). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Rooted-in-Real_Blk_Horz_Logo-1170x139.png 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).

  • 5 images in older formats

    5 images (216 KiB) 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.

  • About 6.1 g of CO₂ per visit

    6.15 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 9691
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • 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 (h3 → h5), which makes the page harder to scan with a screen reader.

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

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

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

1 to fixGoogle 10090
  • No H1 headline

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

  • 130 internal links, 4 external

    The homepage links to 130 pages on stfranciswinery.com and 4 external pages.

7 checks passed
  • Meta description: 118 characters

    Your meta description is 118 characters: “St. Francis Winery & Vineyards is a breathtaking destination in the heart of Sonoma County's prestigious wine country.”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “St. Francis Winery & Vineyards • Sonoma, CA”.

  • Canonical URL set

    The canonical URL is https://www.stfranciswinery.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://www.stfranciswinery.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

5 to fix76
  • 11 pages share a title

    https://www.stfranciswinery.com/collection/wines, https://www.stfranciswinery.com/collection/artisan, https://www.stfranciswinery.com/collection/icon, https://www.stfranciswinery.com/collection/appellation, https://www.stfranciswinery.com/collection/classic and https://www.stfranciswinery.com/collection/zinfandel-by-varietal and 5 others all use the title “St. Francis Wine Collections”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.stfranciswinery.com/classic-sonoma-wines has no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages share a meta description

    https://www.stfranciswinery.com/collection/wines, https://www.stfranciswinery.com/collection/artisan, https://www.stfranciswinery.com/collection/icon, https://www.stfranciswinery.com/collection/appellation, https://www.stfranciswinery.com/collection/classic and https://www.stfranciswinery.com/collection/zinfandel-by-varietal and 5 others use the same meta description. A description written for each page earns more clicks.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://www.stfranciswinery.com/collection/wines, whose canonical is https://www.stfranciswinery.com/collection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://www.stfranciswinery.com/collection/wines, https://www.stfranciswinery.com/collection/artisan, https://www.stfranciswinery.com/collection/icon, https://www.stfranciswinery.com/collection/appellation, https://www.stfranciswinery.com/collection/classic and https://www.stfranciswinery.com/collection/zinfandel-by-varietal and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 63 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 9687
  • 3 small tap targets

    3 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'appendChild')”.

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 603 words of visible text.

6 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop All Wines”, “Shop by Collection” and “Shop by Varietal”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

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

  • 30 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 stfranciswinery.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 Analytics | Google Tag Manager

Company

Founded
1971

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on stfranciswinery.com, including 22 speed issues, 1 SEO issue 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