Website review, no card needed
aubut.ca website review
Visit site (opens in a new tab)Reviewed 22 October 202638 issues · 88 checks
This review found 38 issues worth fixing on aubut.ca, 12 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 862 ms |
| May 9, 2026 | 882 ms |
| May 16, 2026 | 906 ms |
| May 23, 2026 | 907 ms |
| May 30, 2026 | 889 ms |
| Jun 6, 2026 | 861 ms |
| Jun 13, 2026 | 841 ms |
| Jun 20, 2026 | 824 ms |
| Jun 27, 2026 | 814 ms |
| Jul 4, 2026 | 823 ms |
| Jul 11, 2026 | 825 ms |
| Jul 18, 2026 | 825 ms |
| Jul 25, 2026 | 802 ms |
| Aug 1, 2026 | 780 ms |
| Aug 8, 2026 | 773 ms |
| Aug 15, 2026 | 763 ms |
| Aug 22, 2026 | 773 ms |
| Aug 29, 2026 | 798 ms |
| Sep 5, 2026 | 812 ms |
| Sep 12, 2026 | 834 ms |
| Sep 19, 2026 | 841 ms |
| Sep 26, 2026 | 843 ms |
| Oct 3, 2026 | 829 ms |
| Oct 10, 2026 | 817 ms |
| Oct 17, 2026 | 828 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 80 ms |
| May 9, 2026 | 79 ms |
| May 16, 2026 | 79 ms |
| May 23, 2026 | 79 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 81 ms |
| Jun 20, 2026 | 85 ms |
| Jun 27, 2026 | 86 ms |
| Jul 4, 2026 | 86 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 88 ms |
| Aug 1, 2026 | 88 ms |
| Aug 8, 2026 | 90 ms |
| Aug 15, 2026 | 91 ms |
| Aug 22, 2026 | 91 ms |
| Aug 29, 2026 | 93 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 93 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 93 ms |
| Oct 10, 2026 | 94 ms |
| Oct 17, 2026 | 94 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
Speed
Reduce unused JavaScript
3.5 s · 886 KiBAbout 886 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Improve image delivery
1.6 s · 267 KiB1 image could be 267 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Maps, Google Tag Manager and Facebook and others), adding 1.9 MB and 1.2 s of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 67). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
500 ms · 338 KiB10 files are served with short cache lifetimes, so returning visitors download them again (338 KiB).
Google Maps adds 438 ms
438 msGoogle Maps costs a phone 438 ms of main-thread work and 925 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.
Google Tag Manager adds 421 ms
421 msGoogle Tag Manager costs a phone 421 ms of main-thread work and 653 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: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
300 ms · 49 KiBAbout 49 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.
Minify JavaScript
300 ms · 18 KiB18 KiB could be saved by minifying JavaScript.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 272 ms. During a long task the page ignores taps.
2,533 HTML elements
The page has 2,533 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need.
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: 30 ms
30 msYour server sent the HTML in 30 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Background”.
Time to Interactive: 17.3 s
17.3 sThe page becomes fully interactive after 17.3 s. Good is under 3.8 s.
Total Blocking Time: 451 ms
451 msScripts block taps and scrolling for 451 ms in total while the page loads. Good is under 200 ms.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.141
0.141The layout shifts by 0.141 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 80 ms to 94 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.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 102 ms
102 msReal visitors wait 102 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 406 ms
406 msReal visitors wait 406 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 2.6 MB in 96 requests
2.6 MBYour homepage downloads 2.6 MB in 96 requests on a phone: scripts 2.0 MB (46), images 420 KiB (17) and fonts 96 KiB (6). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
216 KiB1 image is downloaded at several times the size a phone draws it, for example 130.webp at 1,152 px wide, shown at 199 px. Resized copies would save about 216 KiB.
About 0.7 g of CO₂ per visit
0.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 89.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
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.
23 images without alt text
23 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
30 form fields without a label
30 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Grossiste alimentaire Montréal Laval | Distribution alimentaire Aubut”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (189 characters)
Your meta description is 189 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
149 internal links, 3 external
The homepage links to 149 pages on aubut.ca and 3 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Grossiste alimentaire”.
Canonical URL set
The canonical URL is https://www.aubut.ca/.
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://www.aubut.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.aubut.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 (917 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.aubut.ca/panier is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages share a meta description
https://www.aubut.ca/trouver-magasin, https://www.aubut.ca/trouver-magasin/laval and https://www.aubut.ca/trouver-magasin/montreal use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
39 of 40 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 1,283 words of copy
The homepage carries about 1,283 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
24 other companies contacted
Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 aubut.ca, 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 Tag Manager
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 aubut.ca, including 19 speed issues, 3 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.