Website review, no card needed

networks-technology.fr logo

networks-technology.fr website review

Visit site (opens in a new tab)Reviewed 9 November 202636 issues · 77 checks

This review found 36 issues worth fixing on networks-technology.fr, 13 of them high impact, across 77 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

Full-page screenshot of networks-technology.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. networks-technology.fr at 0.5 s0.5 s
  2. networks-technology.fr at 1.1 s1.1 s
  3. networks-technology.fr at 1.6 s1.6 s
  4. networks-technology.fr at 2.1 s2.1 s
  5. networks-technology.fr at 2.6 s2.6 s
  6. networks-technology.fr at 3.2 s3.2 s
  7. networks-technology.fr at 3.7 s3.7 s
  8. networks-technology.fr at 4.2 s4.2 s

Speed

8 to fix66
  • Use efficient cache lifetimes

    1.6 s · 18.2 MB

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

  • Reduce unused JavaScript

    2.7 s · 479 KiB

    About 479 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Font display

    2.1 s

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

  • Render-blocking requests

    1.6 s

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

  • Improve image delivery

    2.9 MB

    18 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 66

    66/100

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

  • Google CDN adds 347 ms

    347 ms

    Google CDN costs a phone 347 ms of main-thread work and 742 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.

  • Reduce unused CSS

    300 ms · 87 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 812 KiB and 389 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    15 KiB

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

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 103 ms

    103 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 20.5 s

    20.5 s

    Your largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Demandez une démo Créer de l’intelligence marketing local a…”.

  • Time to Interactive: 27.5 s

    27.5 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • 42 images without width and height

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 81 ms

    81 ms

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

  • Cumulative Layout Shift: 0.023

    0.023

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

Images and page weight

5 to fix28
  • Page weight: 19.6 MB in 82 requests

    19.6 MB

    Your homepage downloads 19.6 MB in 82 requests on a phone: fonts 13.5 MB (4), images 4.6 MB (41) and scripts 1,001 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    VISU_visiblocal.png weighs 492 KiB. On a phone connection a single image that size takes seconds.

  • 13 images in older formats

    13 images (4.1 MB) 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.

  • 13 images below the first screen load straight away

    13 images further down the page (4.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    142 KiB

    2 images are downloaded at several times the size a phone draws them, for example In.jpg at 927 px wide, shown at 30 px. Resized copies would save about 142 KiB.

  • About 5.6 g of CO₂ per visit

    5.56 g

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

Accessibility

4 to fixGoogle 8494
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 9 form fields without a label

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

  • 1 link without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 52 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • 7 H1 headlines

    There are 7 <h1> headlines (“Local Intelligence for”, “Les solutions” and “Les +”). One clear main headline is easier for people and search engines.

  • Meta description is long (183 characters)

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

  • 41 internal links, 4 external

    The homepage links to 41 pages on networks-technology.fr and 4 external pages.

6 checks passed
  • Title: 55 characters

    Your title is a healthy 55 characters: “Plateforme de performance marketing locale - Peppersoft”.

  • Canonical URL set

    The canonical URL is https://www.peppersoft.fr/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.peppersoft.fr/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.peppersoft.fr/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 sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

4 to fix81
  • 10 pages share 5 titles

    https://www.peppersoft.fr/prospection-locale and https://www.peppersoft.fr/prospection-locale-magasin all use the title “Prospection locale de vos points de vente - Peppersoft”, and 4 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages share a meta description

    https://www.peppersoft.fr/prospection-locale and https://www.peppersoft.fr/prospection-locale-magasin use the same meta description. A description written for each page earns more clicks.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.peppersoft.fr/prospection-locale, whose canonical is https://www.peppersoft.fr/prospection-locale-magasin. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.peppersoft.fr/actualites has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.peppersoft.fr/visibilite-locale, https://www.peppersoft.fr/activation-sociale, https://www.peppersoft.fr/pilotage-reseau and https://www.peppersoft.fr/notre-approche took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a map 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.

  • Thin social proof

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

  • A 8-field form

    Your longest form asks for 8 fields (5 required). Every extra field lowers completion.

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

    The homepage carries about 858 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.

Privacy and tracking

  • 1 cookie set on arrival

    1

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 networks-technology.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Foliateam Operateur SAS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on networks-technology.fr, including 13 speed issues, 2 SEO issues and 7 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