Website review, no card needed

waisso.com logo

waisso.com website review

Visit site (opens in a new tab)Reviewed 18 October 202626 issues · 66 checks

This review found 26 issues worth fixing on waisso.com, 13 of them high impact, across 66 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 waisso.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. waisso.com at 1.4 s1.4 s
  2. waisso.com at 2.8 s2.8 s
  3. waisso.com at 4.1 s4.1 s
  4. waisso.com at 5.5 s5.5 s
  5. waisso.com at 6.9 s6.9 s
  6. waisso.com at 8.3 s8.3 s
  7. waisso.com at 9.7 s9.7 s
  8. waisso.com at 11.0 s11.0 s

Speed

8 to fix34
  • Use efficient cache lifetimes

    1.3 s · 2.2 MB

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

  • Render-blocking requests

    2.4 s

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

  • Reduce unused JavaScript

    1.1 s · 248 KiB

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

  • Font display

    1.0 s

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

  • Mobile performance score: 34

    34/100

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

  • Improve image delivery

    450 ms · 939 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and openai.com and others), adding 688 KiB and 515 ms of main-thread time.

  • Google Tag Manager adds 401 ms

    401 ms

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

  • 6 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 9 KiB

    9 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    10 KiB

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 148 ms

    148 ms

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

Core Web Vitals

6 to fix32
  • Largest Contentful Paint: 12.0 s

    12.0 s

    Your largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NOTRE EXPERTISE AU SERVICE DE VOTRE PERFORMANCE DIGITALE”. Most of its time is resource load delay (6.9 s).

  • Speed Index: 16.8 s

    16.8 s

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

  • Cumulative Layout Shift: 1.077

    1.077

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

  • Time to Interactive: 14.5 s

    14.5 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • 31 images without width and height

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

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

1 checks passed
  • Total Blocking Time: 146 ms

    146 ms

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

Images and page weight

3 to fix68
  • Page weight: 3.0 MB in 127 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 127 requests on a phone: images 2.0 MB (47), scripts 786 KiB (41) and fonts 97 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 15 images below the first screen load straight away

    15 images further down the page (867 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 4 images far larger than shown

    460 KiB

    4 images are downloaded at several times the size a phone draws them, for example agence-marketing-digital-bpce.webp at 2,448 px wide, shown at 310 px. Resized copies would save about 460 KiB.

  • 1 image in older formats

    1 image (48 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.9 g of CO₂ per visit

    0.85 g

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

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 43 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 0 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 10096
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 120 internal links, 2 external

    The homepage links to 120 pages on waisso.com and 2 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Waisso réunit 5 agences de marketing digital : +20 ans d’expérience au service de la performance marketing et de la tra…”.

  • One H1 headline

    Your main headline reads: “NOTRE EXPERTISE AU SERVICE DEVOTRE PERFORMANCE DIGITALE”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Waisso | 5 Agences Expertes en Marketing Digital | Paris”.

  • Canonical URL set

    The canonical URL is https://waisso.com/.

  • 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://waisso.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://waisso.com/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.

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://waisso.com/wp-content/uploads/2025/12/waisso-scaled.png.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “tarteaucitron is not defined”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 180 words

    The homepage has only about 180 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Business – Contact”, “Consulting – Contact” and “Digital – Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 8 cookies set on arrival

    8

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

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 waisso.com, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on waisso.com, including 14 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