SEOWebsiteTool
76Grade B

peinture-olasso.fr

Peinture Olasso — Votre devis peinture en 3 minutes

3 failed · 11 warnings · 15 passed

Audited Tue, 14 Jul 2026 10:15:45 GMT · https://peinture-olasso.fr/

Meta & Head

13.2/25

Title, description, canonical, social tags — what search engines read first.

  • Viewport meta tagmedium impactlow effort

    No viewport meta tag found

    Google crawls and ranks the mobile version of your site first, and without a viewport tag phones render pages at desktop width — tiny, zoomed-out text that fails mobile-usability checks and drives visitors straight back to the results. Add <meta name="viewport" content="width=device-width, initial-scale=1"> inside <head> on every page. Resist adding user-scalable=no or maximum-scale=1 while you're there: disabling pinch-zoom hurts accessibility and gets flagged by audits.

  • Open Graph tagsmedium impactlow effort

    No Open Graph tags found

    Open Graph tags control how your page looks when shared on Facebook, LinkedIn, Slack, WhatsApp, and most chat apps; without them, links render as a bare URL or with guessed text, and far fewer people click through. Add four meta tags to <head>: og:title, og:description, og:url, and og:image — an image around 1200x630 pixels works well across platforms. Use absolute https:// URLs for og:image and og:url; relative paths are the most common reason preview images silently fail to appear.

  • Character encoding declaredlow impactlow effort

    No character encoding declaration found

    Without a declared character encoding, browsers have to guess how to decode your text; a wrong guess garbles apostrophes, accents, and currency symbols, and the guessing itself can delay rendering. Add <meta charset="utf-8"> as the very first element inside <head> — browsers only scan the opening bytes of the document for it. Also confirm your server isn't sending a conflicting charset in the Content-Type header, since a mismatch produces exactly the garbled text you're trying to prevent.

  • Meta descriptionhigh impactlow effort

    Meta description is "Peinture Olasso, SARL de peinture en bâtiment sur la Côte Basque et le Sud des Landes. Estimation indicative en ligne en 3 minutes, validée ensuite par l'artisan." (162 characters)

    Search engines truncate descriptions past roughly 160 characters, and very short ones waste the snippet space that persuades searchers to pick your listing over the next one. Rewrite it to 70–160 characters: state what the page offers, work the primary keyword in naturally (matching words get bolded in results), and end with a benefit or call to action. Don't cram in keywords — the description influences clicks, not rankings, so write it for humans.

  • Canonical URLmedium impactlow effort

    No <link rel="canonical"> found

    When the same page is reachable at several URLs — tracking parameters, trailing-slash variants, http vs https — search engines may split ranking signals across the duplicates. A canonical tag names the one version that should get all the credit. Add <link rel="canonical" href="https://www.example.com/page/"> to the <head>, pointing at the page's preferred absolute URL. Double-check it's self-referencing on the primary version: a canonical that points at the wrong page can quietly de-index the right one.

  • Faviconlow impactlow effort

    No <link rel="icon"> and /favicon.ico does not respond

    Google displays favicons beside mobile search results, and browsers show them in tabs, bookmarks, and history — a missing icon makes your listing look generic and less trustworthy next to competitors. Create an icon of at least 48x48 pixels, serve it at /favicon.ico, and reference it with <link rel="icon" href="/favicon.png" type="image/png"> in <head>. Make sure robots.txt doesn't block the icon's path — search engines must be able to crawl it to display it.

  • Twitter card taglow impactlow effort

    No twitter:card meta tag found

    X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.

2 passing checks
  • Title tag<title> is "Peinture Olasso — Votre devis peinture en 3 minutes" (51 characters)
  • Page allows indexingNo restrictive robots meta tag

Content & Structure

21.9/25

Headings, copy depth, images, structured data, internal linking.

  • Structured data (JSON-LD)medium impactmedium effort

    No JSON-LD structured data blocks found

    Structured data makes your listing eligible for rich results — star ratings, FAQs, breadcrumbs, product prices — which occupy more space on the results page and draw more clicks than plain blue links. Add a <script type="application/ld+json"> block with a schema.org type that matches the page: Organization or WebSite for a homepage, Article for posts, Product for product pages. Only mark up content actually visible on the page — markup for invisible content violates Google's guidelines and can earn a manual action.

  • Heading hierarchylow impactlow effort

    Heading level jumps from h2 ("Des faits, pas des promesses") to h4 ("Titre professionnel des Compagnons")

    Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.

  • HTML lang attributelow impactlow effort

    No lang attribute on the <html> element

    The lang attribute tells search engines which language market the page belongs to and tells screen readers which pronunciation rules to use — without it, both are left guessing. Add it to the root element, e.g. <html lang="en">, or a regional variant like <html lang="pt-BR"> where the distinction matters. On multilingual sites, set it per page: hard-coding lang="en" in a shared template while serving German content actively misleads assistive technology and translation tools.

5 passing checks
  • Single H1 heading1 h1 found: "Pendant que votre artisan travaille, son assistant IA prépare votre projet."
  • Word count4696 words of visible text
  • Image alt text36 of 38 images have alt text
  • JavaScript-dependent contentvisible text ~10604 chars in the initial HTML
  • Internal linking31 internal, 1 external links

Technical

21.6/25

HTTPS, redirects, robots, sitemap, speed, crawlability.

  • robots.txt present and permissivemedium impactlow effort

    no robots.txt found

    Without a robots.txt, crawlers assume everything is allowed — not fatal, but you lose the ability to keep them out of low-value areas (internal search results, carts, admin paths) and the standard place to advertise your sitemap. Create a plain-text robots.txt at the site root with at least a "User-agent: *" line and "Sitemap: https://www.example.com/sitemap.xml". Don't use it to hide sensitive URLs, though — the file is public, and disallowing a page doesn't remove it from the index; use noindex or authentication for that.

  • XML sitemap availablemedium impactlow effort

    no sitemap.xml found

    Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.

  • Response compression enabledlow impactlow effort

    no content-encoding header

    This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.

  • HTML5 doctypelow impactlow effort

    No doctype declaration found at the start of the document

    Without a doctype, browsers render in quirks mode — inconsistent layout, and validators flag the page. Add <!DOCTYPE html> as the very first line of the document, before the <html> tag. Watch out for whitespace, comments, or BOM characters sneaking in before it.

8 passing checks
  • Served over HTTPSfinal URL uses https://
  • HTTP redirects to HTTPShttp:// redirects to https://
  • No mixed content0 http:// subresource references
  • Short redirect chainno redirects; URL resolves directly
  • Fast time to first byte144 ms
  • Reasonable HTML size274.9 KB
  • Missing pages return 404missing paths return HTTP 404/410
  • www and non-www resolve consistentlywww and non-www converge on the same host

Performance

Core Web Vitals scoring via Google PageSpeed is coming soon.

Share your score

Embed this live badge on your site — it updates whenever the audit is re-run.

SEO score badge for peinture-olasso.fr

More “p” sitesRecent audits