Website review, no card needed

2townsciderhouse.com logo

2townsciderhouse.com website review

Visit site (opens in a new tab)Reviewed 20 October 202634 issues · 84 checks

This review found 34 issues worth fixing on 2townsciderhouse.com, 6 of them high impact, across 84 checks. The most urgent: page weight: 6.7 MB in 122 requests. 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
1.7 s1.3 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.4 s
Oct 3, 20261.3 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
114 ms94 msMay 2Oct 17108 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202696 ms
May 9, 202697 ms
May 16, 202697 ms
May 23, 202696 ms
May 30, 202699 ms
Jun 6, 2026103 ms
Jun 13, 2026103 ms
Jun 20, 2026103 ms
Jun 27, 2026103 ms
Jul 4, 2026103 ms
Jul 11, 2026104 ms
Jul 18, 2026104 ms
Jul 25, 2026103 ms
Aug 1, 2026101 ms
Aug 8, 2026100 ms
Aug 15, 2026101 ms
Aug 22, 2026100 ms
Aug 29, 2026104 ms
Sep 5, 2026105 ms
Sep 12, 2026111 ms
Sep 19, 2026112 ms
Sep 26, 2026112 ms
Oct 3, 2026112 ms
Oct 10, 2026110 ms
Oct 17, 2026108 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 2townsciderhouse.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

12 to fix82
  • Use efficient cache lifetimes

    1.7 MB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and Google Maps and others), adding 5.1 MB and 933 ms of main-thread time.

  • Mobile performance score: 82

    82/100

    Your mobile performance score is 82 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    150 ms · 544 KiB

    About 544 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    450 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Google Tag Manager adds 360 ms

    360 ms

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

  • imagedelivery.net adds 0 ms

    0 ms

    imagedelivery.net costs a phone 0 ms of main-thread work and 3.8 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.

  • Facebook adds 284 ms

    284 ms

    Facebook costs a phone 284 ms of main-thread work and 277 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.

  • Google Maps adds 253 ms

    253 ms

    Google Maps costs a phone 253 ms of main-thread work and 435 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.

  • 10 long tasks on the main thread

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

  • Main-thread work: 2.2 s

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

  • vinoshipper.com adds 36 ms

    36 ms

    vinoshipper.com costs a phone 36 ms of main-thread work and 347 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

    200 ms · 26 KiB

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

  • Improve image delivery

    190 KiB

    8 images could be 190 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    32 KiB

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

  • Minify CSS

    22 KiB

    22 KiB could be saved by minifying CSS.

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

    4 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 16.9 s

    16.9 s

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

  • Total Blocking Time: 464 ms

    464 ms

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A pint glass of golden cider with the 2 Towns Ciderhouse lo…”.

  • Speed Index: 3.6 s

    3.6 s

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

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

    +13%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 96 ms to 108 ms 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: 1.3 s

    1.3 s

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

  • Real-user INP: 103 ms

    103 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 615 ms

    615 ms

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

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

    -18%

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix63
  • Page weight: 6.7 MB in 122 requests

    6.7 MB

    Your homepage downloads 6.7 MB in 122 requests on a phone: images 4.9 MB (61), scripts 1.3 MB (27) and other files 361 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • 23 images below the first screen load straight away

    23 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.89 g

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

3 to fixGoogle 9194
  • 38 tap targets too small

    38 tap targets are too small or too close together to hit reliably with a finger.

  • 23 text elements with low contrast

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

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 64 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

4 to fixGoogle 8585
  • 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 (“BRINGING CIDER BACK TO THE PEOPLE”, “Golden Lime Cosmic Crisp®” and “CIDER FINDER”). One clear main headline is easier for people and search engines.

  • No robots.txt

    There is no robots.txt at 2townsciderhouse.com/robots.txt, the first file search crawlers ask for.

  • 2 links with vague text

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

  • 44 internal links, 9 external

    The homepage links to 44 pages on 2townsciderhouse.com and 9 external pages.

5 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Pioneering Northwest craft cider since 2010, friends from two nearby towns banded together on a mission to bring cider …”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “2 Towns Ciderhouse - Northwest Craft Cider”.

  • Canonical URL set

    The canonical URL is https://2townsciderhouse.com/.

  • Open Graph tags complete

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.2townsciderhouse.com/sitemap.xml.

AI search readiness

1 to fix81
  • 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.2townsciderhouse.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.

1 checks passed
  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without an H1

    https://www.2townsciderhouse.com/ciders, https://www.2townsciderhouse.com/cosmiccrawl and https://www.2townsciderhouse.com/cider-shop have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://www.2townsciderhouse.com/ciders, https://www.2townsciderhouse.com/cosmiccrawl, https://www.2townsciderhouse.com/events, https://www.2townsciderhouse.com/cider-shop and https://www.2townsciderhouse.com/cider-finder have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 23 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.

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

  • 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

3 to fixGoogle 8871
  • 1 broken image

    1 image failed to load on a phone, for example https://api.2townsciderhouse.com/wp-content/uploads/2026/08/Golden-Lime-Cosmic-1.png.

  • 42 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://googleads.g.doubleclick.net/pagead/viewthroughconversion/973166155/?random=1792469533269&cv…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 438 words of visible text.

2 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Us”, “SHOP MERCH” and “SHOP CIDER”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 2townsciderhouse.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
Next.js
Analytics
Google Analytics
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on 2townsciderhouse.com, including 16 speed issues, 4 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