Website review, no card needed

matters.tech logo

matters.tech website review

Visit site (opens in a new tab)Reviewed 20 October 202638 issues · 81 checks

This review found 38 issues worth fixing on matters.tech, 16 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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 matters.tech (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. matters.tech at 0.4 s0.4 s
  2. matters.tech at 0.8 s0.8 s
  3. matters.tech at 1.2 s1.2 s
  4. matters.tech at 1.6 s1.6 s
  5. matters.tech at 2.0 s2.0 s
  6. matters.tech at 2.4 s2.4 s
  7. matters.tech at 2.8 s2.8 s
  8. matters.tech at 3.2 s3.2 s

Speed

13 to fix35
  • Reduce unused JavaScript

    4.0 s · 4.9 MB

    About 4.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

  • YouTube adds 2.8 s

    2.8 s

    YouTube costs a phone 2.8 s of main-thread work and 7.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.8 s

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

  • Main-thread work: 10.0 s

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

  • Mobile performance score: 35

    35/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Embedly and cloudfront.net and others), adding 13.1 MB and 4.7 s of main-thread time.

  • Improve image delivery

    750 ms · 2.2 MB

    30 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • Embedly adds 766 ms

    766 ms

    Embedly costs a phone 766 ms of main-thread work and 1.4 MB 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.

  • cloudfront.net adds 519 ms

    519 ms

    cloudfront.net costs a phone 519 ms of main-thread work and 31 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.

  • website-files.com adds 163 ms

    163 ms

    website-files.com costs a phone 163 ms of main-thread work and 3.2 MB 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 · 171 KiB

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

  • Google Tag Manager adds 326 ms

    326 ms

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

  • 20 long tasks on the main thread

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

  • Minify CSS

    150 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    6 KiB

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

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

    2 ms

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

Core Web Vitals

6 to fix43
  • First Contentful Paint: 8.2 s

    8.2 s

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

  • Largest Contentful Paint: 10.2 s

    10.2 s

    Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Studio Produit, Tech & IA”.

  • Time to Interactive: 60.0 s

    60.0 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Total Blocking Time: 967 ms

    967 ms

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

  • 35 images without width and height

    35 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
  • Cumulative Layout Shift: 0.019

    0.019

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

Images and page weight

3 to fix53
  • Page weight: 13.8 MB in 263 requests

    13.8 MB

    Your homepage downloads 13.8 MB in 263 requests on a phone: scripts 7.5 MB (80), images 3.1 MB (45) and HTML 2.1 MB (62). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6851637964c32d7e35340fcc_planet_1-p-500.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    110 KiB

    1 image is downloaded at several times the size a phone draws it, for example 638df9fe97a47d39203e1f46_Logo_Matters.svg at 1,354 px wide, shown at 100 px. Resized copies would save about 110 KiB.

  • 2 images in older formats

    2 images (73 KiB) 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.

  • About 3.9 g of CO₂ per visit

    3.90 g

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

Accessibility

5 to fixGoogle 9094
  • 11 text elements with low contrast

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (15 elements)

    All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 79 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 10091
  • No structured data

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

  • 11 H1 headlines

    There are 11 <h1> headlines (“Studio Produit, Tech & IA”, “Ce que nous faisons” and “Nos success stories”). One clear main headline is easier for people and search engines.

  • 35 internal links, 4 external

    The homepage links to 35 pages on matters.tech and 4 external pages.

6 checks passed
  • Meta description: 81 characters

    Your meta description is 81 characters: “Matters accompagne des startups/scale-ups à fort impact environnemental et social”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Matters Product & Startup Studio, développez vos produits”.

  • Canonical URL set

    The canonical URL is https://matters.tech/.

  • 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://matters.tech/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://matters.tech/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 (661 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 7 pages share a title

    https://matters.tech/services/du-prototype-au-minimum-viable-product-mvp, https://matters.tech/services/faire-evoluer-votre-produit-pour-quil-apporte-plus-de-valeur, https://matters.tech/services/accelerer-vos-intitiatives-dinnovation-, https://matters.tech/services/un-coup-de-boost-cible-pour-vos-equipes-produit-tech, https://matters.tech/services/service-finops-pilotage-et-optimisation-cloud and https://matters.tech/services/audit-tech-ux-et-due-diligence and 1 other all use the title “Matters Startup & Product studio”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://matters.tech/services/du-prototype-au-minimum-viable-product-mvp, https://matters.tech/services/faire-evoluer-votre-produit-pour-quil-apporte-plus-de-valeur, https://matters.tech/services/accelerer-vos-intitiatives-dinnovation-, https://matters.tech/services/un-coup-de-boost-cible-pour-vos-equipes-produit-tech, https://matters.tech/services/service-finops-pilotage-et-optimisation-cloud and https://matters.tech/services/audit-tech-ux-et-due-diligence and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://matters.tech/nous-contacter has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 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 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 7397
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 low-resolution image

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

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

    The homepage carries about 722 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 22 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Webflow
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 38 issues on matters.tech, including 19 speed issues, 2 SEO issues 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