Website review, no card needed

hancockandmoore.com logo

hancockandmoore.com website review

Visit site (opens in a new tab)Reviewed 19 October 202633 issues · 77 checks

This review found 33 issues worth fixing on hancockandmoore.com, 13 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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.3 s741 msMay 2Oct 17912 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026800 ms
May 9, 2026968 ms
May 16, 2026989 ms
May 23, 2026995 ms
May 30, 2026953 ms
Jun 6, 2026855 ms
Jun 13, 2026810 ms
Jun 20, 2026878 ms
Jun 27, 2026923 ms
Jul 4, 2026936 ms
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.1 s
Aug 8, 20261.0 s
Aug 15, 2026937 ms
Aug 22, 2026999 ms
Aug 29, 20261.0 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.0 s
Sep 26, 2026984 ms
Oct 3, 2026950 ms
Oct 10, 2026970 ms
Oct 17, 2026912 ms
Real-visitor tap response (INP)75th percentile, phones
74 ms51 msMay 2Oct 1754 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202663 ms
May 9, 202671 ms
May 30, 202670 ms
Jun 6, 202663 ms
Jun 13, 202659 ms
Jun 20, 202661 ms
Jun 27, 202663 ms
Aug 1, 202671 ms
Aug 8, 202668 ms
Aug 15, 202662 ms
Aug 22, 202663 ms
Aug 29, 202663 ms
Sep 5, 202668 ms
Sep 12, 202670 ms
Sep 19, 202663 ms
Sep 26, 202662 ms
Oct 3, 202655 ms
Oct 10, 202656 ms
Oct 17, 202654 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 hancockandmoore.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hancockandmoore.com at 1.1 s1.1 s
  2. hancockandmoore.com at 2.2 s2.2 s
  3. hancockandmoore.com at 3.2 s3.2 s
  4. hancockandmoore.com at 4.3 s4.3 s
  5. hancockandmoore.com at 5.4 s5.4 s
  6. hancockandmoore.com at 6.5 s6.5 s
  7. hancockandmoore.com at 7.6 s7.6 s
  8. hancockandmoore.com at 8.6 s8.6 s

Speed

7 to fix43
  • Use efficient cache lifetimes

    5.8 s · 1.4 MB

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

  • Improve image delivery

    2.8 s · 754 KiB

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

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 43

    43/100

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

  • Reduce unused JavaScript

    150 ms · 251 KiB

    About 251 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 73 KiB

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

  • userway.org adds 80 ms

    80 ms

    userway.org costs a phone 80 ms of main-thread work and 379 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cookiebot, userway.org and jQuery CDN and others), adding 822 KiB and 304 ms of main-thread time.

  • Font display

    150 ms

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

  • 3 long tasks on the main thread

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

  • Minify JavaScript

    44 KiB

    44 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 96 but mobile only 43. 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.

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 8.6 s

    8.6 s

    Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEW INTRODUCTIONS View New Introductions”. Most of its time is element render delay (3.8 s).

  • Speed Index: 8.1 s

    8.1 s

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

  • Time to Interactive: 11.0 s

    11.0 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Cumulative Layout Shift: 0.352

    0.352

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

  • 10 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

8 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: 0.9 s

    0.9 s

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

  • Real-user INP: 54 ms

    54 ms

    Real visitors wait 54 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: 0.7 s

    0.7 s

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

  • Real-user TTFB: 488 ms

    488 ms

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

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

    -18%

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

  • Total Blocking Time: 32 ms

    32 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 55 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 55 requests on a phone: images 1.0 MB (15), scripts 798 KiB (19) and fonts 302 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.70 g

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

2 to fixGoogle 10097
  • 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 (6 elements)

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

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

8 to fixGoogle 9154
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 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: “Home | Hancock and Moore”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

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

  • 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 XML sitemap

    No XML sitemap at https://hancockandmoore.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at hancockandmoore.com/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 17 internal links, 7 external

    The homepage links to 17 pages on hancockandmoore.com and 7 external pages.

AI search readiness

1 to fix83
  • 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://hancockandmoore.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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://hancockandmoore.com/WhereToBuy, https://hancockandmoore.com/Products/NewProducts, https://hancockandmoore.com/Products/CDJ, https://hancockandmoore.com/YourWay, https://hancockandmoore.com/YourWay/Modern and https://hancockandmoore.com/Home/Careers and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://hancockandmoore.com/WhereToBuy, https://hancockandmoore.com/Products/NewProducts, https://hancockandmoore.com/Products/CDJ, https://hancockandmoore.com/YourWay, https://hancockandmoore.com/YourWay/Modern and https://hancockandmoore.com/Home/Careers and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://hancockandmoore.com/WhereToBuy, https://hancockandmoore.com/YourWay, https://hancockandmoore.com/YourWay/Modern and https://hancockandmoore.com/Home/StayConnected have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 8 small tap targets

    8 of 15 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: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • Only about 122 words

    The homepage has only about 122 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “WHERE TO BUY”, “Where To Buy” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 7 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on hancockandmoore.com, including 13 speed issues, 8 SEO issues and 4 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