Website review, no card needed

wineadore.com logo

wineadore.com website review

Visit site (opens in a new tab)Reviewed 16 November 202635 issues · 79 checks

This review found 35 issues worth fixing on wineadore.com, 13 of them high impact, across 79 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

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

How it loaded on a phone

  1. wineadore.com at 2.1 s2.1 s
  2. wineadore.com at 4.1 s4.1 s
  3. wineadore.com at 6.2 s6.2 s
  4. wineadore.com at 8.3 s8.3 s
  5. wineadore.com at 10.4 s10.4 s
  6. wineadore.com at 12.4 s12.4 s
  7. wineadore.com at 14.5 s14.5 s
  8. wineadore.com at 16.6 s16.6 s

Speed

14 to fix35
  • Improve image delivery

    9.4 s · 7.5 MB

    22 images could be 7.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.4 s faster on a phone.

  • Use efficient cache lifetimes

    4.2 s · 3.1 MB

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

  • Reduce unused JavaScript

    2.1 s · 1.0 MB

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

  • Main-thread work: 14.1 s

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

  • Mobile performance score: 35

    35/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Stripe and Google Tag Manager and others), adding 9.5 MB and 2.7 s of main-thread time.

  • Facebook adds 990 ms

    990 ms

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

  • 20 long tasks on the main thread

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

  • Other Google APIs/SDKs adds 84 ms

    84 ms

    Other Google APIs/SDKs costs a phone 84 ms of main-thread work and 8.3 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.

  • Stripe adds 620 ms

    620 ms

    Stripe costs a phone 620 ms of main-thread work and 308 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 Tag Manager adds 486 ms

    486 ms

    Google Tag Manager costs a phone 486 ms of main-thread work and 157 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 429 ms

    429 ms

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

  • Render-blocking requests

    300 ms

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

  • 1,897 HTML elements

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

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

    63 ms

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

Core Web Vitals

5 to fix34
  • Largest Contentful Paint: 25.5 s

    25.5 s

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

  • Speed Index: 21.1 s

    21.1 s

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

  • Time to Interactive: 41.9 s

    41.9 s

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

  • Total Blocking Time: 3.9 s

    3.9 s

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

  • 3 images without width and height

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

2 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

4 to fix33
  • Page weight: 14.8 MB in 141 requests

    14.8 MB

    Your homepage downloads 14.8 MB in 141 requests on a phone: images 12.0 MB (62), scripts 2.6 MB (51) and HTML 48 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 21 images far larger than shown

    1.8 MB

    21 images are downloaded at several times the size a phone draws them, for example image at 2,048 px wide, shown at 142 px. Resized copies would save about 1.8 MB.

  • 11 images in older formats

    11 images (1.1 MB) 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.

  • 9 images below the first screen load straight away

    9 images further down the page (901 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.2 g of CO₂ per visit

    4.19 g

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

Accessibility

2 to fixGoogle 9496
  • 19 text elements with low contrast

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

  • 6 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 75 images in the HTML carry an alt attribute.

  • 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. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 57 internal links, 13 external

    The homepage links to 57 pages on wineadore.com and 13 external pages.

8 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Shop premium wines from around the world at Wine Adore. Find corkage venues and wine tasting events in Singapore, with …”.

  • One H1 headline

    Your main headline reads: “Wine Adore - Premium Wine Marketplace”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Wine Adore - Premium Wine Marketplace | Buy Wines Online”.

  • Canonical URL set

    The canonical URL is https://wineadore.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://wineadore.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://wineadore.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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix79
  • 3 linked pages hidden from search

    https://wineadore.com/corkage, https://wineadore.com/inventory and https://wineadore.com/store-credit are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://wineadore.com/inventory and https://wineadore.com/store-credit all use the title “Wine Adore - Premium Wine Marketplace”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://wineadore.com/inventory and https://wineadore.com/store-credit use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://wineadore.com/corkage, https://wineadore.com/inventory and https://wineadore.com/store-credit 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 34 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.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://www.facebook.com/tr?id=2661737140758209&ev=PageView&noscript=1.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://mpc-pilot-2-s6uit34pua-ue.a.run.app/events?cee=no' violates the following Content Security Polic…”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    66 of 75 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

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

  • No opening hours

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

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Loading... https://wineadore.com/shop”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop”, “Loading...https://wineadore.com/shop” and “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 16 trust badges and “0+ Happy Customers”.

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

  • 6 cookies set on arrival

    6

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

  • 18 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Google

Company

Employees
78
Headquarters
Singapore

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on wineadore.com, including 19 speed 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