Website review, no card needed

berksfoods.com logo

berksfoods.com website review

Visit site (opens in a new tab)Reviewed 23 October 202643 issues · 81 checks

This review found 43 issues worth fixing on berksfoods.com, 17 of them high impact, across 81 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
1.2 s791 msMay 2Oct 17912 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026834 ms
May 9, 2026890 ms
May 16, 2026835 ms
May 23, 2026893 ms
May 30, 2026906 ms
Jun 6, 2026919 ms
Jun 13, 2026933 ms
Jun 20, 2026906 ms
Jun 27, 2026901 ms
Jul 4, 2026867 ms
Jul 11, 2026900 ms
Jul 18, 2026907 ms
Jul 25, 2026921 ms
Aug 1, 2026937 ms
Aug 8, 2026927 ms
Aug 15, 2026911 ms
Aug 22, 2026955 ms
Aug 29, 20261.0 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 2026980 ms
Oct 3, 2026936 ms
Oct 10, 2026912 ms
Oct 17, 2026912 ms
Real-visitor tap response (INP)75th percentile, phones
72 ms62 msMay 2Oct 1766 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202663 ms
May 9, 202666 ms
May 16, 202664 ms
May 23, 202668 ms
May 30, 202668 ms
Jun 6, 202669 ms
Jun 13, 202669 ms
Jun 20, 202668 ms
Jun 27, 202669 ms
Jul 4, 202665 ms
Jul 11, 202667 ms
Jul 18, 202666 ms
Jul 25, 202667 ms
Aug 1, 202670 ms
Aug 8, 202670 ms
Aug 15, 202669 ms
Aug 22, 202670 ms
Aug 29, 202670 ms
Sep 5, 202671 ms
Sep 12, 202671 ms
Sep 19, 202671 ms
Sep 26, 202669 ms
Oct 3, 202668 ms
Oct 10, 202665 ms
Oct 17, 202666 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 berksfoods.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. berksfoods.com at 0.4 s0.4 s
  2. berksfoods.com at 0.8 s0.8 s
  3. berksfoods.com at 1.1 s1.1 s
  4. berksfoods.com at 1.5 s1.5 s
  5. berksfoods.com at 1.9 s1.9 s
  6. berksfoods.com at 2.3 s2.3 s
  7. berksfoods.com at 2.6 s2.6 s
  8. berksfoods.com at 3.0 s3.0 s

Speed

5 to fix63
  • Use efficient cache lifetimes

    12.9 s · 11.0 MB

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

  • Improve image delivery

    7.6 s · 3.9 MB

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

  • Font display

    1.9 s

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

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 66). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 96 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Google Analytics), adding 169 KiB and 170 ms of main-thread time.

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 268 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 16.2 s

    16.2 s

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

  • Time to Interactive: 16.2 s

    16.2 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

8 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: 0.9 s

    0.9 s

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

  • Real-user INP: 63 ms

    63 ms

    Real visitors wait 63 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • 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: 0.5 s

    0.5 s

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

  • Real-user TTFB: 303 ms

    303 ms

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

  • Total Blocking Time: 78 ms

    78 ms

    Scripts block the page for only 78 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 11.1 MB in 56 requests

    11.1 MB

    Your homepage downloads 11.1 MB in 56 requests on a phone: images 10.9 MB (48), scripts 223 KiB (3) and fonts 15 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 10 images over 500 KB

    10 images weigh 7.5 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    821 KiB

    8 images are downloaded at several times the size a phone draws them, for example ph_home-7a-1.png at 1,047 px wide, shown at 312 px. Resized copies would save about 821 KiB.

  • 32 images in older formats

    32 images (10.7 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.

  • 16 images below the first screen load straight away

    16 images further down the page (5.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.2 g of CO₂ per visit

    3.15 g

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

Accessibility

6 to fixGoogle 7685
  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 55 images without alt text

    55 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (27 elements)

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 25 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 30 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

10 to fixGoogle 7352
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (11 characters)

    Your title is only 11 characters: “Berks Foods”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at berksfoods.com/robots.txt, the first file search crawlers ask for.

  • 11 links with vague text

    11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 58 internal links, 10 external

    The homepage links to 58 pages on berksfoods.com and 10 external pages.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix65
  • 2 linked pages are broken

    Your homepage links to https://www.berksfoods.com/products-retail-make-it-easy-hams.htm and https://www.berksfoods.com/products-retail-organic-foods.htm, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 13 pages without a meta description

    https://www.berksfoods.com/products-retail.htm, https://www.berksfoods.com/recipes-hot-dogs.htm, https://www.berksfoods.com/special-offers.htm, https://www.berksfoods.com/about-us.htm, https://www.berksfoods.com/careers.htm and https://www.berksfoods.com/we-care.htm and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.berksfoods.com/products-retail.htm, https://www.berksfoods.com/recipes-hot-dogs.htm, https://www.berksfoods.com/products-retail-hot-dogs.htm, https://www.berksfoods.com/products-retail-ring-bologna.htm, https://www.berksfoods.com/products-retail-hams.htm and https://www.berksfoods.com/products-retail-sausage.htm and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.berksfoods.com/special-offers.htm has 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 26 found) and read each the way a search engine does.

4 checks passed
  • 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 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

  • Only about 173 words

    The homepage has only about 173 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Order Online”, “Contact Us” and “Shop Amazon”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 berksfoods.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2020.

Stack

Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on berksfoods.com, including 10 speed issues, 10 SEO issues and 4 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