Website review, no card needed
aldogroup.com website review
Visit site (opens in a new tab)Reviewed 18 October 202630 issues · 71 checks
This review found 30 issues worth fixing on aldogroup.com, 10 of them high impact, across 71 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.9 s |
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 71 ms |
| May 2, 2026 | 72 ms |
| May 9, 2026 | 72 ms |
| May 16, 2026 | 73 ms |
| May 23, 2026 | 74 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 74 ms |
| Jun 20, 2026 | 71 ms |
| Jun 27, 2026 | 73 ms |
| Jul 4, 2026 | 76 ms |
| Jul 11, 2026 | 76 ms |
| Jul 18, 2026 | 80 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 78 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 81 ms |
| Aug 22, 2026 | 85 ms |
| Aug 29, 2026 | 85 ms |
| Sep 5, 2026 | 85 ms |
| Sep 12, 2026 | 80 ms |
| Sep 19, 2026 | 78 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 73 ms |
| Oct 10, 2026 | 71 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.5 s · 287 KiBAbout 287 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 92). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
500 ms · 74 KiB2 images could be 74 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Legacy JavaScript
350 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Google Tag Manager adds 187 ms
187 msGoogle Tag Manager costs a phone 187 ms of main-thread work and 308 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.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Analytics and sanity.io), adding 434 KiB and 205 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
16 KiB1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).
Phones get a much slower page than desktops
Desktop scores 92 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 411 ms of it running JavaScript. That is comfortably low.
Server response: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 9.9 s
9.9 sYour largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Website_version_courte_Home.png”.
Time to Interactive: 9.9 s
9.9 sThe page becomes fully interactive after 9.9 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 71 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Total Blocking Time: 128 ms
128 msScripts block the page for only 128 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image below the first screen load straight away
1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.41 g of CO₂e: 49.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.4 MB in 63 requests
1.4 MBYour homepage downloads 1.4 MB in 63 requests on a phone: scripts 730 KiB (24), fonts 603 KiB (26) and images 103 KiB (6). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
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.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (10 characters)
Your title is only 10 characters: “Aldo Group”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (10 characters)
Your meta description is only 10 characters: “Aldo Group”. 70 to 160 characters is enough to sell the click.
11 internal links, 3 external
The homepage links to 11 pages on aldogroup.com and 3 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.aldogroup.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.aldogroup.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.aldogroup.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (233 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.aldogroup.com/en/sitemap has no <title>, so Google invents the link text in results.
6 pages point its canonical at the homepage
https://www.aldogroup.com/en/brands, https://www.aldogroup.com/en/aps, https://www.aldogroup.com/en/csr, https://www.aldogroup.com/en/careers, https://www.aldogroup.com/en/news and https://www.aldogroup.com/en/ethics declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
8 pages share a title
https://www.aldogroup.com/en, /, https://www.aldogroup.com/en/brands, https://www.aldogroup.com/en/aps, https://www.aldogroup.com/en/csr and https://www.aldogroup.com/en/careers and 2 others all use the title “Aldo Group”. 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.aldogroup.com/en/sitemap has no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
/, https://www.aldogroup.com/en/brands, https://www.aldogroup.com/en/aps, https://www.aldogroup.com/en/csr, https://www.aldogroup.com/en/careers and https://www.aldogroup.com/en/news and 2 others use the same meta description. A description written for each page earns more clicks.
1 page without an H1
/ has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.aldogroup.com/en/csr, https://www.aldogroup.com/en/contact and https://www.aldogroup.com/en/sitemap 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.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
2 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
2 small tap targets
2 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 211 words
The homepage has only about 211 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Apply Now!”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before 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
5Opening 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.
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.
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 aldogroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Vercel
Company
- Founded
- 1972
- Headquarters
- Montreal
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on aldogroup.com, including 13 speed issues, 3 SEO issues and 4 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.