Website review, no card needed

originalhousewine.com logo

originalhousewine.com website review

Visit site (opens in a new tab)Reviewed 6 November 202624 issues · 66 checks

This review found 24 issues worth fixing on originalhousewine.com, 7 of them high impact, across 66 checks. The most urgent: improve image delivery. 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.2 s779 msMay 16Sep 51.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.0 s
May 23, 2026876 ms
Jun 13, 2026822 ms
Jun 20, 2026990 ms
Jun 27, 2026983 ms
Jul 4, 20261.0 s
Jul 18, 20261.1 s
Aug 8, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
72 ms64 msMay 16Aug 2968 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202668 ms
May 23, 202665 ms
May 30, 202668 ms
Jun 27, 202668 ms
Jul 4, 202668 ms
Jul 18, 202669 ms
Aug 8, 202671 ms
Aug 29, 202668 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 originalhousewine.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix66
  • Improve image delivery

    1.8 s · 459 KiB

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

  • Mobile performance score: 66

    66/100

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

  • Use efficient cache lifetimes

    200 ms · 10 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (10 KiB).

  • 3 third-party services on the page

    3 third-party services load with your homepage (nfcube.com, Shopify and shop.app), adding 134 KiB and 27 ms of main-thread time.

  • Reduce unused CSS

    12 KiB

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

  • Duplicated JavaScript

    7 KiB

    7 KiB JavaScript is shipped twice across bundles.

  • 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: 0.9 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix68
  • Largest Contentful Paint: 7.7 s

    7.7 s

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

  • Time to Interactive: 7.8 s

    7.8 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

    The first text or image appears after 2.8 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.

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

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

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • 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

2 to fix64
  • Page weight: 9.1 MB in 140 requests

    9.1 MB

    Your homepage downloads 9.1 MB in 140 requests on a phone: media 7.2 MB (1), images 977 KiB (33) and other files 628 KiB (65). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    HW_FeatureImage.jpg 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).

  • About 2.6 g of CO₂ per visit

    2.58 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.58 g of CO₂e: 309.2 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 9694
  • 9 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • Title is long (89 characters)

    Your title is 89 characters, so Google will cut it off around 60: “House Wine - Magnificent wine for your home at a magnificent price. – Original House Wine”.

  • Meta description is long (320 characters)

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • One H1 headline

    Your <h1> is empty.

  • 62 internal links, 3 external

    The homepage links to 62 pages on originalhousewine.com and 3 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://originalhousewine.com/.

  • Structured data in place

    Structured data found: Organization 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://originalhousewine.com/sitemap.xml.

AI search readiness

100
4 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 (317 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://originalhousewine.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix83
  • 5 pages without a meta description

    https://originalhousewine.com/collections/multi-packs, https://originalhousewine.com/collections/pride-1, https://originalhousewine.com/collections/merch, https://originalhousewine.com/collections/cocktails and https://originalhousewine.com/pages/faq have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://originalhousewine.com/collections/shop-all, https://originalhousewine.com/collections/shop-all/Vessel_Bottle, https://originalhousewine.com/collections/shop-all/Vessel_Can, https://originalhousewine.com/collections/shop-all/Type_Bubbles, https://originalhousewine.com/collections/shop-all/Type_Red and https://originalhousewine.com/collections/shop-all/Type_White and 1 other use the same meta description. A description written for each page earns more clicks.

  • 6 links to non-canonical URLs

    Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://originalhousewine.com/collections/shop-all/Vessel_Bottle, whose canonical is https://originalhousewine.com/collections/shop-all/vessel_bottle. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://originalhousewine.com/pages/faq has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://originalhousewine.com/collections/multi-packs, https://originalhousewine.com/collections/merch and https://originalhousewine.com/collections/cocktails 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 31 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    79 of 80 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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: 14 customer or partner logos. 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.

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

    The homepage carries about 331 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop”, “Shop All” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 8 cookies set on arrival

    8

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

  • 9 other companies contacted

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

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

nfcube.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on originalhousewine.com, including 7 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