Website review, no card needed

100kmfoods.com logo

100kmfoods.com website review

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

This review found 36 issues worth fixing on 100kmfoods.com, 15 of them high impact, across 79 checks. The most urgent: improve image delivery. 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

Full-page screenshot of 100kmfoods.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 100kmfoods.com at 0.6 s0.6 s
  2. 100kmfoods.com at 1.3 s1.3 s
  3. 100kmfoods.com at 1.9 s1.9 s
  4. 100kmfoods.com at 2.6 s2.6 s
  5. 100kmfoods.com at 3.2 s3.2 s
  6. 100kmfoods.com at 3.9 s3.9 s
  7. 100kmfoods.com at 4.5 s4.5 s
  8. 100kmfoods.com at 5.1 s5.1 s

Speed

7 to fix33
  • Improve image delivery

    23.6 s · 12.4 MB

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

  • Reduce unused JavaScript

    7.5 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 7.5 s faster on a phone.

  • Mobile performance score: 33

    33/100

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

  • Reduce unused CSS

    900 ms · 196 KiB

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

  • Render-blocking requests

    450 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • 3 long tasks on the main thread

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

  • 2,847 HTML elements

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

  • Legacy JavaScript

    200 ms · 10 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Cloudflare CDN, Google Fonts and Hubspot), adding 103 KiB and 2 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 47 ms

    47 ms

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

Core Web Vitals

7 to fix29
  • Largest Contentful Paint: 41.1 s

    41.1 s

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

  • Time to Interactive: 41.3 s

    41.3 s

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

  • Cumulative Layout Shift: 0.474

    0.474

    The layout shifts by 0.474 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 7.6 s

    7.6 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Total Blocking Time: 381 ms

    381 ms

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

  • 8 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

6 to fix19
  • Page weight: 19.9 MB in 128 requests

    19.9 MB

    Your homepage downloads 19.9 MB in 128 requests on a phone: images 17.7 MB (112), scripts 1.9 MB (7) and stylesheets 216 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 7 images over 500 KB

    7 images weigh 7.3 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    948 KiB

    6 images are downloaded at several times the size a phone draws them, for example 0000358_100km Foods Wholesale About Us Slider.png at 1,370 px wide, shown at 390 px. Resized copies would save about 948 KiB.

  • 40 images in older formats

    40 images (11.5 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.

  • An image on the first screen is lazy-loaded

    0000358_100km Foods Wholesale About Us Slider.png 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).

  • 8 images below the first screen load straight away

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

  • About 5.6 g of CO₂ per visit

    5.64 g

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

Accessibility

7 to fixGoogle 8391
  • 25 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 9 images without alt text

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

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

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

  • 9 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • Meta description is short (26 characters)

    Your meta description is only 26 characters: “Your home page description”. 70 to 160 characters is enough to sell the click.

  • 6 H1 headlines

    There are 6 <h1> headlines (“Wholesale Local Food Distributor”, “We Connect Chefs With 100+ Ontario Producers” and “Why Choose Us?”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://100kmfoods.com/images/thumbs/0000130_100km Logo…”.

  • 6 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 484 internal links, 14 external

    The homepage links to 484 pages on 100kmfoods.com and 14 external pages.

5 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “100km Foods | Wholesale Local Food Distributor”.

  • Canonical URL set

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

AI search readiness

1 to fix65
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No llms.txt

    There is no https://100kmfoods.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.

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

2 checks passed
  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 12 pages without a meta description

    https://100kmfoods.com/volume-discounts, https://100kmfoods.com/vegetables, https://100kmfoods.com/squash-zucchini, https://100kmfoods.com/peas-beans-corn, https://100kmfoods.com/mushrooms and https://100kmfoods.com/lettuce-leafy-vegetables and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://100kmfoods.com/contactus, whose canonical is https://100kmfoods.com/contact. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages slow to respond

    https://100kmfoods.com/squash-zucchini, https://100kmfoods.com/peas-beans-corn and https://100kmfoods.com/chicory-endive took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 197 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 96100
  • 3 low-resolution images

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

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No analytics detected

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

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

    The homepage carries about 982 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “REQUEST AN ACCOUNT”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “CONTACT US”, “REQUEST AN ACCOUNT” and “Register”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

Privacy and tracking

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

  • 4 other companies contacted

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

1 checks passed
  • 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 100kmfoods.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on 100kmfoods.com, including 14 speed issues, 4 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