Website review, no card needed

galleysolutions.com logo

galleysolutions.com website review

Visit site (opens in a new tab)Reviewed 20 October 202638 issues · 79 checks

This review found 38 issues worth fixing on galleysolutions.com, 16 of them high impact, across 79 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
7.4 s3.5 sMay 2Oct 174.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20265.4 s
May 9, 20265.3 s
May 16, 20265.4 s
May 23, 20265.5 s
May 30, 20265.3 s
Jun 6, 20265.3 s
Jun 13, 20265.0 s
Jun 20, 20264.9 s
Jun 27, 20265.5 s
Jul 4, 20266.5 s
Jul 11, 20266.9 s
Jul 18, 20266.7 s
Jul 25, 20266.5 s
Aug 1, 20265.8 s
Aug 8, 20265.0 s
Aug 15, 20264.9 s
Aug 22, 20265.0 s
Aug 29, 20265.2 s
Sep 5, 20264.2 s
Sep 12, 20264.4 s
Sep 19, 20264.3 s
Sep 26, 20264.1 s
Oct 3, 20264.0 s
Oct 10, 20264.2 s
Oct 17, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
235 ms105 msMay 2Oct 17179 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026122 ms
May 9, 2026134 ms
May 16, 2026151 ms
May 23, 2026153 ms
May 30, 2026146 ms
Jun 6, 2026156 ms
Jun 13, 2026128 ms
Jun 20, 2026120 ms
Jun 27, 2026121 ms
Jul 4, 2026178 ms
Jul 11, 2026209 ms
Jul 18, 2026217 ms
Jul 25, 2026220 ms
Aug 1, 2026186 ms
Aug 8, 2026169 ms
Aug 15, 2026143 ms
Aug 29, 2026152 ms
Oct 3, 2026162 ms
Oct 10, 2026169 ms
Oct 17, 2026179 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 galleysolutions.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. galleysolutions.com at 0.5 s0.5 s
  2. galleysolutions.com at 1.0 s1.0 s
  3. galleysolutions.com at 1.5 s1.5 s
  4. galleysolutions.com at 1.9 s1.9 s
  5. galleysolutions.com at 2.4 s2.4 s
  6. galleysolutions.com at 2.9 s2.9 s
  7. galleysolutions.com at 3.4 s3.4 s
  8. galleysolutions.com at 3.9 s3.9 s

Speed

11 to fix44
  • Reduce unused JavaScript

    5.2 s · 1.0 MB

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

  • Use efficient cache lifetimes

    3.1 s · 588 KiB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 44

    44/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Squarespace and Facebook and others), adding 2.6 MB and 1.3 s of main-thread time.

  • Reduce unused CSS

    600 ms · 279 KiB

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

  • Google Tag Manager adds 572 ms

    572 ms

    Google Tag Manager costs a phone 572 ms of main-thread work and 1.0 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.

  • Legacy JavaScript

    500 ms · 121 KiB

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

  • Improve image delivery

    450 ms · 170 KiB

    4 images could be 170 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Squarespace adds 373 ms

    373 ms

    Squarespace costs a phone 373 ms of main-thread work and 979 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.

  • Main-thread work: 3.0 s

    A phone's processor spends 3.0 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 13 long tasks on the main thread

    13 long tasks block the main thread while loading, the longest for 152 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 110 ms

    110 ms

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

Core Web Vitals

11 to fix50
  • 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.2 s

    4.2 s

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

  • Real-user FCP: 4.0 s

    4.0 s

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

  • Largest Contentful Paint: 25.2 s

    25.2 s

    Your largest element takes 25.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Galley recipe management, live food costing, and the teams …”.

  • Time to Interactive: 25.8 s

    25.8 s

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

  • First Contentful Paint: 6.7 s

    6.7 s

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

  • Speed Index: 11.0 s

    11.0 s

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

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

    +36%

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 479 ms

    479 ms

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

  • 8 images without width and height

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

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

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

    -17%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.4 s to 4.6 s 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).

Images and page weight

2 to fix75
  • Page weight: 3.9 MB in 140 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 140 requests on a phone: scripts 2.6 MB (69), other files 493 KiB (30) and images 348 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    123 KiB

    2 images are downloaded at several times the size a phone draws them, for example culinary-software-rfp-builder-thumbnail.png at 500 px wide, shown at 98 px. Resized copies would save about 123 KiB.

  • 2 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.11 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9394
  • 32 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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

2 to fixGoogle 10086
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6007cf1ee5265a1eeaa…”.

  • 28 internal links, 5 external

    The homepage links to 28 pages on galleysolutions.com and 5 external pages.

6 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Galley Solutions is the creator of the culinary resource planning platform that aligns kitchen creativity with operatio…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Galley Solutions: Culinary Resource Planning for Every Kitchen”.

  • Canonical URL set

    The canonical URL is https://www.galleysolutions.com/.

  • 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://www.galleysolutions.com/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    12%

    A phone browser shows 1,044 words, but the HTML your server sends has only 128. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No llms.txt

    There is no https://www.galleysolutions.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.

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

Other pages

5 to fix76
  • 2 pages share a title

    https://www.galleysolutions.com/demo-reservation and https://www.galleysolutions.com/demo-reservation-v3 all use the title “Reserve a Demo for Culinary Operations — Galley Solutions”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.galleysolutions.com/pricing-test has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.galleysolutions.com/demo-reservation and https://www.galleysolutions.com/demo-reservation-v3 use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.galleysolutions.com/demo-reservation-v3, whose canonical is https://www.galleysolutions.com/demo-reservation. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://www.galleysolutions.com/onsite-foodservice-software, https://www.galleysolutions.com/crp-platform-overview, https://www.galleysolutions.com/resources, https://www.galleysolutions.com/demo-reservation and https://www.galleysolutions.com/demo-reservation-v3 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://www.galleysolutions.com/onsite-foodservice-software, https://www.galleysolutions.com/crp-platform-overview, https://www.galleysolutions.com/resources, https://www.galleysolutions.com/demo-reservation and https://www.galleysolutions.com/demo-reservation-v3 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.

  • 10 internal pages checked

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

3 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 4 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    9 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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,044 words of copy

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

5 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Pricing”, “RESERVE A DEMO” and “Reserve a Demo”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, HubSpot and Umami.

  • Direct contact links

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

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 19 cookies set on arrival

    19

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

  • 50 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 galleysolutions.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
Squarespace
Framework
jQuery
Analytics
Google 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 38 issues on galleysolutions.com, including 22 speed issues, 2 SEO issues 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