Website review, no card needed
grw-immobilier.com website review
Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 74 checks
This review found 37 issues worth fixing on grw-immobilier.com, 15 of them high impact, across 74 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
70CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Improve image delivery
7.5 s · 2.3 MB7 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.5 s faster on a phone.
Use efficient cache lifetimes
3.5 s · 1.6 MB10 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Reduce unused JavaScript
4.0 s · 879 KiBAbout 879 KiB 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.
Render-blocking requests
2.2 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Google Analytics and awswaf.com and others), adding 1.0 MB and 747 ms of main-thread time.
Avoid multiple page redirects
762 msThe page goes through 1 redirect before it starts loading, costing about 762 ms. Link and advertise the final URL directly.
Google Tag Manager adds 667 ms
667 msGoogle Tag Manager costs a phone 667 ms of main-thread work and 877 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
310 ms · 66 KiBAbout 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 178 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.4 s
21.4 sYour largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nous respectons votre vie privée. En cliquant sur «Accepter…”.
Time to Interactive: 21.8 s
21.8 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 427 ms
427 msScripts block taps and scrolling for 427 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.124
0.124The layout shifts by 0.124 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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.
Images and page weight
Page weight: 4.8 MB in 100 requests
4.8 MBYour homepage downloads 4.8 MB in 100 requests on a phone: images 3.1 MB (10), scripts 1.5 MB (48) and stylesheets 138 KiB (30). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
824 KiB4 images are downloaded at several times the size a phone draws them, for example 305741-grw-immobilier-1-1785820058.jpg at 1,920 px wide, shown at 280 px. Resized copies would save about 824 KiB.
6 images in older formats
6 images (3.0 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.
4 images below the first screen load straight away
4 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 162.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
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 11 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (27 characters)
Your title is only 27 characters: “immobilier | GRW Immobilier”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (14 characters)
Your meta description is only 14 characters: “GRW Immobilier”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
40 internal links, 8 external
The homepage links to 40 pages on grw-immobilier.com and 8 external pages.
5 checks passed
One H1 headline
Your main headline reads: “GRW IMMOBILIER”.
Canonical URL set
The canonical URL is https://www.grw-immobilier.com/.
Structured data in place
Structured data found: .
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.grw-immobilier.com/catalog/sitemaps.php.
AI search readiness
robots.txt blocks 1 AI answer engine crawler
1 of 6Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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://www.grw-immobilier.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.
Opted out of AI training for 3 crawlers
robots.txt blocks GPTBot, ClaudeBot and Google-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (535 words), so crawlers that don't run JavaScript still read it.
Other pages
8 linked pages are broken
Your homepage links to https://www.grw-immobilier.com/contact_us.php, https://www.grw-immobilier.com/recrutement.php, https://www.grw-immobilier.com/selection.php, https://www.grw-immobilier.com/estimation.php, https://www.grw-immobilier.com/create_alerte_mail.php and https://www.grw-immobilier.com/mentions.php and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.
1 linked page hidden from search
https://www.grw-immobilier.com/catalog/mentions.php is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages share a meta description
https://www.grw-immobilier.com/content/1/notre-agence.html, https://www.grw-immobilier.com/catalog/estimation.php and https://www.grw-immobilier.com/catalog/mentions.php use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.grw-immobilier.com/catalog/news.php, whose canonical is https://www.grw-immobilier.com/news//les-caracteristiques-d-une-transaction-immobiliere-a-rambouillet-avec-une-agence-ou-un-mandataire.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
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
Every page has a meta description
All 7 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.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
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 417 words of copy
The homepage carries about 417 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT”.
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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
8Opening 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.
5 other companies contacted
Loading the homepage contacts 5 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 grw-immobilier.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on grw-immobilier.com, including 16 speed issues, 4 SEO 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.