Website review, no card needed

greenkub.fr logo

greenkub.fr website review

Visit site (opens in a new tab)Reviewed 22 October 202622 issues · 81 checks

This review found 22 issues worth fixing on greenkub.fr, 14 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

Real-visitor load time (LCP)75th percentile, phones
5.4 s346 msMay 2Oct 171.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.3 s
May 9, 20264.4 s
May 16, 20264.7 s
May 23, 20264.8 s
May 30, 20264.7 s
Jun 6, 20264.7 s
Jun 13, 20264.5 s
Jun 20, 20264.4 s
Jun 27, 20264.4 s
Jul 4, 20264.5 s
Jul 11, 20264.8 s
Jul 18, 20264.8 s
Jul 25, 20264.5 s
Aug 1, 20263.8 s
Aug 8, 20261.6 s
Aug 15, 20261.0 s
Aug 22, 2026977 ms
Aug 29, 2026957 ms
Sep 5, 2026928 ms
Sep 12, 2026978 ms
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
188 ms102 msMay 2Oct 17178 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026156 ms
May 9, 2026146 ms
May 16, 2026140 ms
May 23, 2026138 ms
May 30, 2026135 ms
Jun 6, 2026136 ms
Jun 13, 2026140 ms
Jun 20, 2026145 ms
Jun 27, 2026148 ms
Jul 4, 2026151 ms
Jul 11, 2026156 ms
Jul 18, 2026151 ms
Jul 25, 2026144 ms
Aug 1, 2026138 ms
Aug 8, 2026128 ms
Aug 15, 2026118 ms
Aug 22, 2026113 ms
Aug 29, 2026112 ms
Sep 5, 2026117 ms
Sep 12, 2026130 ms
Sep 19, 2026144 ms
Sep 26, 2026152 ms
Oct 3, 2026161 ms
Oct 10, 2026170 ms
Oct 17, 2026178 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 greenkub.fr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix49
  • Reduce unused JavaScript

    2.9 s · 586 KiB

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

  • Use efficient cache lifetimes

    2.0 s · 380 KiB

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

  • Mobile performance score: 49

    49/100

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

  • Improve image delivery

    500 ms · 154 KiB

    5 images could be 154 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Hubspot and Google Tag Manager and others), adding 635 KiB and 551 ms of main-thread time.

  • Legacy JavaScript

    300 ms · 63 KiB

    Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 2.6 s

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

  • 15 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 49. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Duplicated JavaScript

    5 KiB

    5 KiB JavaScript is shipped twice across bundles.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 17.2 s

    17.2 s

    Your largest element takes 17.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 17.6 s

    17.6 s

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

  • Speed Index: 8.3 s

    8.3 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Total Blocking Time: 475 ms

    475 ms

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

8 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: 1.1 s

    1.1 s

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

  • Real-user INP: 152 ms

    152 ms

    Real visitors wait 152 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: 1.1 s

    1.1 s

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

  • Real-user TTFB: 573 ms

    573 ms

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

  • Largest content (LCP) got 76% faster for real visitors

    -76%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix45
  • Page weight: 4.6 MB in 81 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 81 requests on a phone: images 3.0 MB (28), scripts 1.4 MB (31) and fonts 64 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    real-4.jpg weighs 1.6 MB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (1.6 MB) 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 1.3 g of CO₂ per visit

    1.29 g

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

2 checks passed
  • 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

2 to fixGoogle 9797
  • 34 text elements with low contrast

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 64 images in the HTML carry an alt attribute.

  • 55 automated accessibility rules passed

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

SEO

Google 100100
  • 102 internal links, 11 external

    The homepage links to 102 pages on greenkub.fr and 11 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Greenkub, constructeur d'habitats bois : studios de jardin, maisons ossature bois RE2020 sous CCMI, extensions. Clé en …”.

  • One H1 headline

    Your main headline reads: “Emménagez dans votre maison en bois neuve 60 jours après le début du chantier.”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Greenkub · Constructeur de maisons et studios de jardin en bois”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, GeneralContractor, ItemList and LocalBusiness.

  • 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.greenkub.fr/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • Opted out of AI training for 2 crawlers

    robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

3 checks passed
  • 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,765 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.greenkub.fr/llms.txt (22 KiB, 145 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 56 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 10074
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56376800&tm=gtm002&Ver=2&mid=cdefd992-c276-4686-b826-e668c3fd81fd&bo=1&sid=f2938280ce4c11f1acd1f145914df741&vid=f293b4a0ce4c11f1b20fd319f48cafe4&vids=1&msclkid=N&pi=91.

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix78
  • 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 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 991 words of copy

    The homepage carries about 991 words of visible text.

7 checks passed
  • 2 short forms

    2 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks, 1 customer or partner logo and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies (measured from a US location before any click).

  • 31 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 greenkub.fr, 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
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 22 issues on greenkub.fr, including 12 speed issues and 2 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