sapori.has.restaurant

Showing top 10 issues. Full audit with code-level fixes available on the free plan.

• 01
  WARN · onpage

  Meta Description

  The meta description is long (230 chars). Google + Bing truncate around 155–160 chars on desktop and ~120 chars on mobile — anything past that is invisible in classic SERPs (though ChatGPT / Claude / Perplexity may still cite the full text). Trailing text often contains the CTA, which gets cut off.
  Sign up to see how to fix this
• 02
  FAIL · ai-readiness

  Knowledge Panel Readiness

  Low knowledge-panel readiness — score 25/100. AI search engines and Google Knowledge Panel cannot confidently identify this brand. The cheapest, fastest fixes are: (1) add Organization JSON-LD with a sameAs chain (Wikipedia, Wikidata, LinkedIn, Crunchbase, GitHub, social), (2) make NAP (Name/Address/Phone) visible in the footer or contact page, (3) create a Wikidata entry (low notability bar), then (4) pursue Wikipedia once notability is established.
  Sign up to see how to fix this
• 03
  FAIL · onpage

  Image Alt Attributes

  14 out of 14 images are missing the alt attribute (only 0% have alt). A significant portion of images is inaccessible to search engines and users with disabilities.
  Sign up to see how to fix this
• 04
  FAIL · technical

  Viewport Meta Tag

  The viewport meta tag was found but does not contain the required "width=device-width" directive. Current value: "initial-scale=1.0, maximum-scale=1.0, user-scalable=0". Without this directive, the browser will not adapt the page width to the mobile device screen.
  Sign up to see how to fix this
• 05
  FAIL · performance

  Browser Caching

  Caching headers are completely absent. Without Cache-Control, Expires, ETag, and Last-Modified, the browser will reload all resources on every visit, significantly increasing load time and consuming user bandwidth.
  Sign up to see how to fix this
• 06
  FAIL · ai-readiness

  Structured Data Completeness

  No structured data (JSON-LD / Schema.org) found. AI search engines rely heavily on structured data to understand and cite content. Without it, your pages are much less likely to appear in AI-generated answers.
  Sign up to see how to fix this
• 07
  FAIL · performance

  Render-Blocking Resources

  Found 13 render-blocking resources (9 CSS, 4 JS) — this is too many. The browser must download and process all of these files before it can start rendering the page. This critically delays First Contentful Paint (FCP) and Largest Contentful Paint (LCP).
  Sign up to see how to fix this
• 08
  FAIL · security

  Security Headers

  Only 0 out of 6 modern security headers found. Missing: x-frame-options, x-content-type-options, strict-transport-security, content-security-policy, referrer-policy, permissions-policy. The site is exposed to XSS (no CSP), clickjacking (no X-Frame-Options / CSP frame-ancestors), MIME-sniffing (no X-Content-Type-Options), and HTTPS-stripping MITM (no HSTS). Mozilla Observatory grades sites with <4 headers as D or F.
  Sign up to see how to fix this
• 09
  FAIL · security

  Mixed Content

  Found 3 element(s) with mixed content (HTTP resources on an HTTPS page). By tag: <script>: 3. Browsers may block these resources, causing incomplete page loading.
  Sign up to see how to fix this
• 10
  FAIL · content

  Keyword Stuffing

  Keyword stuffing detected. The following words appear excessively often: "italian" — 3 times (3.1%), "like" — 3 times (3.1%). The acceptable keyword density is 1-2%. Exceeding the 3% threshold may result in search engine penalties.
  Sign up to see how to fix this