Website review, no card needed

insidegroup.fr logo

insidegroup.fr website review

Visit site (opens in a new tab)Reviewed 4 November 202625 issues · 89 checks

This review found 25 issues worth fixing on insidegroup.fr, 6 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.

  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
2.6 s1.5 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.5 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.2 s
Jul 11, 20262.1 s
Jul 18, 20261.9 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.9 s
Aug 15, 20262.3 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.4 s
Oct 10, 20262.3 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
146 ms91 msMay 16Oct 31102 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026119 ms
May 23, 2026119 ms
May 30, 2026127 ms
Jun 6, 2026119 ms
Jun 13, 2026112 ms
Jun 20, 2026113 ms
Jun 27, 2026105 ms
Jul 4, 2026100 ms
Jul 11, 202697 ms
Jul 18, 2026101 ms
Jul 25, 2026109 ms
Aug 1, 2026119 ms
Aug 8, 2026128 ms
Aug 22, 2026131 ms
Aug 29, 2026121 ms
Sep 5, 2026140 ms
Sep 12, 2026135 ms
Sep 19, 2026135 ms
Sep 26, 2026124 ms
Oct 3, 2026121 ms
Oct 10, 202699 ms
Oct 17, 2026102 ms
Oct 24, 2026103 ms
Oct 31, 2026102 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 insidegroup.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

insidegroup.fr does not allow embedding, so this is Google's rendering of the page.

Speed

9 to fix78
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 78

    78/100

    Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, LinkedIn Ads and Google/Doubleclick Ads and others), adding 555 KiB and 536 ms of main-thread time.

  • Google Tag Manager adds 512 ms

    512 ms

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

    350 ms

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

  • Reduce unused JavaScript

    338 KiB

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

  • 5 long tasks on the main thread

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

  • Main-thread work: 2.4 s

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

  • 2,278 HTML elements

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

  • Reduce unused CSS

    150 ms · 27 KiB

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

  • Use efficient cache lifetimes

    25 KiB

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

  • Legacy JavaScript

    17 KiB

    Polyfills for old browsers add 17 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.

  • 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: 98 ms

    98 ms

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

Core Web Vitals

6 to fix100
  • 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: 9.5 s

    9.5 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Total Blocking Time: 495 ms

    495 ms

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

  • Cumulative Layout Shift: 0.176

    0.176

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

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

  • Real-user INP: 102 ms

    102 ms

    Real visitors wait 102 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.

  • Tap response (INP) got 14% faster for real visitors

    -14%

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

  • Speed Index: 3.3 s

    3.3 s

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Largest Contentful Paint: 1.5 s

    1.5 s

    Your largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Inside Partenaire de conseil et de services numériques faci…”.

Images and page weight

1 to fix70
  • Page weight: 7.1 MB in 85 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 85 requests on a phone: media 5.9 MB (1), scripts 887 KiB (34) and fonts 226 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    2.02 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

1 to fixGoogle 9799
  • 1 link without text

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 1 failed. 4 mores 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 (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Inside : votre partenaire IT infrastructure, digital, IA, cybersec –ESN”.

  • 116 internal links, 3 external

    The homepage links to 116 pages on insidegroup.fr and 3 external pages.

7 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Chez Inside, nous accompagnons et facilitons vos initiatives IT et l'évolution de votre système d'information : infra, …”.

  • One H1 headline

    Your main headline reads: “Inside Partenaire de conseil et de services numériques facilitant la transformation des entreprises”.

  • Canonical URL set

    The canonical URL is https://insidegroup.fr/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://insidegroup.fr/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 (943 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (8 KiB, 36 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 86 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 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • No security.txt

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

8 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (insidegroup.fr).

  • Valid certificate (83 days left)

    The certificate from Let's Encrypt · YE1 verifies for insidegroup.fr and is valid for another 83 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://insidegroup.fr redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 43 links work

    All 43 links checked from your homepage (40 internal, 3 external) answered without errors.

Domain and trust

4 checks passed
  • Domain is 12 years old

    12 years

    insidegroup.fr was registered in Jan 2014 through OVH. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only pki.goog, digicert.com, amazonaws.com and sectigo.com to issue certificates for insidegroup.fr, so a mis-issued certificate from anyone else is refused.

  • DNSSEC is on

    insidegroup.fr's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

  • Registered until Jan 2029

    insidegroup.fr is registered until Jan 2029.

Content and conversion

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

  • Thin social proof

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

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

    The homepage carries about 607 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Email authentication

1 to fix70
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be insidegroup.fr is still delivered. Add a report address, check the reports, then move to quarantine.

  • Email authentication score: 70/100

    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.

2 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com include:spf.protection.outlook.com include:amazonses.com include:spf.mailjet.com include…”.

  • DKIM signing found

    A DKIM key is published (selector “google” and “mail”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

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

  • 13 other companies contacted

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

Upkeep, stack and company

  • 1 plugin is behind its latest release.elementor 4.3.5 → 4.3.6

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on insidegroup.fr, including 15 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