Website review, no card needed

oci-urbanisme.fr logo

oci-urbanisme.fr website review

Visit site (opens in a new tab)Reviewed 8 November 202636 issues · 80 checks

This review found 36 issues worth fixing on oci-urbanisme.fr, 13 of them high impact, across 80 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 oci-urbanisme.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. oci-urbanisme.fr at 1.9 s1.9 s
  2. oci-urbanisme.fr at 3.8 s3.8 s
  3. oci-urbanisme.fr at 5.7 s5.7 s
  4. oci-urbanisme.fr at 7.6 s7.6 s
  5. oci-urbanisme.fr at 9.5 s9.5 s
  6. oci-urbanisme.fr at 11.4 s11.4 s
  7. oci-urbanisme.fr at 13.4 s13.4 s
  8. oci-urbanisme.fr at 15.3 s15.3 s

Speed

11 to fix64
  • Use efficient cache lifetimes

    16.8 s · 3.9 MB

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

  • Reduce unused JavaScript

    4.3 s · 905 KiB

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

  • Improve image delivery

    2.6 s · 585 KiB

    7 images could be 585 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 64

    64/100

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

  • Reduce unused CSS

    750 ms · 125 KiB

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

  • Legacy JavaScript

    750 ms · 59 KiB

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

  • Font display

    550 ms

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

  • Google Tag Manager adds 323 ms

    323 ms

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

  • Minify JavaScript

    310 ms · 56 KiB

    56 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.1 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Hotjar and Matomo and others), adding 867 KiB and 410 ms of main-thread time.

  • 7 long tasks on the main thread

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

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

    212 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 27.8 s

    27.8 s

    Your largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Automatisez l’instruction des dossiers d’urbanisme Découvrez”.

  • Speed Index: 18.1 s

    18.1 s

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

  • Time to Interactive: 27.9 s

    27.9 s

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

  • 21 images without width and height

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

3 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 108 ms

    108 ms

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

  • Cumulative Layout Shift: 0.05

    0.05

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

Images and page weight

2 to fix60
  • Page weight: 4.9 MB in 112 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 112 requests on a phone: images 2.7 MB (39), scripts 1.8 MB (40) and fonts 255 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    233 KiB

    2 images are downloaded at several times the size a phone draws them, for example Logo-OCI-Urbanisme.png at 925 px wide, shown at 47 px. Resized copies would save about 233 KiB.

  • 3 images in older formats

    3 images (281 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.

  • 2 images below the first screen load straight away

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

  • About 1.4 g of CO₂ per visit

    1.39 g

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

Accessibility

8 to fixGoogle 8089
  • 10 buttons without a name

    10 buttons have no accessible name, so screen readers announce just “button”.

  • 4 text elements with low contrast

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

  • 4 tap targets too small

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

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 2 form fields without a label

    2 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 32 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 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
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “OCI Urbanisme | Logiciels ADS urbanisme et services pour collectivités”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 48 internal links, 30 external

    The homepage links to 48 pages on oci-urbanisme.fr and 30 external pages.

6 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “OCI Urbanisme équipe les collectivités mairies et EPCI de son logiciel d'instruction des dossiers d'urbanisme ADS et le…”.

  • One H1 headline

    Your main headline reads: “Netads La boite à outils métier du service urbanisme”.

  • Canonical URL set

    The canonical URL is https://www.oci-urbanisme.fr/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.oci-urbanisme.fr/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://www.oci-urbanisme.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.

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 (752 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 3 linked pages hidden from search

    https://www.oci-urbanisme.fr/ads-foncier, https://www.oci-urbanisme.fr/services and https://www.oci-urbanisme.fr/societe are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.oci-urbanisme.fr/ads-foncier, https://www.oci-urbanisme.fr/societe, https://www.oci-urbanisme.fr/societe/nos-partenaires, https://www.oci-urbanisme.fr/societe/rejoignez-nous, https://www.oci-urbanisme.fr/demande-de-contact and https://www.oci-urbanisme.fr/demande-de-devis have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.oci-urbanisme.fr/ads-foncier has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.oci-urbanisme.fr/ads-foncier/dematerialisation-ads, https://www.oci-urbanisme.fr/services/architectures-licensing, https://www.oci-urbanisme.fr/societe, https://www.oci-urbanisme.fr/societe/mieux-nous-connaitre, https://www.oci-urbanisme.fr/societe/nos-partenaires and https://www.oci-urbanisme.fr/societe/rejoignez-nous and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 9 small tap targets

    9 of 17 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

3 to fix75
  • 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.

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

  • Thin social proof

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

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

    The homepage carries about 584 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Formulaire de contact”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Hotjar and Matomo.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 6 cookies set on arrival

    6

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 oci-urbanisme.fr, 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 Analytics | Google Tag Manager | Hotjar | Matomo
Hosting
Societe Francaise Du Radiotelephone - SFR SA

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 oci-urbanisme.fr, including 15 speed issues, 2 SEO issues and 3 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