4c.com website review

Not measured in this review.

• Real-user TTFB: 1.0 s

  1.0 s

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

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

  +19%

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

• Largest content (LCP) held steady for real visitors

  -7%

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

• Page weight: 4.6 MB

  4.6 MB

  Your homepage downloads 4.6 MB on a phone, 3.8 MB of it images (83%). Under 2 MB keeps phones on slow connections fast.

• 9 images in older formats

  9 images (507 KiB) 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.

  Elements (5)

• 4 images below the first screen load straight away

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

  Elements (4)

• About 1.3 g of CO₂ per visit

  1.30 g

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

• 2 text elements with low contrast

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

  Elements (2)

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

  Elements (2)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• 2 links without text

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

  Elements (2)

• Headings skip levels

  Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

  View sourceElements (1)

• 7 H1 headlines

  There are 7 <h1> headlines (“Bread Crumbs & Gluten Free Crumbs”, “Iced Tea & Drink Mixes” and “Iced Tea & Drink Mix Pitcher Packs”). One clear main headline is easier for people and search engines.

  View source

• No social preview image

  No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  View source

• No XML sitemap

  No XML sitemap at https://www.4c.com/wp-sitemap.xml, so Google discovers your pages only by following links.

• 33 internal links, 4 external

  The homepage links to 33 pages on 4c.com and 4 external pages.

• No llms.txt

  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.

• 15 pages without a meta description

  /customer-contact, /where-to-buy, /frequently-asked-questions, /jobs, /news and /caffeine-content and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 4 pages without an H1

  /frequently-asked-questions, /jobs, /news and /military-home have no <h1> headline, so visitors and search engines get no clear main topic.

• 10 pages with very little text

  /customer-contact, /where-to-buy, /military-home, /products/bread-crumbs-gluten-free-crumbs, /products/iced-tea-drink-mixes and /products/iced-tea-drink-mix-pitcher-packs and 4 others 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.

• 15 internal pages checked

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

• 8 small tap targets

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

• 2 insecure resources on an https page

  2 resources load over plain http on your https page (for example http://www.4c.com/wp-content/uploads/2017/10/founder.png); browsers block or warn about them.

• HTTP/1.1 only

  The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

• No X-Content-Type-Options

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

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

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

• No CAA record

  4c.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.

• DNSSEC is off

  4c.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.

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

  The homepage carries about 354 words of visible text.

• No DMARC policy

  4c.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 40/100

  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.

• 3 trackers load before any consent

  3

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

• 4 cookies set on arrival

  4

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

• 7 other companies contacted

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