Programmable

Website review, no card needed

sfeir.com logo

sfeir.com website review

Visit site (opens in a new tab)Reviewed 3 November 202610 issues · 71 checks

This review found 10 issues worth fixing on sfeir.com, 1 of them high impact, across 71 checks. The most urgent: no call to action on the first screen. 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

Site score

94A

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.1 s476 msJun 6Oct 31837 ms
Show as table
DateReal-visitor load time (LCP)
Jun 6, 2026546 ms
Jun 13, 2026734 ms
Jun 20, 2026758 ms
Jun 27, 2026825 ms
Jul 4, 2026915 ms
Jul 11, 2026902 ms
Jul 18, 2026887 ms
Jul 25, 2026931 ms
Aug 1, 2026947 ms
Aug 8, 2026962 ms
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 2026962 ms
Sep 5, 2026867 ms
Sep 12, 2026889 ms
Sep 19, 2026884 ms
Sep 26, 2026826 ms
Oct 3, 2026797 ms
Oct 10, 2026749 ms
Oct 17, 2026769 ms
Oct 24, 2026782 ms
Oct 31, 2026837 ms
Real-visitor tap response (INP)75th percentile, phones
86 ms59 msJun 13Oct 3167 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 202674 ms
Jun 20, 202675 ms
Jun 27, 202679 ms
Jul 4, 202683 ms
Jul 11, 202679 ms
Jul 18, 202674 ms
Jul 25, 202663 ms
Aug 1, 202663 ms
Aug 8, 202662 ms
Aug 15, 202664 ms
Aug 22, 202672 ms
Aug 29, 202674 ms
Sep 5, 202670 ms
Sep 12, 202670 ms
Sep 19, 202670 ms
Sep 26, 202669 ms
Oct 3, 202670 ms
Oct 10, 202670 ms
Oct 17, 202669 ms
Oct 24, 202669 ms
Oct 31, 202667 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

www.sfeir.com (opens in a new tab)
Full-page screenshot of sfeir.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sfeir.com at 0.4 s0.4 s
  2. sfeir.com at 0.8 s0.8 s
  3. sfeir.com at 1.1 s1.1 s
  4. sfeir.com at 1.5 s1.5 s
  5. sfeir.com at 1.9 s1.9 s
  6. sfeir.com at 2.3 s2.3 s
  7. sfeir.com at 2.6 s2.6 s
  8. sfeir.com at 3.0 s3.0 s

Speed

2 to fix99

  • Improve image delivery

    500 ms · 81 KiB

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Matomo, Cloudflare and cloudflareinsights.com), adding 65 KiB and 33 ms of main-thread time.

  • Reduce unused JavaScript

    31 KiB

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

  • Use efficient cache lifetimes

    10 KiB

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

  • Legacy JavaScript

    10 KiB

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

  • 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.

3 checks passed

  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 38 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

1 to fix100

  • Largest content (LCP) got 26% slower for real visitors

    +26%

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

  • Tap response (INP) held steady for real visitors

    -9%

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

12 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: 0.9 s

    0.9 s

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

  • Real-user INP: 77 ms

    77 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 400 ms

    400 ms

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

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “SFEIR devient partenaire Preferred du Claude Partner Networ…”.

  • Time to Interactive: 2.1 s

    2.1 s

    The page is fully interactive after 2.1 s.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Speed Index: 1.0 s

    1.0 s

    Visually, the page fills in at 1.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90

  • 1 image far larger than shown

    67 KiB

    1 image is downloaded at several times the size a phone draws it, for example preferred-claude-partner-network.jpg at 990 px wide, shown at 128 px. Resized copies would save about 67 KiB.

  • 1 image in older formats

    1 image (79 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 0.07 g of CO₂ per visit

    0.07 g

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

2 checks passed

  • Page weight: 257 KiB in 13 requests

    257 KiB

    Your homepage downloads 257 KiB in 13 requests on a phone: images 90 KiB (2), scripts 71 KiB (4) and fonts 61 KiB (2). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

Google 100100
2 checks passed

  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093

  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “SFEIR | AI Engineering Company, Software Factory 10x & IA en production | SFEIR”.

  • 195 internal links, 0 external

    The homepage links to 195 pages on sfeir.com and 0 external pages.

7 checks passed

  • Meta description: 154 characters

    Your meta description is 154 characters: “SFEIR est une AI Engineering Company : nous concevons, déployons et opérons vos systèmes d'IA en production, de la Soft…”.

  • One H1 headline

    Your main headline reads: “Visez le 10x. Nous concevons, déployons et opérons vos systèmes d'IA en production.”.

  • Canonical URL set

    The canonical URL is https://www.sfeir.com/.

  • Structured data in place

    Structured data found: Organization, WebPage 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.sfeir.com/sitemap-index.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (195 KiB, 620 links), a plain-text guide to the site for AI tools.

Other pages

100

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 79 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 9293

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Executing inline script violates the following Content Security Policy directive 'script-src 'self' 'sha256-H59iWqWcASu…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64

  • 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.

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

    The homepage carries about 626 words of visible text.

3 checks passed

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 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.

  • 4 other companies contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 sfeir.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Astro
Hosting
Cloudflare Pages

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 10 issues on sfeir.com, including 3 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