Website review, no card needed

andronicos.com logo

andronicos.com website review

Visit site (opens in a new tab)Reviewed 21 October 202650 issues · 91 checks

This review found 50 issues worth fixing on andronicos.com, 24 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
4.5 s3.4 sMay 2Oct 174.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.8 s
May 9, 20263.9 s
May 16, 20264.0 s
May 23, 20264.1 s
May 30, 20264.1 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20263.9 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.6 s
Jul 18, 20263.5 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.8 s
Aug 15, 20264.0 s
Aug 22, 20264.1 s
Aug 29, 20264.3 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.4 s
Sep 26, 20264.3 s
Oct 3, 20264.2 s
Oct 10, 20264.2 s
Oct 17, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
174 ms133 msMay 2Oct 17161 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026138 ms
May 9, 2026143 ms
May 16, 2026139 ms
May 23, 2026146 ms
May 30, 2026144 ms
Jun 6, 2026144 ms
Jun 13, 2026144 ms
Jun 20, 2026148 ms
Jun 27, 2026147 ms
Jul 4, 2026146 ms
Jul 11, 2026150 ms
Jul 18, 2026139 ms
Jul 25, 2026146 ms
Aug 1, 2026141 ms
Aug 8, 2026146 ms
Aug 15, 2026154 ms
Aug 22, 2026153 ms
Aug 29, 2026154 ms
Sep 5, 2026146 ms
Sep 12, 2026145 ms
Sep 19, 2026146 ms
Sep 26, 2026154 ms
Oct 3, 2026169 ms
Oct 10, 2026162 ms
Oct 17, 2026161 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 andronicos.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. andronicos.com at 0.7 s0.7 s
  2. andronicos.com at 1.4 s1.4 s
  3. andronicos.com at 2.2 s2.2 s
  4. andronicos.com at 2.9 s2.9 s
  5. andronicos.com at 3.6 s3.6 s
  6. andronicos.com at 4.3 s4.3 s
  7. andronicos.com at 5.1 s5.1 s
  8. andronicos.com at 5.8 s5.8 s

Speed

10 to fix25
  • Reduce unused JavaScript

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

  • Use efficient cache lifetimes

    4.7 s · 1.1 MB

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

  • Improve image delivery

    1.4 s · 677 KiB

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

  • Reduce unused CSS

    1.4 s · 184 KiB

    About 184 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 25

    25/100

    Your mobile performance score is 25 (desktop: 33). 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, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,808 HTML elements

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    300 ms · 48 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Adobe Tag Manager, Google/Doubleclick Ads and Optanon and others), adding 748 KiB and 455 ms of main-thread time.

  • Minify JavaScript

    7 KiB

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 74 ms

    74 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.1 s

    4.1 s

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

  • Largest Contentful Paint: 23.4 s

    23.4 s

    Your largest element takes 23.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Stock up on Halloween candy, treats & more.”.

  • Time to Interactive: 26.3 s

    26.3 s

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

  • Speed Index: 13.8 s

    13.8 s

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

  • First Contentful Paint: 6.3 s

    6.3 s

    The first text or image appears after 6.3 s on a phone. Good is under 1.8 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.

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 997 ms

    997 ms

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

  • Cumulative Layout Shift: 0.121

    0.121

    The layout shifts by 0.121 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

    +15%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

1 checks passed
  • Real-user INP: 142 ms

    142 ms

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

Images and page weight

2 to fix60
  • Page weight: 4.1 MB in 175 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 175 requests on a phone: scripts 2.8 MB (66), images 876 KiB (60) and stylesheets 205 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    77 KiB

    1 image is downloaded at several times the size a phone draws it, for example 5cfd46db50a54e907a00b805ad0673e22ee9e0b570c0d2818142c98da4d4 at 288 px wide, shown at 50 px. Resized copies would save about 77 KiB.

  • 1 image in older formats

    1 image (106 KiB) is 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.

  • 5 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.17 g

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

Accessibility

10 to fixGoogle 8787
  • Certain ARIA roles must be contained by particular parents (1 element)

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

  • 7 tap targets too small

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 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.

  • 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 skip levels

    Headings skip levels (h1 → h3), 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).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

5 to fixGoogle 10079
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Shopped with us before?” and “Hi, {firstName}! We think you might have more tha…”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (172 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 231 internal links, 33 external

    The homepage links to 231 pages on andronicos.com and 33 external pages.

3 checks passed
  • Title: 64 characters

    Your title is a healthy 64 characters: “Grocery Delivery Near You - Order Groceries Online | Andronico's”.

  • 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.andronicos.com/shop/sitemaps/sitemap-index.xml.

AI search readiness

1 to fix88
  • 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.andronicos.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.

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

  • Text is in the HTML

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

Other pages

3 to fix73
  • 9 pages without a title

    https://www.andronicos.com/shop/purchases/buy-it-again.html, https://www.andronicos.com/order-account/orders, https://www.andronicos.com/schedule-and-save/manage, https://www.andronicos.com/customer-account/account-settings, https://www.andronicos.com/customer-account/family-members and https://www.andronicos.com/customer-account/rewards and 3 others have no <title>, so Google invents the link text in results.

  • 10 linked pages hidden from search

    https://www.andronicos.com/lp/supported-browsers.html, https://www.andronicos.com/shop/purchases/buy-it-again.html, https://www.andronicos.com/order-account/orders, https://www.andronicos.com/schedule-and-save/manage, https://www.andronicos.com/customer-account/account-settings and https://www.andronicos.com/customer-account/family-members and 4 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 12 pages without a meta description

    https://www.andronicos.com/lp/supported-browsers.html, https://www.andronicos.com/erums/store/prebook, https://www.andronicos.com/customer-account/account-dashboard, https://www.andronicos.com/shop/purchases/buy-it-again.html, https://www.andronicos.com/order-account/orders and https://www.andronicos.com/schedule-and-save/manage and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

Best practices

5 to fixGoogle 6569
  • 2 broken images

    2 images failed to load on a phone, for example https://www.andronicos.com/undefined?$collections-canvas-banner-mobile$&defaultImage=Not_Available.

  • 49 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Loading the font 'data:application/font-woff;charset=utf-8;base64,d09GRgABAAAAABDkAAsAAAAAG6gAAQAAAAAAAAAAAAAAAAAAAAAAA…”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

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

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now” and “Halloween treats Shop now”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Buy It Again”, “Manage Schedule & Save” and “Try again”.

  • 1 short form

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

Privacy and tracking

  • 7 trackers load before any consent

    7

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

  • 25 cookies set on arrival

    25

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

  • 40 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 andronicos.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on andronicos.com, including 21 speed issues, 5 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