stackoverflow.com

Se afișează primele 10 probleme. Auditul complet cu remedieri la nivel de cod este disponibil pe planul gratuit.

• 01
  FAIL · technical

  Robots.txt

  The robots.txt file was not found on the website. Without this file, search engine crawlers receive no instructions on how to crawl the site, which may lead to indexing of unwanted pages or inefficient use of crawl budget.
  Înscrie-te pentru a vedea cum se remediază
• 02
  FAIL · onpage

  Meta Description

  The meta description is missing from the page. Search engines use it to generate the snippet shown in search results. Without a description, the search engine will select an arbitrary text fragment from the page.
  Înscrie-te pentru a vedea cum se remediază
• 03
  WARN · onpage

  H1 Heading

  Found 4 <h1> tags on the page. It is recommended to use only one H1 heading per page. Multiple H1 tags dilute topical relevance and may confuse search engines.
  Înscrie-te pentru a vedea cum se remediază
• 04
  FAIL · technical

  Canonical Tag

  The canonical tag is missing. Without a canonical URL, search engines may index duplicate versions of the page, leading to diluted link equity and duplicate content issues.
  Înscrie-te pentru a vedea cum se remediază
• 05
  FAIL · technical

  XML Sitemap

  The sitemap.xml file was not found. A sitemap helps search engines discover all important pages, understand the site structure, and prioritize crawling. Without it, some pages may not be indexed.
  Înscrie-te pentru a vedea cum se remediază
• 06
  FAIL · performance

  GZIP/Brotli Compression

  The server does not use response compression (GZIP or Brotli). Without compression, the browser downloads the full size of HTML, CSS, and JavaScript, significantly increasing load time, especially on slow connections. Compression can reduce transferred data size by 60–80%.
  Înscrie-te pentru a vedea cum se remediază
• 07
  FAIL · performance

  Browser Caching

  Only 1 out of 4 caching headers found (Cache-Control). Missing: Expires, ETag, Last-Modified. Caching is virtually unconfigured, causing resources to be reloaded on every visit.
  Înscrie-te pentru a vedea cum se remediază
• 08
  WARN · performance

  Time to First Byte (TTFB)

  Time to First Byte is 501 ms (0.50 sec). This is acceptable but there is room for improvement. The optimal value is less than 200 ms. A slow TTFB delays the start of page rendering.
  Înscrie-te pentru a vedea cum se remediază
• 09
  FAIL · performance

  Render-Blocking Resources

  Found 10 render-blocking resources (3 CSS, 7 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).
  Înscrie-te pentru a vedea cum se remediază
• 10
  FAIL · performance

  Image Lazy Loading

  None of the 15 images on the page use lazy loading (loading="lazy"). All images are loaded simultaneously when the page opens, significantly slowing down initial load and consuming user bandwidth.
  Înscrie-te pentru a vedea cum se remediază