Website review, no card needed
ifocop.fr website review
Visit site (opens in a new tab)Reviewed 28 October 202627 issues · 87 checks
This review found 27 issues worth fixing on ifocop.fr, 10 of them high impact, across 87 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 915 ms |
| May 16, 2026 | 928 ms |
| May 23, 2026 | 924 ms |
| May 30, 2026 | 919 ms |
| Jun 6, 2026 | 914 ms |
| Jun 13, 2026 | 906 ms |
| Jun 20, 2026 | 925 ms |
| Jun 27, 2026 | 951 ms |
| Jul 4, 2026 | 988 ms |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 166 ms |
| May 16, 2026 | 167 ms |
| May 23, 2026 | 167 ms |
| May 30, 2026 | 167 ms |
| Jun 6, 2026 | 168 ms |
| Jun 13, 2026 | 163 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 164 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 166 ms |
| Aug 1, 2026 | 170 ms |
| Aug 8, 2026 | 181 ms |
| Aug 15, 2026 | 189 ms |
| Aug 22, 2026 | 191 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 193 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 201 ms |
| Sep 26, 2026 | 203 ms |
| Oct 3, 2026 | 208 ms |
| Oct 10, 2026 | 208 ms |
| Oct 17, 2026 | 205 ms |
| Oct 24, 2026 | 199 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
Use efficient cache lifetimes
1.1 s · 661 KiB13 files are served with short cache lifetimes, so returning visitors download them again (661 KiB).
Mobile performance score: 67
67/100Your mobile performance score is 67 (desktop: 87). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 263 KiBAbout 263 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
600 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 600 ms.
Reduce unused CSS
300 ms · 55 KiBAbout 55 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.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
2,260 HTML elements
The page has 2,260 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Google Tag Manager and Cloudflare CDN and others), adding 511 KiB and 407 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.
Legacy JavaScript
35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need.
Improve image delivery
13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 204 ms
204 msYour server sent the HTML in 204 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 14.4 s
14.4 sVisually, the page fills in at 14.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
Largest Contentful Paint: 6.0 s
6.0 sYour largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ALERTE FRAUDE – Attention aux faux e-mails ifocop ! Des e-m…”.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 166 ms to 199 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 182 ms
182 msReal visitors wait 182 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: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 792 ms
792 msReal visitors wait 792 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 148 ms
148 msScripts block the page for only 148 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.54 g of CO₂e: 65.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.9 MB in 66 requests
1.9 MBYour homepage downloads 1.9 MB in 66 requests on a phone: scripts 1,011 KiB (22), fonts 750 KiB (9) and images 71 KiB (14). That is a lean page.
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
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Invalid ARIA attributes
7 elements use ARIA attributes their role does not allow, which confuses screen readers.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (7 elements).
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
323 internal links, 8 external
The homepage links to 323 pages on ifocop.fr and 8 external pages.
8 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Choisissez ifocop, N°1 de la reconversion & alternance, avec un taux de retour à l’emploi de +80% et 20 certifications …”.
One H1 headline
Your main headline reads: “Vivre une aventure formative, apprendre tout au long de sa vie”.
Title: 58 characters
Your title is a healthy 58 characters: “ifocop — Le choix de la Reconversion Pro & de l’Alternance”.
Canonical URL set
The canonical URL is https://www.ifocop.fr/.
Structured data in place
Structured data found: BreadcrumbList, EducationEvent, EducationalOrganization, EventSeries and Organization.
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.ifocop.fr/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.ifocop.fr/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,798 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.ifocop.fr/etre-contacte is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 134 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.
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 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “gtag is not defined”.
5 low-resolution images
5 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
26 of 27 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 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.
Local business without LocalBusiness data
Your homepage shows a street address 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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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,562 words of copy
The homepage carries about 1,562 words of visible text.
5 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Matomo.
Direct contact links
Visitors can reach you directly: 4 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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Microsoft Clarity (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
17 other companies contacted
Loading the homepage contacts 17 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 ifocop.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager | Matomo
- Hosting
- Alwaysdata
Company
- Founded
- 1969
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on ifocop.fr, including 13 speed 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.