Website review, no card needed

clydesgroup.com logo

clydesgroup.com website review

Visit site (opens in a new tab)Reviewed 30 October 202630 issues · 80 checks

This review found 30 issues worth fixing on clydesgroup.com, 10 of them high impact, across 80 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
3.5 s1.4 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.8 s
May 23, 20262.0 s
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.5 s
Jul 18, 20261.9 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20263.3 s
Sep 26, 20262.8 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
99 ms72 msMay 16Oct 1096 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202675 ms
May 23, 202675 ms
May 30, 202685 ms
Jun 6, 202688 ms
Sep 19, 202686 ms
Oct 10, 202696 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 clydesgroup.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. clydesgroup.com at 0.7 s0.7 s
  2. clydesgroup.com at 1.3 s1.3 s
  3. clydesgroup.com at 2.0 s2.0 s
  4. clydesgroup.com at 2.6 s2.6 s
  5. clydesgroup.com at 3.3 s3.3 s
  6. clydesgroup.com at 3.9 s3.9 s
  7. clydesgroup.com at 4.6 s4.6 s
  8. clydesgroup.com at 5.3 s5.3 s

Speed

11 to fix55
  • Use efficient cache lifetimes

    7.5 s · 1.8 MB

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

  • Reduce unused JavaScript

    6.0 s · 903 KiB

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

  • audioeye.com adds 1.8 s

    1.8 s

    audioeye.com costs a phone 1.8 s of main-thread work and 309 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.1 s

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

  • Main-thread work: 4.8 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye.com, getbento.com and Google CDN and others), adding 10.4 MB and 2.8 s of main-thread time.

  • Improve image delivery

    500 ms · 1.4 MB

    14 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • getbento.com adds 607 ms

    607 ms

    getbento.com costs a phone 607 ms of main-thread work and 4.3 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.

  • Mobile performance score: 55

    55/100

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

  • Instagram adds 0 ms

    0 ms

    Instagram costs a phone 0 ms of main-thread work and 4.6 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.

  • Google CDN adds 363 ms

    363 ms

    Google CDN costs a phone 363 ms of main-thread work and 742 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.

  • Reduce unused CSS

    230 ms · 81 KiB

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

  • Legacy JavaScript

    150 ms · 35 KiB

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

  • 11 long tasks on the main thread

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

  • Font display

    100 ms

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

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 36.9 s

    36.9 s

    Your largest element takes 36.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 16.4 s

    16.4 s

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

  • Time to Interactive: 40.0 s

    40.0 s

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

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

    +21%

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

  • Total Blocking Time: 360 ms

    360 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 2 images without width and height

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

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

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

    1.7 s

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 409 ms

    409 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 10.8 MB in 86 requests

    10.8 MB

    Your homepage downloads 10.8 MB in 86 requests on a phone: images 6.9 MB (37), scripts 2.7 MB (20) and fonts 660 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (61 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.

  • 3 images below the first screen load straight away

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

  • About 3.1 g of CO₂ per visit

    3.06 g

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

3 to fixGoogle 9697
  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (1 element).

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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 10090
  • 2 H1 headlines

    There are 2 <h1> headlines (“Home” and “Welcome toClyde's Restaurant Group”). One clear main headline is easier for people and search engines.

  • Meta description is long (164 characters)

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

  • 23 internal links, 32 external

    The homepage links to 23 pages on clydesgroup.com and 32 external pages.

6 checks passed
  • Title: 55 characters

    Your title is a healthy 55 characters: “Clyde's Restaurant Group | Hospitality Group in the USA”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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://www.clydesgroup.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

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

Other pages

1 to fix98
  • 8 pages share a meta description

    https://www.clydesgroup.com/concepts, https://www.clydesgroup.com/thanksgiving, https://www.clydesgroup.com/private-events, https://www.clydesgroup.com/reservations, https://www.clydesgroup.com/order-online and https://www.clydesgroup.com/about-crg and 2 others use the same meta description. A description written for each page earns more clicks.

  • 8 internal pages checked

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

7 checks passed
  • Linked pages load

    All 8 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 8 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 9687
  • 14 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://wsv3cdn.audioeye.com/static-scripts/v2/2026-10-29/compliance.css' from origin 'htt…”.

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 341 words of copy

    The homepage carries about 341 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: “JOIN OUR TEAM” and “EMAIL SIGNUP”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop”, “Order Online” and “Join Our Team”.

  • 1 short form

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

Privacy and tracking

  • 10 cookies set on arrival

    10

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

  • 18 other companies contacted

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

1 checks passed
  • 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 clydesgroup.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
Bootstrap
Hosting
Fastly

Company

Founded
1963
Headquarters
Washington, D.C.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on clydesgroup.com, including 18 speed issues, 2 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