Website review, no card needed

mahoneysgarden.com logo

mahoneysgarden.com website review

Visit site (opens in a new tab)Reviewed 22 October 202626 issues · 77 checks

This review found 26 issues worth fixing on mahoneysgarden.com, 14 of them high impact, across 77 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.9 s1.6 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
89 ms69 msMay 2Oct 1773 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202683 ms
May 9, 202682 ms
May 16, 202682 ms
May 23, 202683 ms
May 30, 202684 ms
Jun 6, 202686 ms
Jun 13, 202686 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202684 ms
Jul 11, 202686 ms
Jul 18, 202686 ms
Jul 25, 202686 ms
Aug 8, 202684 ms
Aug 15, 202681 ms
Aug 22, 202677 ms
Aug 29, 202671 ms
Sep 5, 202671 ms
Sep 12, 202671 ms
Sep 19, 202671 ms
Sep 26, 202674 ms
Oct 3, 202673 ms
Oct 10, 202673 ms
Oct 17, 202673 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 mahoneysgarden.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix58
  • Improve image delivery

    3.0 s · 3.3 MB

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

  • Render-blocking requests

    2.8 s

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

  • Reduce unused JavaScript

    1.5 s · 281 KiB

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

  • Mobile performance score: 58

    58/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Fonts and others), adding 339 KiB and 174 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 10 KiB

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

  • Use efficient cache lifetimes

    150 ms · 5 KiB

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

  • 3 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix100
  • 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: 21.5 s

    21.5 s

    Your largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Save now: 33% off Spring and Summer Trees and Shrubs”.

  • Time to Interactive: 22.6 s

    22.6 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user TTFB: 996 ms

    996 ms

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

7 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 76 ms

    76 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Tap response (INP) got 12% faster for real visitors

    -12%

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

  • 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

3 to fix45
  • Page weight: 6.4 MB in 91 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 91 requests on a phone: images 5.6 MB (23), scripts 597 KiB (30) and fonts 141 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    rectangle--768x535.png weighs 545 KiB. On a phone connection a single image that size takes seconds.

  • 5 images in older formats

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

  • 1 image below the first screen load straight away

    1 image further down the page (212 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.81 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8894
  • Certain ARIA roles must contain particular children (1 element)

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

  • 6 tap targets too small

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 18 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • 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 17 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 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10090
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 148 internal links, 18 external

    The homepage links to 148 pages on mahoneysgarden.com and 18 external pages.

7 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Mahoney's Garden Center is dedicated to providing the highest quality and largest selection of plants, gardening produc…”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Mahoney's Garden Center - Plants & Garden Supplies in MA”.

  • Canonical URL set

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix86
  • 2 pages share a title

    https://mahoneysgarden.com/mahoneys-grown and https://mahoneysgarden.com/proven-winners-at-mahoneys all use the title “Locally-Grown Plants & Flowers - Mahoney's Garden Center”. 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://mahoneysgarden.com/mahoneys-grown and https://mahoneysgarden.com/proven-winners-at-mahoneys use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://mahoneysgarden.com/proven-winners-at-mahoneys, https://mahoneysgarden.com/rewards-program, https://mahoneysgarden.com/specials, https://mahoneysgarden.com/guarantee, https://mahoneysgarden.com/frequently-asked-questions and https://mahoneysgarden.com/blog and 2 others 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 44 found) and read each the way a search engine does.

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

  • 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 10093
  • 12 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 262 words of copy

    The homepage carries about 262 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP ONLINE”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Community Support – Request a Donation”, “Order Online” and “Shop Online”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 mahoneysgarden.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 Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on mahoneysgarden.com, including 10 speed issues, 1 SEO issue and 1 conversion gap. 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