Website review, no card needed
adij22.bzh website review
Visit site (opens in a new tab)Reviewed 4 November 202641 issues · 80 checks
This review found 41 issues worth fixing on adij22.bzh, 17 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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
70C- #104,629 of 125,753 reviewed websitesbeats 14%
- #63,056 of 70,254 online storesbeats 8%
- #2,258 of 2,951 WooCommerce storesbeats 19%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
6.2 s · 5.7 MB98 files are served with short cache lifetimes, so returning visitors download them again (5.7 MB).
Improve image delivery
3.3 s · 3.6 MB15 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
3.0 s43 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,646 HTML elements
The page has 3,646 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
4 third-party services on the page
4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and JSDelivr CDN and others), adding 864 KiB and 721 ms of main-thread time.
Google CDN adds 637 ms
637 msGoogle CDN costs a phone 637 ms of main-thread work and 736 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.
Reduce unused JavaScript
170 ms · 485 KiBAbout 485 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 170 ms faster on a phone.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
170 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 218 ms. During a long task the page ignores taps.
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 498 ms
498 msYour server sent the HTML in 498 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.6 s
13.6 sYour largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Rassembler Informer et Accompagner Notre association”.
Time to Interactive: 18.4 s
18.4 sThe page becomes fully interactive after 18.4 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 336 ms
336 msScripts block taps and scrolling for 336 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.138
0.138The layout shifts by 0.138 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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: 8.6 MB in 115 requests
8.6 MBYour homepage downloads 8.6 MB in 115 requests on a phone: images 5.2 MB (25), other files 1.5 MB (5) and scripts 1.1 MB (44). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
ADIJ22-HEADER-HOME-PAGE-01-1.png weighs 1.4 MB. On a phone connection a single image that size takes seconds.
7 images far larger than shown
1.5 MB7 images are downloaded at several times the size a phone draws them, for example ADIJ22-HEADER-HOME-PAGE-01-1.png at 1,000 px wide, shown at 330 px. Resized copies would save about 1.5 MB.
9 images in older formats
9 images (3.3 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.
7 images below the first screen load straight away
7 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
ADIJ22-HEADER-HOME-PAGE-01-1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 2.4 g of CO₂ per visit
2.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.44 g of CO₂e: 293.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
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.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (16 characters)
Your title is only 16 characters: “Accueil - ADIJ22”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“Rassembler Informer et Accompagner” and “Rassembler Informer et Accompagner”). One clear main headline is easier for people and search engines.
Meta description is long (187 characters)
Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.
195 internal links, 14 external
The homepage links to 195 pages on adij22.bzh and 14 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.adij22.bzh/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.adij22.bzh/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.adij22.bzh/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 (1,177 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share 3 titles
https://www.adij22.bzh/pour-nos-partenaires-et-professionnels/je-cherche-je-trouve and https://www.adij22.bzh/pour-les-jeunes/je-cherche-je-trouve all use the title “Je cherche / Je trouve - ADIJ22”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://www.adij22.bzh/agenda, https://www.adij22.bzh/ressources, https://www.adij22.bzh/contact, https://www.adij22.bzh/boutique, https://www.adij22.bzh/notre-association/decouvrir-ladij22 and https://www.adij22.bzh/notre-association/s-engager and 9 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.adij22.bzh/agenda, https://www.adij22.bzh/ressources, https://www.adij22.bzh/contact, https://www.adij22.bzh/boutique, https://www.adij22.bzh/notre-association/decouvrir-ladij22 and https://www.adij22.bzh/notre-association/s-engager and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://www.adij22.bzh/agenda, https://www.adij22.bzh/ressources, https://www.adij22.bzh/contact, https://www.adij22.bzh/boutique, https://www.adij22.bzh/notre-association/decouvrir-ladij22 and https://www.adij22.bzh/notre-association/s-engager and 9 others 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.adij22.bzh/boutique took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 94 found) and read each the way a search engine does.
5 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.
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
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
7 of 8 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.
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 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 812 words of copy
The homepage carries about 812 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact”.
12 short forms
12 short forms (0 fields at most) are right on the homepage.
Privacy and tracking
9 cookies set on arrival
9Opening 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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
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 adij22.bzh, 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
- Hosting
- O2switch
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on adij22.bzh, including 16 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.