Website review, no card needed

kayco.com logo

kayco.com website review

Visit site (opens in a new tab)Reviewed 20 October 202648 issues · 91 checks

This review found 48 issues worth fixing on kayco.com, 15 of them high impact, across 91 checks. The most urgent: page weight: 34.0 MB in 169 requests. 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
3.9 s1.1 sMay 2Oct 173.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.9 s
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.9 s
Jul 4, 20262.4 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.0 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.5 s
Sep 5, 20263.6 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.3 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
78 ms61 msMay 2Oct 1771 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202670 ms
May 9, 202670 ms
May 16, 202669 ms
May 23, 202663 ms
May 30, 202667 ms
Jun 6, 202663 ms
Jun 13, 202663 ms
Jun 20, 202663 ms
Jun 27, 202663 ms
Jul 4, 202669 ms
Jul 11, 202671 ms
Jul 18, 202676 ms
Jul 25, 202672 ms
Aug 1, 202671 ms
Aug 8, 202671 ms
Aug 15, 202671 ms
Aug 22, 202672 ms
Aug 29, 202674 ms
Sep 5, 202676 ms
Sep 12, 202674 ms
Sep 19, 202672 ms
Sep 26, 202672 ms
Oct 3, 202671 ms
Oct 10, 202670 ms
Oct 17, 202671 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 kayco.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kayco.com at 0.7 s0.7 s
  2. kayco.com at 1.3 s1.3 s
  3. kayco.com at 2.0 s2.0 s
  4. kayco.com at 2.6 s2.6 s
  5. kayco.com at 3.3 s3.3 s
  6. kayco.com at 3.9 s3.9 s
  7. kayco.com at 4.6 s4.6 s
  8. kayco.com at 5.2 s5.2 s

Speed

8 to fix71
  • Render-blocking requests

    3.1 s

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

  • Use efficient cache lifetimes

    550 ms · 33.6 MB

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

  • Improve image delivery

    31.1 MB

    97 images could be 31.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 71

    71/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Fonts and others), adding 410 KiB and 502 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 19 KiB

    About 19 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 277 ms

    277 ms

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

  • Main-thread work: 2.1 s

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

  • Font display

    250 ms

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

  • 8 long tasks on the main thread

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

  • Reduce unused JavaScript

    137 KiB

    About 137 KiB of JavaScript is downloaded but never used on this page.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 20 ms

    20 ms

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

Core Web Vitals

12 to fix0
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 5.2 s

    5.2 s

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

  • Real-user FCP: 4.7 s

    4.7 s

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

  • Real-user TTFB: 4.2 s

    4.2 s

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

  • Speed Index: 8.6 s

    8.6 s

    Visually, the page fills in at 8.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.

  • Real-user CLS: 0.12

    0.12

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

  • Largest content (LCP) got 72% slower for real visitors

    +72%

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

  • 87 images without width and height

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

    Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Kayco is the leading Kosher food distributor in America”. Most of its time is element render delay (4.9 s).

  • Time to Interactive: 6.2 s

    6.2 s

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

  • Total Blocking Time: 276 ms

    276 ms

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

  • Tap response (INP) held steady for real visitors

    +1%

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

1 checks passed
  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

5 to fix18
  • Page weight: 34.0 MB in 169 requests

    34.0 MB

    Your homepage downloads 34.0 MB in 169 requests on a phone: images 33.3 MB (121), scripts 466 KiB (27) and fonts 210 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 21 images over 500 KB

    21 images weigh 29.2 MB together. On a phone connection a single image that size takes seconds.

  • 33 images far larger than shown

    16.5 MB

    33 images are downloaded at several times the size a phone draws them, for example 710752.png at 1,553 px wide, shown at 194 px. Resized copies would save about 16.5 MB.

  • 40 images in older formats

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

  • 40 images below the first screen load straight away

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

  • About 9.6 g of CO₂ per visit

    9.64 g

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

Accessibility

8 to fixGoogle 8690
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

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

    All page content should be contained by landmarks: 12 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.

  • 5 links without text

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

  • 2 form fields without a label

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 120 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 9273
  • No H1 headline

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

  • Title is short (12 characters)

    Your title is only 12 characters: “Home - Kayco”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (200 characters)

    Your meta description is 200 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 149 internal links, 5 external

    The homepage links to 149 pages on kayco.com and 5 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.kayco.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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://www.kayco.com/sitemap_index.xml.

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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix65
  • 1 linked page is broken

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

  • 14 pages without a meta description

    https://www.kayco.com/brands, https://www.kayco.com/products, https://www.kayco.com/categories, https://www.kayco.com/about, https://www.kayco.com/contact and https://www.kayco.com/brands/manischewitz and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.kayco.com/brands, https://www.kayco.com/products, https://www.kayco.com/categories, https://www.kayco.com/about, https://www.kayco.com/contact and https://www.kayco.com/brands/manischewitz and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.kayco.com/brands and https://www.kayco.com/contact 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.

  • 1 page slow to respond

    https://www.kayco.com/products took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 139 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

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

  • Thin social proof

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

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

  • About 437 words of copy

    The homepage carries about 437 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 9 cookies set on arrival

    9

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

  • 6 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
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 48 issues on kayco.com, including 20 speed issues, 5 SEO issues and 3 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