supdeco.sn website review

78 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

31 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.

Your mobile performance score is 53 (desktop: 64). Pages that score under 90 lose visitors before the first paint.

About 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 720 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Maps and others), adding 721 KiB and 581 ms of main-thread time.

6 images could be 438 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 431 KiB of JavaScript is downloaded but never used on this page.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).

A phone's processor spends 3.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,847 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 long tasks block the main thread while loading, the longest for 159 ms. During a long task the page ignores taps.

6 KiB could be saved by minifying CSS.

23 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Real visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.

Real visitors see the first content after 4.6 s (75th percentile). Good is under 1.8 s.

Real visitors wait 3.4 s for your server to start answering (75th percentile). Good is under 800 ms.

Visually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 10.8 s. Good is under 3.8 s.

The layout shifts by 0.371 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 131 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SCIENCES, INGÉNIERIE ET INFORMATIQUE”. Most of its time is element render delay (3.0 s).

Scripts block taps and scrolling for 371 ms in total while the page loads. Good is under 200 ms.

12 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.8 MB in 103 requests on a phone: images 1.2 MB (18), scripts 1.1 MB (39) and fonts 318 KiB (6). Under 2 MB keeps phones on slow connections fast.

4 images (533 KiB) 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.

4 images further down the page (533 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example Supdeco-Campus-Banjul-celebre-sa-cinquieme-promotion.jpeg at 1,200 px wide, shown at 350 px. Resized copies would save about 76 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 dropdown has no label.

8 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

10 visible links have no text or label, so screen readers cannot say where they go.

9 form fields have no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 86 characters, so Google will cut it off around 60: “Groupe Supdeco Dakar | École de Management, Informatique & Transport Logistique, droit”.

Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

3 links have no real href, so search engines can't follow them.

The homepage links to 363 pages on supdeco.sn and 46 external pages.

There is no https://supdeco.sn/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.

https://supdeco.sn/nos-missions-visions-et-valeurs, https://supdeco.sn/pres-de-30-ans-au-service-de-lafrique, https://supdeco.sn/les-atouts-du-groupe-sup-de-co, https://supdeco.sn/reconnaissances-et-accreditations, https://supdeco.sn/nos-campus and https://supdeco.sn/experience-etudiante-a-sup-de-co have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 168 found) and read each the way a search engine does.

51 of 72 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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 503 ()”.

2 images are served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 348 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

Opening the homepage sets 14 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.