Website review, no card needed

georgesatthecove.com logo

georgesatthecove.com website review

Visit site (opens in a new tab)Reviewed 21 October 202636 issues · 86 checks

This review found 36 issues worth fixing on georgesatthecove.com, 14 of them high impact, across 86 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
1.9 s1.8 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
88 ms77 msMay 2Oct 1781 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202680 ms
May 9, 202679 ms
May 16, 202683 ms
May 23, 202685 ms
May 30, 202687 ms
Jun 6, 202687 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202686 ms
Jul 4, 202683 ms
Jul 11, 202681 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202678 ms
Aug 8, 202678 ms
Aug 15, 202680 ms
Aug 22, 202680 ms
Aug 29, 202686 ms
Sep 5, 202687 ms
Sep 12, 202686 ms
Sep 19, 202687 ms
Sep 26, 202685 ms
Oct 3, 202683 ms
Oct 10, 202683 ms
Oct 17, 202681 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 georgesatthecove.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. georgesatthecove.com at 0.4 s0.4 s
  2. georgesatthecove.com at 0.9 s0.9 s
  3. georgesatthecove.com at 1.3 s1.3 s
  4. georgesatthecove.com at 1.8 s1.8 s
  5. georgesatthecove.com at 2.2 s2.2 s
  6. georgesatthecove.com at 2.7 s2.7 s
  7. georgesatthecove.com at 3.1 s3.1 s
  8. georgesatthecove.com at 3.6 s3.6 s

Speed

15 to fix32
  • Reduce unused JavaScript

    9.3 s · 1.5 MB

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

  • Render-blocking requests

    2.5 s

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

  • Use efficient cache lifetimes

    2.1 s · 319 KiB

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

  • Mobile performance score: 32

    32/100

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

  • Main-thread work: 5.4 s

    A phone's processor spends 5.4 s on main-thread work while loading, 2.4 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 (Squarespace, Google CDN and iubenda and others), adding 3.5 MB and 2.1 s of main-thread time.

  • Reduce unused CSS

    900 ms · 215 KiB

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

  • Squarespace adds 812 ms

    812 ms

    Squarespace costs a phone 812 ms of main-thread work and 1.5 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 494 ms

    494 ms

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

  • Legacy JavaScript

    450 ms · 111 KiB

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

  • iubenda adds 402 ms

    402 ms

    iubenda costs a phone 402 ms of main-thread work and 125 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.

  • Improve image delivery

    329 KiB

    1 image could be 329 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 20 long tasks on the main thread

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

  • exploretock.com adds 104 ms

    104 ms

    exploretock.com costs a phone 104 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.

  • Adobe TypeKit adds 5 ms

    5 ms

    Adobe TypeKit costs a phone 5 ms of main-thread work and 407 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.

  • 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: 45 ms

    45 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 8.5 s

    8.5 s

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

  • Largest Contentful Paint: 24.8 s

    24.8 s

    Your largest element takes 24.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “George's at the Cove logo mark”.

  • Time to Interactive: 26.6 s

    26.6 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • 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

    +3%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

7 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: 2.3 s

    2.3 s

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

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 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.

  • Real-user TTFB: 446 ms

    446 ms

    Real visitors wait 446 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: 4.5 MB in 108 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 108 requests on a phone: scripts 2.8 MB (59), fonts 525 KiB (12) and other files 495 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.28 g

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

3 to fixGoogle 9796
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 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.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

5 to fixGoogle 9272
  • No H1 headline

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

  • Title is short (19 characters)

    Your title is only 19 characters: “Georges at the Cove”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (198 characters)

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

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/64247d76d617127ecef…”.

  • 2 links crawlers can't follow

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

  • 75 internal links, 4 external

    The homepage links to 75 pages on georgesatthecove.com and 4 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.georgesatthecove.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.georgesatthecove.com/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.georgesatthecove.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 (561 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.georgesatthecove.com/menu-lunch, https://www.georgesatthecove.com/menu-dinner, https://www.georgesatthecove.com/little-luxuries-menu, https://www.georgesatthecove.com/menu-beverages, https://www.georgesatthecove.com/ocean-terrace and https://www.georgesatthecove.com/level2 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.georgesatthecove.com/gift-cards, https://www.georgesatthecove.com/directions and https://www.georgesatthecove.com/contact 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 28 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.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/64247d76d617127ecef1930f/338/5c5…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 361 words of copy

    The homepage carries about 361 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “Join Our Email List” and “BOOK A RESERVATION”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 16 other companies contacted

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

2 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) 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 georgesatthecove.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
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 36 issues on georgesatthecove.com, including 21 speed issues, 5 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