Website review, no card needed

mcmurrayhatchery.com logo

mcmurrayhatchery.com website review

Visit site (opens in a new tab)Reviewed 11 November 202639 issues · 93 checks

This review found 39 issues worth fixing on mcmurrayhatchery.com, 13 of them high impact, across 93 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
720 ms547 msMay 23Nov 7583 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026688 ms
May 30, 2026695 ms
Jun 6, 2026692 ms
Jun 13, 2026691 ms
Jun 20, 2026693 ms
Jun 27, 2026694 ms
Jul 4, 2026698 ms
Jul 11, 2026700 ms
Jul 18, 2026692 ms
Jul 25, 2026682 ms
Aug 1, 2026668 ms
Aug 8, 2026652 ms
Aug 15, 2026644 ms
Aug 22, 2026634 ms
Aug 29, 2026627 ms
Sep 5, 2026620 ms
Sep 12, 2026616 ms
Sep 19, 2026612 ms
Sep 26, 2026606 ms
Oct 3, 2026605 ms
Oct 10, 2026596 ms
Oct 17, 2026595 ms
Oct 24, 2026595 ms
Oct 31, 2026567 ms
Nov 7, 2026583 ms
Real-visitor tap response (INP)75th percentile, phones
79 ms69 msMay 23Nov 771 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202673 ms
May 30, 202675 ms
Jun 6, 202677 ms
Jun 13, 202678 ms
Jun 20, 202677 ms
Jun 27, 202677 ms
Jul 4, 202678 ms
Jul 11, 202677 ms
Jul 18, 202678 ms
Jul 25, 202678 ms
Aug 1, 202678 ms
Aug 8, 202678 ms
Aug 15, 202678 ms
Aug 22, 202678 ms
Aug 29, 202678 ms
Sep 5, 202678 ms
Sep 12, 202677 ms
Sep 19, 202677 ms
Sep 26, 202674 ms
Oct 3, 202672 ms
Oct 10, 202671 ms
Oct 17, 202671 ms
Oct 24, 202671 ms
Oct 31, 202670 ms
Nov 7, 202671 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 mcmurrayhatchery.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mcmurrayhatchery.com at 0.5 s0.5 s
  2. mcmurrayhatchery.com at 1.0 s1.0 s
  3. mcmurrayhatchery.com at 1.5 s1.5 s
  4. mcmurrayhatchery.com at 2.0 s2.0 s
  5. mcmurrayhatchery.com at 2.5 s2.5 s
  6. mcmurrayhatchery.com at 3.0 s3.0 s
  7. mcmurrayhatchery.com at 3.5 s3.5 s
  8. mcmurrayhatchery.com at 4.0 s4.0 s

Speed

8 to fix59
  • Improve image delivery

    3.6 s · 4.0 MB

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

  • Render-blocking requests

    3.2 s

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

  • Reduce unused JavaScript

    1.6 s · 289 KiB

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

  • Mobile performance score: 59

    59/100

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

  • Reduce unused CSS

    750 ms · 153 KiB

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

  • Use efficient cache lifetimes

    550 ms · 133 KiB

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

  • Minify JavaScript

    450 ms · 82 KiB

    82 KiB could be saved by minifying JavaScript.

  • 2,322 HTML elements

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

  • Font display

    250 ms

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

  • 4 third-party services on the page

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

  • Minify CSS

    150 ms · 15 KiB

    15 KiB could be saved by minifying CSS.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    14 KiB

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 33 ms

    33 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 46.2 s

    46.2 s

    Your largest element takes 46.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop 2027 Chicks 2027 day-old baby chicks, turkeys, ducks, …”.

  • Time to Interactive: 46.2 s

    46.2 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • 2 images without width and height

    2 images 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-11-07, real Chrome visitors' tap response (inp) went from 73 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 71 ms

    71 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 701 ms

    701 ms

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

  • Largest content (LCP) got 17% faster for real visitors

    -17%

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

  • Total Blocking Time: 133 ms

    133 ms

    Scripts block the page for only 133 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

1 to fix70
  • Page weight: 13.0 MB in 61 requests

    13.0 MB

    Your homepage downloads 13.0 MB in 61 requests on a phone: images 11.3 MB (21), fonts 831 KiB (6) and scripts 607 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • About 3.7 g of CO₂ per visit

    3.68 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8488
  • 8 text elements with low contrast

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

  • 6 tap targets too small

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

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (13 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 9 form fields without a label

    9 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 links without text

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

  • 37 automated accessibility rules passed

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

SEO

7 to fixGoogle 8569
  • No H1 headline

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

  • Title is short (24 characters)

    Your title is only 24 characters: “Murray McMurray Hatchery”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 42 links crawlers can't follow

    42 links have no real href, so search engines can't follow them.

  • No structured data

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

  • Meta description is long (251 characters)

    Your meta description is 251 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.

  • 2 links with vague text

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

  • No X (Twitter) card tag

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

  • 462 internal links, 16 external

    The homepage links to 462 pages on mcmurrayhatchery.com and 16 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.mcmurrayhatchery.com/index.html.

  • 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.mcmurrayhatchery.com/sitemap.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.mcmurrayhatchery.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,793 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix74
  • 1 linked page hidden from search

    https://www.mcmurrayhatchery.com/newsletter_manage.html is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages share 2 titles

    / and https://www.mcmurrayhatchery.com/newsletter_manage.html all use the title “Murray McMurray Hatchery”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages share a meta description

    https://www.mcmurrayhatchery.com/history.html, https://www.mcmurrayhatchery.com/faq.html, https://www.mcmurrayhatchery.com/newsletter_manage.html, https://www.mcmurrayhatchery.com/p/menu.html and https://www.mcmurrayhatchery.com/contactus.html use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.mcmurrayhatchery.com/bantam-chicks.html, whose canonical is https://www.mcmurrayhatchery.com/chicks.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://www.mcmurrayhatchery.com/shoppingcart.html, https://www.mcmurrayhatchery.com/catalogrequest.html, https://www.mcmurrayhatchery.com/availableview.html, https://www.mcmurrayhatchery.com/p/menu.html, https://www.mcmurrayhatchery.com/availabledates.html and https://www.mcmurrayhatchery.com/chicks.html and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.mcmurrayhatchery.com/newsletter_manage.html took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 11 small tap targets

    11 of 19 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

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

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

  • About 296 words of copy

    The homepage carries about 296 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “Shop 2027 Chicks”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “CONTACT US”, “CALL ME NOW” and “Sale — Shop & Save!”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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

  • 4 cookies set on arrival

    4

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 mcmurrayhatchery.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
jQuery
Analytics
Google Analytics
Hosting
DigitalOcean

Company

Employees
38

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on mcmurrayhatchery.com, including 13 speed issues, 7 SEO issues and 2 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