Website review, no card needed

ffthospitality.com logo

ffthospitality.com website review

Visit site (opens in a new tab)Reviewed 26 October 202626 issues · 78 checks

This review found 26 issues worth fixing on ffthospitality.com, 9 of them high impact, across 78 checks. The most urgent: wix adds 1.0 s. 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
2.4 s1.5 sSep 26Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
Sep 26, 20261.6 s
Oct 3, 20261.9 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.0 s

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 ffthospitality.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ffthospitality.com at 2.0 s2.0 s
  2. ffthospitality.com at 4.0 s4.0 s
  3. ffthospitality.com at 6.1 s6.1 s
  4. ffthospitality.com at 8.1 s8.1 s
  5. ffthospitality.com at 10.1 s10.1 s
  6. ffthospitality.com at 12.1 s12.1 s
  7. ffthospitality.com at 14.2 s14.2 s
  8. ffthospitality.com at 16.2 s16.2 s

Speed

9 to fix47
  • Wix adds 1.0 s

    1.0 s

    Wix costs a phone 1.0 s of main-thread work and 2.0 MB 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.

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47 (desktop: 79). 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, 3.1 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 (Wix, Google Tag Manager and digitaloceanspaces.com and others), adding 2.9 MB and 1.8 s of main-thread time.

  • Reduce unused JavaScript

    300 ms · 525 KiB

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

  • Use efficient cache lifetimes

    456 KiB

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

  • 15 long tasks on the main thread

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

  • Google Tag Manager adds 313 ms

    313 ms

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

  • 2,327 HTML elements

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

  • Reduce unused CSS

    61 KiB

    About 61 KiB of CSS is downloaded but never applied on this page.

  • Duplicated JavaScript

    35 KiB

    35 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    32 KiB

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

  • Improve image delivery

    16 KiB

    2 images could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 79 but mobile only 47. 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.

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

    26 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 8.7 s

    8.7 s

    Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Event & Business Catering”.

  • Time to Interactive: 17.4 s

    17.4 s

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

  • Speed Index: 11.1 s

    11.1 s

    Visually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 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.

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

    +21%

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

  • Total Blocking Time: 462 ms

    462 ms

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

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

    2.0 s

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

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

    1.7 s

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

  • Real-user TTFB: 575 ms

    575 ms

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

  • Cumulative Layout Shift: 0.025

    0.025

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

Images and page weight

2 to fix64
  • Page weight: 4.0 MB in 252 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 252 requests on a phone: scripts 1.8 MB (104), other files 1.0 MB (94) and images 726 KiB (46). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    8.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.1 g of CO₂ per visit

    1.14 g

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

1 to fixGoogle 9999
  • All page content should be contained by landmarks (2 elements)

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

  • Headings skip levels

    Headings skip levels (h3 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 51 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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 9288
  • No H1 headline

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 95 internal links, 36 external

    The homepage links to 95 pages on ffthospitality.com and 36 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “At FFT we specialize in experiential catering. Find out why we're one of Chicago's leading catering companies for busin…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Event & Business Catering in Chicago | Food For Thought”.

  • Canonical URL set

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

  • Structured data in place

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

AI search readiness

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

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

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.ffthospitality.com/llms.txt (3 KiB, 3 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without an H1

    https://www.ffthospitality.com/catering, https://www.ffthospitality.com/catering/weddings, https://www.ffthospitality.com/catering/corporate-events, https://www.ffthospitality.com/catering/social-events, https://www.ffthospitality.com/catering/fft-afar and https://www.ffthospitality.com/featured-venues and 9 others 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 27 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

  • About 899 words of copy

    The homepage carries about 899 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CALL NOW”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “JOIN OUR TEAM”, “INQUIRE” and “CALL NOW”.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 2 email links.

  • 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

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.

  • 15 cookies set on arrival

    15

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 ffthospitality.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
Wix
Framework
React
Hosting
Wix

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on ffthospitality.com, including 15 speed issues, 2 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