Website review, no card needed

2600.eu logo

2600.eu website review

Visit site (opens in a new tab)Reviewed 4 November 202635 issues · 87 checks

This review found 35 issues worth fixing on 2600.eu, 15 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.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.8 s1.7 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20264.4 s
May 30, 20264.4 s
Jun 6, 20264.4 s
Jun 13, 20263.8 s
Jun 20, 20263.2 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.6 s
Jul 18, 20263.0 s
Jul 25, 20262.5 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.1 s
Sep 5, 20262.4 s
Sep 12, 20262.7 s
Sep 19, 20263.1 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20262.7 s
Oct 24, 20262.6 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
329 ms201 msMay 16Oct 31274 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026244 ms
May 23, 2026259 ms
May 30, 2026260 ms
Jun 6, 2026255 ms
Jun 13, 2026236 ms
Jun 20, 2026236 ms
Jun 27, 2026235 ms
Jul 4, 2026229 ms
Jul 11, 2026226 ms
Jul 18, 2026217 ms
Jul 25, 2026216 ms
Aug 1, 2026218 ms
Aug 8, 2026219 ms
Aug 15, 2026255 ms
Aug 22, 2026262 ms
Aug 29, 2026265 ms
Sep 5, 2026259 ms
Sep 12, 2026242 ms
Sep 19, 2026230 ms
Sep 26, 2026250 ms
Oct 3, 2026282 ms
Oct 10, 2026295 ms
Oct 17, 2026314 ms
Oct 24, 2026284 ms
Oct 31, 2026274 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

Full-page screenshot of 2600.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 2600.eu at 1.0 s1.0 s
  2. 2600.eu at 2.0 s2.0 s
  3. 2600.eu at 3.0 s3.0 s
  4. 2600.eu at 4.0 s4.0 s
  5. 2600.eu at 5.0 s5.0 s
  6. 2600.eu at 6.0 s6.0 s
  7. 2600.eu at 7.1 s7.1 s
  8. 2600.eu at 8.1 s8.1 s

Speed

10 to fix36
  • Use efficient cache lifetimes

    1.3 s · 792 KiB

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

  • Render-blocking requests

    1.7 s

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 4.9 s

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

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    750 ms · 837 KiB

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

  • Google Tag Manager adds 643 ms

    643 ms

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

  • Improve image delivery

    300 ms · 83 KiB

    6 images could be 83 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Hubspot adds 330 ms

    330 ms

    Hubspot costs a phone 330 ms of main-thread work and 512 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.

  • Facebook adds 309 ms

    309 ms

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

  • 17 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    37 KiB

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

  • Reduce unused CSS

    27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page.

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 197 ms

    197 ms

    Your server sent the HTML in 197 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • 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.

  • Real-user CLS: 0.46

    0.46

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

  • Time to Interactive: 21.0 s

    21.0 s

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

  • Cumulative Layout Shift: 1

    1

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

  • Total Blocking Time: 799 ms

    799 ms

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Prochaine Journée Portes Ouvertes : 28 nov. 2026 >”.

  • Real-user INP: 274 ms

    274 ms

    Real visitors wait 274 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • 32 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) got 11% slower for real visitors

    +11%

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

2 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Largest content (LCP) got 38% faster for real visitors

    -38%

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 157 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 157 requests on a phone: scripts 2.1 MB (55), images 869 KiB (44) and fonts 267 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (42 KiB) is 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.

  • About 1.0 g of CO₂ per visit

    0.96 g

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

2 checks passed
  • 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

5 to fixGoogle 9392
  • 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.

  • [role="img"] and [role="image"] elements must have alternative text (1 element)

    [role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 2 links crawlers can't follow

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

  • 120 internal links, 9 external

    The homepage links to 120 pages on 2600.eu and 9 external pages.

8 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Reconnue et labellisée SecNumedu par l'ANSSI, l’École 2600 forme les experts cyber grâce à son cursus post-bac, du Bach…”.

  • One H1 headline

    Your main headline reads: “École 2600, l'école de cybersécurité”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Ecole 2600 | Ecole de Cybersécurité”.

  • Canonical URL set

    The canonical URL is https://www.2600.eu/.

  • Structured data in place

    Structured data found: BreadcrumbList, LocalBusiness 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.2600.eu/wp-content/uploads/seokey/sitemaps/sitemap-index-FRA.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.2600.eu/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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (845 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 3 pages slow to respond

    https://www.2600.eu/evenements/journee-portes-ouvertes-nov-2026, https://www.2600.eu/formations-cybersecurite and https://www.2600.eu/formations-cybersecurite/formation-bac-plus-5 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 26 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 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    18 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

  • 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 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 575 words of copy

    The homepage carries about 575 words of visible text.

4 checks passed
  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar, Matomo and Cloudflare Web Analytics.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 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.

  • 42 other companies contacted

    Loading the homepage contacts 42 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 2600.eu, 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
Analytics
Google Tag Manager | Hotjar | Matomo
Hosting
CELESTE - Internet services provider

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on 2600.eu, including 22 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25