cef.com website review

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

30 files are served with short cache lifetimes, so returning visitors download them again (671 KiB).

Your mobile performance score is 10. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, cookiebot.eu and Facebook and others), adding 1.5 MB and 2.2 s of main-thread time.

About 374 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.

Google Tag Manager costs a phone 661 ms of main-thread work and 533 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.

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

cookiebot.eu costs a phone 578 ms of main-thread work and 32 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.

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

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

Facebook costs a phone 337 ms of main-thread work and 230 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.

FontAwesome CDN costs a phone 134 ms of main-thread work and 490 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.

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

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

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.

Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Itinerarios profesionales”.

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

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

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

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

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

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

2 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-24, real Chrome visitors' tap response (inp) went from 136 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.1 MB in 107 requests on a phone: scripts 1.7 MB (34), fonts 216 KiB (4) and images 91 KiB (23). Under 2 MB keeps phones on slow connections fast.

Welcome 5.jpg.webp 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).

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

4 dropdowns have no label.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

19 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 136 pages on cef.com and 15 external pages.

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.

There is no /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.

/noticias and /areas-formacion use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /curso/curso-monografico-movilidad-extranjeria-nacionalidad, whose canonical is /curso/curso-movilidad-extranjeria-nacionalidad. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=17548766&tm=gtm002&Ver=2&mid=83718b13-ec30-4d5e-ba36-10616bf2e8ab&bo=1&sid=4fa53570d37211f1992e03c9b64aae80&vid=4fa55b70d37211f18db8f717dbb05fba&vids=1&msclkid=N&pid=e.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

2 links to other sites are dead, for example https://b2cef.b2clogin.com/b2cef.onmicrosoft.com/b2c_1a_ca_signup_signin/oauth2/v2.0/authorize?client_id=3d65fdd7-4c4c-490d-8c53-a4cc68a1fb34&redirect_uri=https%3A%2F%2Fopolab.cef.com%2Fauthentication%2Flogin-callback&response_type=id_token&scope=openid%20profile&response_mode=form_post&nonce=639053014445949600.NGY1ZWRkN2MtNDhlMC00Yzc5LTkxNjgtMWQ3NzE3YmM4MDZiNmY3ODQ4NTgtZDFhNC00ZDFlLWFiMzUtMDQ1MThhN2Q3MGM1&client_info=1&x-client-brkrver=IDWeb.3.3.1.0&state=CfDJ8B8h_sdh3JhAsozBWj87Iv5HvxBWrKei87nbQFbKfDI9K0Blb7nQg1Rw5uKNkvNadXwsz_kDo_5J6D2cS3H60PxFZrtow_cqUDu6lk4Rpfu5xU-c2msMyCIFfn5N0VY7O3IeFjf61Ndomh-YP78W17d6B1QVs0UznOFmxHfDCm6A4OkQMWeLDTQqlwlK6SCVxRiidbR3m4KEMLD_E2gkbxIhO57o7BQhIKegzkgiYSnMlJbXmvDLplGzNOAWlxwwWJzM-TkSVHEPR2VuOko_hIRSm3cxpPeAmUYRPpYps5ThTf68-VmjV_UaET5nRJd0vw&x-client-SKU=ID_NET8_0&x-client-ver=8.2.0.0 (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

cef.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

cef.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,923 words of visible text.

cef.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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