Website review, no card needed
digital-campus.fr website review
Visit site (opens in a new tab)Reviewed 3 November 202643 issues · 89 checks
This review found 43 issues worth fixing on digital-campus.fr, 13 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 202 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 215 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 204 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 195 ms |
| Jul 4, 2026 | 199 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 203 ms |
| Jul 25, 2026 | 203 ms |
| Aug 1, 2026 | 208 ms |
| Aug 8, 2026 | 211 ms |
| Aug 15, 2026 | 217 ms |
| Aug 22, 2026 | 228 ms |
| Aug 29, 2026 | 232 ms |
| Sep 5, 2026 | 233 ms |
| Sep 12, 2026 | 228 ms |
| Sep 19, 2026 | 222 ms |
| Sep 26, 2026 | 209 ms |
| Oct 3, 2026 | 206 ms |
| Oct 10, 2026 | 206 ms |
| Oct 17, 2026 | 204 ms |
| Oct 24, 2026 | 222 ms |
| Oct 31, 2026 | 232 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.8 s
1.5 s
2.3 s
3.1 s
3.9 s
4.6 s
5.4 s
6.2 s
Speed
Render-blocking requests
2.3 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Didomi and jQuery CDN and others), adding 1.3 MB and 1.1 s of main-thread time.
Use efficient cache lifetimes
500 ms · 707 KiB78 files are served with short cache lifetimes, so returning visitors download them again (707 KiB).
Improve image delivery
550 ms · 604 KiB18 images could be 604 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Google Tag Manager adds 868 ms
868 msGoogle Tag Manager costs a phone 868 ms of main-thread work and 680 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 CSS
600 ms · 146 KiBAbout 146 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused JavaScript
567 KiBAbout 567 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 346 ms. During a long task the page ignores taps.
2,464 HTML elements
The page has 2,464 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Didomi adds 137 ms
137 msDidomi costs a phone 137 ms of main-thread work and 334 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify JavaScript
54 KiB54 KiB could be saved by minifying JavaScript.
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: 243 ms
243 msYour server sent the HTML in 243 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.
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Digital campus”.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 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.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 202 ms to 232 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 199 ms
199 msReal visitors wait 199 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.
Cumulative Layout Shift: 0.043
0.043The layout barely moves while loading (CLS 0.043, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 119 requests
3.7 MBYour homepage downloads 3.7 MB in 119 requests on a phone: scripts 1.8 MB (46), images 1.5 MB (34) and stylesheets 174 KiB (10). Under 2 MB keeps phones on slow connections fast.
20 images in older formats
20 images (1.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.
An image on the first screen is lazy-loaded
bg-hp-mobile.jpg 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).
3 images far larger than shown
42 KiB3 images are downloaded at several times the size a phone draws them, for example img_3956.jpg at 971 px wide, shown at 280 px. Resized copies would save about 42 KiB.
3 images below the first screen load straight away
3 images further down the page (128 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 124.6 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”.
Invalid ARIA attributes
5 elements use ARIA attributes their role does not allow, which confuses screen readers.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (44 elements)
All page content should be contained by landmarks: 44 elements on the page fail this check, rated moderate by axe-core.
24 links without text
24 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (168 characters)
Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found ((untyped), Organization and WebSite) but with 1 problem, for example “block has no @type”.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
314 internal links, 0 external
The homepage links to 314 pages on digital-campus.fr and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Digital Campus, l'école du digital pour révéler votre potentiel”.
Title: 42 characters
Your title is a healthy 42 characters: “Digital Campus - N°1 des écoles du digital”.
Canonical URL set
The canonical URL is https://www.digital-campus.fr/.
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.digital-campus.fr/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, logo, 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.digital-campus.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.
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 (2,408 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages slow to respond
https://www.digital-campus.fr/ecole/aix, https://www.digital-campus.fr/ecole/biarritz, https://www.digital-campus.fr/ecole/bordeaux, https://www.digital-campus.fr/ecole/dakar, https://www.digital-campus.fr/ecole/lyon and https://www.digital-campus.fr/ecole/montpellier and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 85 found) and read each the way a search engine does.
7 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.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
11 of 13 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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 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 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,267 words of copy
The homepage carries about 1,267 words of visible text.
2 checks passed
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks, 8 customer or partner logos and a star rating.
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 Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
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.
1 checks passed
Consent tool: Didomi
A consent management tool (Didomi) 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 digital-campus.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- OVHcloud
Hiring
- Hiring
- 3 open roles
- Job board
- smartrecruiters
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on digital-campus.fr, including 22 speed issues, 3 SEO issues and 5 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.