eatmycatfish.com website review

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

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

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

Google Tag Manager costs a phone 1.6 s of main-thread work and 1.1 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.

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

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

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

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

About 84 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.

Facebook costs a phone 465 ms of main-thread work and 314 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.

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

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

Hotjar costs a phone 320 ms of main-thread work and 65 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.

Clarity costs a phone 284 ms of main-thread work and 28 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying CSS.

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.

Your largest element takes 26.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Delicious fried catfish and side dishes”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 137 requests on a phone: scripts 1.9 MB (55), images 1.7 MB (20) and fonts 312 KiB (6). Under 2 MB keeps phones on slow connections fast.

Gumbo-1.png weighs 713 KiB. On a phone connection a single image that size takes seconds.

4 images (1.2 MB) are 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 are downloaded at several times the size a phone draws them, for example Gumbo-1.png at 1,536 px wide, shown at 507 px. Resized copies would save about 201 KiB.

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

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

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

4 visible links have no text or label, so screen readers cannot say where they go.

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

Your meta description is only 21 characters: “Eat Local. Eat Fresh.”. 70 to 160 characters is enough to sell the click.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

The homepage links to 48 pages on eatmycatfish.com and 4 external pages.

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.

There is no /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.

/locations, /menu, /vip-club, /our-story, /catering and /home-draft/fundraiser and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

eatmycatfish.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

eatmycatfish.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 468 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be eatmycatfish.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.

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

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.

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