Website review, no card needed

bakecrafters.com logo

bakecrafters.com website review

Visit site (opens in a new tab)Reviewed 22 October 202643 issues · 88 checks

This review found 43 issues worth fixing on bakecrafters.com, 16 of them high impact, across 88 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

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.3 sMay 2Oct 171.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.5 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.8 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.5 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
104 ms76 msMay 2Oct 1786 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202695 ms
May 9, 202692 ms
May 16, 2026101 ms
May 23, 202696 ms
May 30, 2026101 ms
Jun 6, 202694 ms
Jun 13, 202691 ms
Jun 20, 202685 ms
Jun 27, 202688 ms
Jul 4, 202693 ms
Jul 11, 202680 ms
Jul 18, 202689 ms
Jul 25, 202687 ms
Aug 1, 202694 ms
Aug 8, 202696 ms
Aug 15, 202682 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202692 ms
Sep 19, 202695 ms
Sep 26, 202692 ms
Oct 3, 202686 ms
Oct 10, 202687 ms
Oct 17, 202686 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 bakecrafters.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix54
  • Improve image delivery

    6.7 s · 10.6 MB

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

  • Use efficient cache lifetimes

    11.4 s · 2.1 MB

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

  • Render-blocking requests

    11.0 s

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

  • Reduce unused JavaScript

    5.6 s · 946 KiB

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

  • Reduce unused CSS

    3.4 s · 621 KiB

    About 621 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.4 s faster on a phone.

  • Minify JavaScript

    3.4 s · 516 KiB

    516 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 54

    54/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google Analytics and Browser-Update.org and others), adding 6.0 MB and 223 ms of main-thread time.

  • ghost.io adds 0 ms

    0 ms

    ghost.io costs a phone 0 ms of main-thread work and 5.6 MB 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.

  • Google Tag Manager adds 195 ms

    195 ms

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

  • 4 long tasks on the main thread

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

  • Font display

    100 ms

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

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

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

  • Server response: 25 ms

    25 ms

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

Core Web Vitals

5 to fix100
  • First Contentful Paint: 12.2 s

    12.2 s

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

  • Largest Contentful Paint: 35.8 s

    35.8 s

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

  • Time to Interactive: 37.3 s

    37.3 s

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

  • Speed Index: 14.9 s

    14.9 s

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 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: 1.5 s

    1.5 s

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

  • Real-user INP: 84 ms

    84 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 513 ms

    513 ms

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

  • Total Blocking Time: 136 ms

    136 ms

    Scripts block the page for only 136 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: 13.0 MB in 33 requests

    13.0 MB

    Your homepage downloads 13.0 MB in 33 requests on a phone: images 10.8 MB (18), scripts 1.5 MB (6) and stylesheets 643 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 10 images over 500 KB

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

  • 6 images far larger than shown

    5.4 MB

    6 images are downloaded at several times the size a phone draws them, for example vlcsnap-2023-11-22-16h40m32s439.png at 1,920 px wide, shown at 153 px. Resized copies would save about 5.4 MB.

  • 15 images in older formats

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

  • 8 images below the first screen load straight away

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

  • About 3.7 g of CO₂ per visit

    3.69 g

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

Accessibility

8 to fixGoogle 8088
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 7 images without alt text

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

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

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

  • No main landmark

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails 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.

  • 7 form fields without a label

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

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

5 to fixGoogle 8382
  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Delicious Solutions for All Industries! K12! Food…” and “Sorry, no results found.”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

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

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 33 internal links, 15 external

    The homepage links to 33 pages on bakecrafters.com and 15 external pages.

4 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Breakfast, Lunch and Snack solutions for your K12, C&amp;U, Military, Restaurant, Healthcare, In-store bakery, or c-sto…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Wholesale baked goods | K12, healthcare, military, restaurants”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://bakecrafters.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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://bakecrafters.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.

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

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://bakecrafters.com/about/careers, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a meta description

    https://bakecrafters.com/news/celebrating-the-power-of-school-lunch and https://bakecrafters.com/news/french-toast-favorites-students-love have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix67
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • A 55-field form

    Your longest form asks for 55 fields (0 required). Every extra field lowers completion.

  • 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 59 words

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

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”, “Contact Us!” and “Create & Download Sales Sheet”.

  • Analytics in place

    Analytics detected: Google Tag Manager and 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.

  • 5 cookies set on arrival

    5

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

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager

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 bakecrafters.com, including 15 speed issues, 5 SEO issues and 6 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