neocomputer.md

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

• 01
  FAIL · performance

  Time to First Byte (TTFB)

  Time to First Byte is 625 ms (0.63 sec) — this is too slow. The server takes a significant amount of time to process the request before it starts sending a response. This negatively affects all Core Web Vitals metrics, as the browser cannot begin rendering until the first byte is received.
  Sign up to see how to fix this
• 02
  WARN · technical

  Viewport Meta Tag

  The viewport meta tag restricts user zoom capability (user-scalable=no). This creates accessibility issues — users with visual impairments will not be able to enlarge the content. Google may consider this a degraded user experience.
  Sign up to see how to fix this
• 03
  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
• 04
  FAIL · performance

  Render-Blocking Resources

  Found 7 render-blocking resources (6 CSS, 1 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
• 05
  FAIL · performance

  Image Lazy Loading

  None of the 32 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.
  Sign up to see how to fix this
• 06
  FAIL · performance

  HTTP Requests Count

  The page loads 47 external resources — this is too many (6 CSS, 9 JS, 32 images). A high number of HTTP requests critically slows down page loading, as browsers are limited to 6 simultaneous connections per domain. This negatively affects all performance metrics.
  Sign up to see how to fix this
• 07
  FAIL · security

  Security Headers

  Only 1 out of 7 recommended security headers found. Missing: x-frame-options, x-content-type-options, content-security-policy, x-xss-protection, referrer-policy, permissions-policy. The site is vulnerable to multiple attack types, including XSS, clickjacking, and MIME-sniffing.
  Sign up to see how to fix this
• 08
  FAIL · security

  Server Signature

  The Server header reveals the software version: "nginx/1.28.2". Attackers can use specific version information to find known vulnerabilities. The X-Powered-By header reveals the framework in use: "PHP/7.4.33". This is a significant security risk — attackers gain information about the technology stack for targeted attacks.
  Sign up to see how to fix this
• 09
  FAIL · content

  Keyword Stuffing

  Keyword stuffing detected. The following words appear excessively often: "neocomputer" — 9 times (7%), "schimb" — 4 times (3.1%), "str" — 4 times (3.1%), "chiinu" — 4 times (3.1%), "program" — 4 times (3.1%), "lucru" — 4 times (3.1%), "luni" — 4 times (3.1%), "vineri" — 4 times (3.1%), "simbata" — 4 times (3.1%), "duminic" — 4 times (3.1%), "loading" — 4 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
• 10
  WARN · ai-readiness

  E-E-A-T Signals

  1/4 E-E-A-T signals found. Present: Contact information. Missing: Author attribution, Publication/modification date, About/Team page link. AI search engines prioritize content from sources that demonstrate clear authorship, timeliness, and trustworthiness.
  Sign up to see how to fix this