Website review, no card needed

atozwineworks.com logo

atozwineworks.com website review

Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 91 checks

This review found 43 issues worth fixing on atozwineworks.com, 12 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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
3.2 s1.8 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.6 s
May 9, 20262.7 s
May 16, 20262.8 s
May 23, 20263.1 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.5 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.6 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
306 ms88 msMay 2Oct 17261 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026113 ms
May 9, 2026120 ms
May 16, 2026137 ms
May 23, 2026148 ms
May 30, 2026144 ms
Jun 6, 2026148 ms
Jun 13, 2026153 ms
Jun 20, 2026132 ms
Jun 27, 2026135 ms
Jul 4, 2026138 ms
Jul 11, 2026148 ms
Jul 18, 2026179 ms
Jul 25, 2026246 ms
Aug 1, 2026263 ms
Aug 8, 2026273 ms
Aug 15, 2026276 ms
Aug 22, 2026281 ms
Aug 29, 2026277 ms
Sep 5, 2026276 ms
Sep 12, 2026278 ms
Sep 19, 2026274 ms
Sep 26, 2026273 ms
Oct 3, 2026265 ms
Oct 10, 2026270 ms
Oct 17, 2026261 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 atozwineworks.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. atozwineworks.com at 0.6 s0.6 s
  2. atozwineworks.com at 1.2 s1.2 s
  3. atozwineworks.com at 1.8 s1.8 s
  4. atozwineworks.com at 2.4 s2.4 s
  5. atozwineworks.com at 3.0 s3.0 s
  6. atozwineworks.com at 3.6 s3.6 s
  7. atozwineworks.com at 4.2 s4.2 s
  8. atozwineworks.com at 4.8 s4.8 s

Speed

13 to fix29
  • Reduce unused JavaScript

    2.7 s · 1.5 MB

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

  • Render-blocking requests

    3.6 s

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

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 7.3 s

    A phone's processor spends 7.3 s on main-thread work while loading, 3.7 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 Tag Manager, Google CDN and commerce7.com and others), adding 3.3 MB and 2.6 s of main-thread time.

  • Use efficient cache lifetimes

    900 ms · 415 KiB

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

  • Reduce unused CSS

    750 ms · 123 KiB

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

  • Google CDN adds 635 ms

    635 ms

    Google CDN costs a phone 635 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 647 ms

    647 ms

    Google Tag Manager costs a phone 647 ms of main-thread work and 560 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 403 ms

    403 ms

    commerce7.com costs a phone 403 ms of main-thread work and 722 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 335 ms. During a long task the page ignores taps.

  • Hotjar adds 257 ms

    257 ms

    Hotjar costs a phone 257 ms of main-thread work and 71 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.

  • Klaviyo adds 148 ms

    148 ms

    Klaviyo costs a phone 148 ms of main-thread work and 324 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

    150 ms · 101 KiB

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

  • Improve image delivery

    116 KiB

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Phones get a much slower page than desktops

    Desktop scores 62 but mobile only 29. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

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

12 to fix33
  • 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: 24.1 s

    24.1 s

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

  • Time to Interactive: 35.0 s

    35.0 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Speed Index: 11.7 s

    11.7 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 261 ms

    261 ms

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

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

    +128%

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 19 images without width and height

    19 images have no width and height attributes, so the layout jumps as each one loads.

  • 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.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0.043

    0.043

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

Images and page weight

2 to fix69
  • Page weight: 8.0 MB in 248 requests

    8.0 MB

    Your homepage downloads 8.0 MB in 248 requests on a phone: scripts 3.6 MB (104), images 3.2 MB (33) and other files 405 KiB (36). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Policeman-color-300x291-1.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).

  • 7 images below the first screen load straight away

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

  • About 2.3 g of CO₂ per visit

    2.28 g

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

4 to fixGoogle 8996
  • All page content should be contained by landmarks (2 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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 72 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 8591
  • Meta description is long (168 characters)

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

  • 13 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 80 internal links, 17 external

    The homepage links to 80 pages on atozwineworks.com and 17 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “A to Z Wineworks”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Quality Wines for Sustainable Value | A to Z Wineworks”.

  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

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

Other pages

3 to fix83
  • 6 pages share a title

    https://atozwineworks.com/product/a-to-z-oregon-pinot-noir, https://atozwineworks.com/product/a-to-z-chardonnay, https://atozwineworks.com/product/a-to-z-pinot-gris, https://atozwineworks.com/product/the-essence-of-oregon-pinot-noir, https://atozwineworks.com/product/a-to-z-rose and https://atozwineworks.com/product/a-to-z-bubbles all use the title “Product - Oregon Wines of Exceptional Quality | A to Z Wineworks”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://atozwineworks.com/shop, https://atozwineworks.com/product/a-to-z-oregon-pinot-noir, https://atozwineworks.com/product/a-to-z-chardonnay, https://atozwineworks.com/product/a-to-z-pinot-gris, https://atozwineworks.com/product/the-essence-of-oregon-pinot-noir and https://atozwineworks.com/product/a-to-z-rose and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://atozwineworks.com/product/a-to-z-oregon-pinot-noir, https://atozwineworks.com/product/a-to-z-chardonnay, https://atozwineworks.com/product/a-to-z-pinot-gris, https://atozwineworks.com/product/the-essence-of-oregon-pinot-noir, https://atozwineworks.com/product/a-to-z-rose and https://atozwineworks.com/product/a-to-z-bubbles have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages slow to respond

    https://atozwineworks.com/shop, https://atozwineworks.com/product/a-to-z-chardonnay, https://atozwineworks.com/product/a-to-z-pinot-gris, https://atozwineworks.com/product/the-essence-of-oregon-pinot-noir, https://atozwineworks.com/product/a-to-z-bubbles and https://atozwineworks.com/find-our-wines and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

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

    The homepage carries about 394 words of visible text.

5 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us” and “learn more”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 14 cookies set on arrival

    14

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

  • 31 other companies contacted

    Loading the homepage contacts 31 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 atozwineworks.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

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 atozwineworks.com, including 25 speed issues, 3 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