Website review, no card needed
factry.ca website review
Visit site (opens in a new tab)Reviewed 21 October 202630 issues · 72 checks
This review found 30 issues worth fixing on factry.ca, 15 of them high impact, across 72 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 137 ms |
| May 16, 2026 | 122 ms |
| May 23, 2026 | 122 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 123 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 118 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.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.4 s
6.3 s
7.2 s
Speed
Reduce unused JavaScript
2.7 s · 680 KiBAbout 680 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 1.1 MB16 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Google Tag Manager adds 2.6 s
2.6 sGoogle Tag Manager costs a phone 2.6 s of main-thread work and 816 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
2.6 s63 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Main-thread work: 11.5 s
A phone's processor spends 11.5 s on main-thread work while loading, 6.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 24
24/100Your mobile performance score is 24 (desktop: 62). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Hubspot and Segment and others), adding 1.2 MB and 3.4 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 823 ms. During a long task the page ignores taps.
Hubspot adds 719 ms
719 msHubspot costs a phone 719 ms of main-thread work and 332 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.
Improve image delivery
400 ms · 89 KiB1 image could be 89 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
1,931 HTML elements
The page has 1,931 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 62 but mobile only 24. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.5 s
21.5 sYour largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Les individus capables de créativité et les organisations m…”.
Total Blocking Time: 4.4 s
4.4 sScripts block taps and scrolling for 4.4 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 23.9 s
23.9 sThe page becomes fully interactive after 23.9 s. Good is under 3.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.112
0.112The layout shifts by 0.112 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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 137 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
Images and page weight
Page weight: 4.1 MB in 261 requests
4.1 MBYour homepage downloads 4.1 MB in 261 requests on a phone: scripts 1.6 MB (96), other files 1.6 MB (82) and images 788 KiB (9). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 140.2 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
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (152 elements)
All page content should be contained by landmarks: 152 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found ((untyped)) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.
No robots.txt
There is no robots.txt at factry.lcieducation.com/robots.txt, the first file search crawlers ask for.
Open Graph partly set
Open Graph is missing og:title, so shared links fall back to guesses.
68 internal links, 11 external
The homepage links to 68 pages on factry.ca and 11 external pages.
5 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Apprendre la créativité, c’est possible. Découvrez nos formations conçues par des experts pour les professionnels de to…”.
One H1 headline
Your main headline reads: “À la Factry, on met la créativité au travail.”.
Title: 62 characters
Your title is a healthy 62 characters: “À la Factry, nous mettons la créativité à l'œuvre. | La Factry”.
Canonical URL set
The canonical URL is https://factry.lcieducation.com/.
XML sitemap found
Your XML sitemap is reachable at https://factry.lcieducation.com/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://factry.lcieducation.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (708 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://factry.lcieducation.com/fr/formations/formations-sur-mesure and https://factry.lcieducation.com/fr/formations/propulseinfopresse all use the title “Programmes pour la relève Factry: élargissez vos horizons | La Factry”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages share a meta description
https://factry.lcieducation.com/fr/solutions-entreprises, https://factry.lcieducation.com/fr/solutions-entreprises/transformation-equipes, https://factry.lcieducation.com/fr/solutions-entreprises/transformation-organisation, https://factry.lcieducation.com/fr/solutions-entreprises/evenements-corporatifs, https://factry.lcieducation.com/fr/formations/formations-sur-mesure and https://factry.lcieducation.com/fr/formations/propulseinfopresse and 4 others use the same meta description. A description written for each page earns more clicks.
4 pages slow to respond
https://factry.lcieducation.com/fr/blogue/batir-sur-des-fondations-solides-limportance-des-softs-skills-en-ingenierie-et-en-construction, https://factry.lcieducation.com/fr/blogue/idee-hors-norme, https://factry.lcieducation.com/fr/blogue/culture-mobilisante-daniel-lamarre and https://factry.lcieducation.com/fr/blogue/marie-amiot-raison-lever took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 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 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 1 customer or partner logo. 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.
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 700 words of copy
The homepage carries about 700 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, LinkedIn Insight and Segment (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 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 factry.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- 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 30 issues on factry.ca, including 17 speed issues, 2 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.