Website review, no card needed
sysco.ca website review
Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 88 checks
This review found 38 issues worth fixing on sysco.ca, 12 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 79 ms |
| May 23, 2026 | 79 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 79 ms |
| Jun 13, 2026 | 79 ms |
| Jun 20, 2026 | 79 ms |
| Jun 27, 2026 | 80 ms |
| Jul 4, 2026 | 79 ms |
| Jul 11, 2026 | 80 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 80 ms |
| Aug 15, 2026 | 81 ms |
| Aug 22, 2026 | 84 ms |
| Aug 29, 2026 | 86 ms |
| Sep 5, 2026 | 87 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 89 ms |
| Oct 17, 2026 | 92 ms |
| Oct 24, 2026 | 89 ms |
| Oct 31, 2026 | 91 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
How it loaded on a phone
3.7 s
7.5 s
11.2 s
14.9 s
18.6 s
22.4 s
26.1 s
29.8 s
Speed
Improve image delivery
11.1 s · 4.4 MB10 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.1 s faster on a phone.
Use efficient cache lifetimes
3.9 s · 2.0 MB15 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).
Reduce unused JavaScript
1.7 s · 466 KiBAbout 466 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Render-blocking requests
1.4 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
5 third-party services on the page
5 third-party services load with your homepage (Intercom, Tealium and TrustArc and others), adding 7.0 MB and 416 ms of main-thread time.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
620 ms · 105 KiBAbout 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 620 ms faster on a phone.
sysco.com adds 0 ms
0 mssysco.com costs a phone 0 ms of main-thread work and 6.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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 205 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 18.3 s
18.3 sYour largest element takes 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Rooted in Canada Sysco delivers the freshest produce, custo…”.
Speed Index: 13.6 s
13.6 sVisually, the page fills in at 13.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 18.3 s
18.3 sThe page becomes fully interactive after 18.3 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 79 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 94 ms
94 msReal visitors wait 94 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 428 ms
428 msReal visitors wait 428 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 189 ms
189 msScripts block the page for only 189 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Images and page weight
Page weight: 7.7 MB in 61 requests
7.7 MBYour homepage downloads 7.7 MB in 61 requests on a phone: images 6.6 MB (15), scripts 803 KiB (16) and fonts 172 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.20 g of CO₂e: 263.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (4 elements)
Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h5, h1 → h5 and h1 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 2 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“Rooted in Canada”, “Foodservice Distributor” and “Sysco Shop”). 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.
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.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
76 internal links, 19 external
The homepage links to 76 pages on sysco.ca and 19 external pages.
4 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Sysco Canada is a leader among Canadian food distributors and food wholesalers, and a passionate business partner for c…”.
Title: 55 characters
Your title is a healthy 55 characters: “Sysco Canada - Food Service, Distributors & Wholesalers”.
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.sysco.ca/sitemap.xml.
AI search readiness
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.sysco.ca/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 (622 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://www.sysco.ca/en-us all use the title “Sysco Canada - Food Service, Distributors & Wholesalers”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.sysco.ca/en-us/About/Company-Profile/foodie-swag has no meta description, so Google writes the search snippet from whatever text it finds.
11 pages share a meta description
https://www.sysco.ca/en-us and https://www.sysco.ca/fr-ca use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.sysco.ca/en-us/About/Company-Profile/Our-Purpose has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.sysco.ca/en-us/About/Company-Profile/foodie-swag 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 64 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
11 small tap targets
11 of 22 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 “[OPTIMIZELY] - ERROR 2026-11-04T08:57:56.277Z PROJECT_CONFIG_MANAGER: You must provide at least one of sdkKey or datafi…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 435 words of copy
The homepage carries about 435 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE” and “SHOP NOW”.
15 calls to action
The homepage has 15 calls to action, for example “Contact”, “Order Now” and “Contact Us”.
Privacy and tracking
15 cookies set on arrival
15Opening the homepage sets 15 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: TrustArc
A consent management tool (TrustArc) loads with the page.
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 sysco.ca, 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 © 2023.
Stack
- Framework
- Next.js
- Hosting
- Fastly
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on sysco.ca, including 13 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.