Search the site · Ask Zorva

Results appear as you type. Press Enter and Zorva answers from this site’s own pages.

Public scan result · scored by the Zorva Labs website scan

nashkingspc.com scored 24/100 on the website scan.

Major issues

nashkingspc.com · Scanned 2026-10-21

33 passed11 warnings28 failed

  • Technical SEO & indexability5 of 10 points
  • On-page SEO & content9 of 25 points
  • AI search / AEO / GEO readiness2 of 35 points
  • Local SEO & entity signals0 of 5 points
  • Speed, scripts & mobile6 of 20 points
  • Conversion & lead generation2 of 5 points

Why AI search is 35 of the 100 points

Google is sending fewer people to websites. When it answers with an AI Overview, the top-ranked page's click rate is 58% lower than it would otherwise be (Ahrefs, 300,000 keywords, December 2023 against December 2025), and 68% of Google searches now end without a click at all (SparkToro, January–April 2026). The answer comes more and more from Google's AI, ChatGPT, Gemini and Perplexity, and they name the businesses whose sites they can read and quote. That is what this part of the scan measures, so it carries the most points. Every area's points fall faster than its checks: a warning counts a quarter of a pass, and an area half done earns about a third of its points, because search and AI answers go to the sites that finish the work.

What to fix first

  • ✗

    Readable without JavaScript +1 point

    Only 0 words are in the HTML the server sends; the rest of the page is drawn by JavaScript in the browser (an empty app container a script fills). ChatGPT's, Claude's and Perplexity's crawlers run no JavaScript, so to them the page is close to blank.

    What we’d do: The page's words are in the HTML the server sends — built ahead of time or rendered on the server — so every crawler reads what a visitor reads.

  • ✗

    FAQPage schema +5 points

    No FAQ — not in the schema and not on the page. Question-and-answer blocks are what the answer engines lift most readily.

    What we’d do: Every substantive page carries a visible FAQ with FAQPage schema built from the same text.

  • ✗

    llms.txt +5 points

    /llms.txt returns a web page, not a text file — the site answers unknown paths with its home page, so there is no llms.txt and no real 404 either.

    What we’d do: Every site ships an llms.txt written from its facts, and unknown paths return 404.

  • ✗

    Questions answered on the page +5 points

    No question is asked and answered on the 1 page read. When someone asks ChatGPT or Google's AI about a service, the engines quote pages that ask that question and answer it in a sentence or two.

    What we’d do: Every service page answers the questions people ask about that service — four or more, each asked as a heading and answered in its first sentence — with FAQPage schema from the same text.

  • !

    Page title +3 points

    “Professional Pressure Washing Nashville TN | Nash King's Pro Clean” is 66 characters. Google shows about 60 and cuts the rest, so the end of it is lost in results.

    What we’d do: We write titles of 30–60 characters, the topic first and the brand last, so nothing is cut.

Every check, by category (103 checks)

Technical SEO & indexability 5 of 10 points

  • ✗

    Security headers

    Missing 3 of the four baseline security headers: Content-Security-Policy, frame protection (X-Frame-Options or CSP frame-ancestors), Referrer-Policy.

    What we’d do: Content-Security-Policy, X-Content-Type-Options, frame protection and Referrer-Policy on every response.

  • ✗

    Sitemap

    No sitemap found or at /sitemap.xml, /sitemap_index.xml or /wp-sitemap.xml. Crawlers have to discover every page by following links.

    What we’d do: A sitemap generated from the site's pages on every build, named in robots.txt and submitted to Google and Bing on every deploy.

  • ✗

    Missing pages return 404

    A made-up URL returns 200 with a page. These soft 404s get crawled and indexed as real pages and waste the crawl on nothing.

    What we’d do: Missing routes return a real 404 with a helpful page.

  • !

    robots.txt

    /robots.txt returns the HTML of a page instead of a robots file — the site answers every path with a page, which is also a soft 404.

    What we’d do: A real robots.txt that names the sitemap and keeps only the private paths out.

  • !

    Lighthouse best practices

    Lighthouse best practices 81/100 — the report names what to fix.

    What we’d do: No console errors, no deprecated APIs, images at their real aspect ratio, HTTPS everywhere.

  • •

    HTTPS certificate

    The certificate could not be read from this platform, but the page was fetched over HTTPS.

  • •

    Structured data Google accepts

    Skipped — no structured data on the pages read.

  • •

    Internal links resolve

    Too few of the site's links answered this scan to judge (2 tried).

  • •

    Sitemap named in robots.txt

    Skipped — no robots.txt.

  • •

    Sitemap lists the live URLs

    Skipped — no sitemap.

  • •

    Sitemap dates

    Skipped — no sitemap.

  • ✓

    Indexable by search engines

    No noindex on the page or in the headers, and robots.txt lets Googlebot in.

  • ✓

    Canonical URL

    Canonical is https://nashkingspc.com/.

  • ✓

    HSTS header

    Strict-Transport-Security is set — browsers remember to use HTTPS.

  • ✓

    Mixed content

    Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.

  • ✓

    HTTP redirects to HTTPS

    http:// redirects (301) to https://www.nashkingspc.com/.

  • ✓

    Language declared

    <html lang="en">.

  • ✓

    Redirect chain

    One redirect (301) to https://nashkingspc.com/.

  • ✓

    www and apex agree

    www.nashkingspc.com redirects (301) to nashkingspc.com.

  • ✓

    Lighthouse SEO score

    Lighthouse SEO 92/100.

On-page SEO & content 9 of 25 points

  • ✗

    Single H1

    No H1 heading on the page — the one line that says what the page is about.

    What we’d do: Every page gets one H1 that names the service and the place.

  • ✗

    Image alt text

    1 of 1 images have no alt attribute — screen readers and image search get nothing.

    What we’d do: Every image gets an alt that says what is in it; decorative ones get alt="".

  • ✗

    Readable content in the HTML

    The HTML carries only 0 words of readable text. If the page is drawn by JavaScript, search engines and AI crawlers may be seeing an empty page.

    What we’d do: Every page's words are in the HTML the server sends, not assembled in the browser.

  • ✗

    A page for each service

    No service pages linked from the home page (no sitemap to read): the site is one page, or its services share one. Each search is for one service, and a page that covers them all ranks for none.

    What we’d do: A page for every service the business sells, each with its own title, its own words, its own FAQ and Service schema, so a search for that service lands on the page about it and an engine can quote it.

  • ✗

    About and privacy pages

    Neither an About page nor a privacy policy is linked from the home page: nothing tells a visitor, or Google's quality raters, who runs the business or what happens to what they send.

    What we’d do: An About page with the owner and the crew by name, their photos and roles, and a privacy policy, both linked from every page's footer.

  • !

    Page title

    “Professional Pressure Washing Nashville TN | Nash King's Pro Clean” is 66 characters. Google shows about 60 and cuts the rest, so the end of it is lost in results.

    What we’d do: We write titles of 30–60 characters, the topic first and the brand last, so nothing is cut.

  • •

    Titles across the site

    Skipped — no inner page read.

  • •

    No stock or AI-marked pictures

    No pictures on the pages read.

  • •

    Descriptions across the site

    Skipped — no inner page read.

  • •

    Pages that repeat each other

    Skipped — no inner page read.

  • •

    Canonical and share card on every page

    Skipped — no inner page read.

  • •

    Pictures named and described for what they show

    No pictures on the pages read.

  • •

    Title and H1 differ

    Skipped — no title or no H1 to compare.

  • •

    Titles lead with the subject

    Skipped — no inner page read.

  • •

    Service pages link each other

    Skipped — no service page read.

  • •

    Pages read

    No sitemap to pick inner pages from, so the home page stands for the site.

  • •

    Article schema on the post

    Skipped — no post found in the sitemap.

  • ✓

    Meta description

    149 characters — fills the space Google shows without being cut.

  • ✓

    Social share cards

    Open Graph title and image and a Twitter card with its own image. A share on any platform unfurls with a picture.

  • ✓

    No stock phrases

    None of the phrases copy falls back on when it has no facts (“look no further”, “we pride ourselves”, “one-stop shop”, a run of “top-notch” and “peace of mind”) on the 1 page read.

  • ✓

    No placeholder or template text

    No template or placeholder text on the 1 page read — no lorem ipsum, sample address or number, “add your text here”, or “undefined” where a value should be.

  • ✓

    Not a stock template

    No builder or stock theme shows in the page: no template credit, demo pictures or sample text.

  • ✓

    Share image loads

    The share image loads (image/webp, 44 KB).

  • ✓

    Favicon

    No favicon link, but /favicon.ico is served — browsers and Google find it there.

  • ✓

    A menu a thumb can use

    A header with no menu links to read.

AI search / AEO / GEO readiness 2 of 35 points

  • ✗

    FAQPage schema

    No FAQ — not in the schema and not on the page. Question-and-answer blocks are what the answer engines lift most readily.

    What we’d do: Every substantive page carries a visible FAQ with FAQPage schema built from the same text.

  • ✗

    llms.txt

    /llms.txt returns a web page, not a text file — the site answers unknown paths with its home page, so there is no llms.txt and no real 404 either.

    What we’d do: Every site ships an llms.txt written from its facts, and unknown paths return 404.

  • ✗

    Questions answered on the page

    No question is asked and answered on the 1 page read. When someone asks ChatGPT or Google's AI about a service, the engines quote pages that ask that question and answer it in a sentence or two.

    What we’d do: Every service page answers the questions people ask about that service — four or more, each asked as a heading and answered in its first sentence — with FAQPage schema from the same text.

  • ✗

    Readable without JavaScript

    Only 0 words are in the HTML the server sends; the rest of the page is drawn by JavaScript in the browser (an empty app container a script fills). ChatGPT's, Claude's and Perplexity's crawlers run no JavaScript, so to them the page is close to blank.

    What we’d do: The page's words are in the HTML the server sends — built ahead of time or rendered on the server — so every crawler reads what a visitor reads.

  • ✗

    JSON-LD present and valid

    No JSON-LD on the page. Google and the answer engines get no structured statement of what this is.

    What we’d do: Every page carries Organization or LocalBusiness, WebSite, BreadcrumbList and the page's own type.

  • ✗

    Extractable structure

    No H2 headings: 0 H2s, 0 H3s, 0 list items. The page reads as one block, which neither search nor AI can quote from.

    What we’d do: Every page is written in headed sections with lists and question headings, so an answer can be lifted whole.

  • ✗

    The first paragraph answers

    The home page has no H1 to answer under. An answer engine quotes the sentence right under the heading.

    What we’d do: The first paragraph under the headline answers the question the page is for — what, where, for whom — in two or three sentences, so a searcher sees it without scrolling and an engine can lift it whole.

  • •

    FAQ questions visible on the page

    Skipped — no FAQ schema to compare.

  • •

    FAQs on the inner pages

    Skipped — no inner page read.

  • •

    Specifics an engine can cite

    Skipped — no service page or post read to hold to the competitor test.

  • •

    Schema on the inner pages

    Skipped — no inner page read.

  • •

    Freshness dates in schema

    No dateModified or datePublished in the schema. Not expected on every home page; a freshness date helps the engines trust the page is current.

  • •

    Speakable specification

    No speakable specification. Google's speakable is a news-only beta, so this is noted, not scored.

  • ✓

    AI answers may quote the page

    Nothing on the page stops an answer engine from quoting it: no nosnippet, max-snippet limit, noarchive or noai.

  • ✓

    AI crawlers allowed

    No robots.txt, so every AI crawler is allowed by default. GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot each get the home page from the edge, as a browser does.

Local SEO & entity signals 0 of 5 points

  • ✗

    Business entity schema

    No Organization or LocalBusiness schema. The engines have no entity to attach the reviews, the phone and the service area to.

    What we’d do: LocalBusiness (or the trade's own type) with name, phone, address, hours, service area and sameAs on every page.

  • ✗

    Service area stated by town

    The home page does not say which towns the business serves — visitors and engines both need it.

    What we’d do: The towns the business works in, named — a service-area line in the footer of every page and areaServed in the schema with each town — so a search from any of them finds it.

  • ✗

    Linked to its profiles

    Nothing ties this site to the business's profiles elsewhere: no sameAs in the schema, and no link to a Google Business Profile, Facebook or Yelp page. Those links are how the engines tell this business from others with a similar name.

    What we’d do: The business node's sameAs lists every real profile — the Google Business Profile first, then Facebook, Yelp, BBB and the trade's own directories — and the footer links to them.

  • ✗

    Address and phone on the page

    Neither a phone number nor a town or street address is on the home page as text. Map search and the answer engines match a business to a place by what its pages say.

    What we’d do: The business name, phone and town — or street address — in the footer of every page, exactly as the Google Business Profile has them, and the same in the schema.

  • ✗

    Trust signals

    No insurance, guarantee, license or accreditation language on the home page. Noted, not scored.

    What we’d do: Insurance, a written guarantee and the trade's credentials, stated plainly where the visitor decides.

  • ✗

    Reviews on the page

    No reviews, rating or testimonials on the home page, and no link to a profile that has them — the proof visitors look for first.

    What we’d do: The Google rating and count, three or more reviews quoted word for word with the reviewer's first name, and a link to the profile they live on — in the HTML, so the engines read them too.

  • ✗

    Hours shown and in schema

    No hours on the home page or in the schema. “Are they open now?” is the first thing map search and a visitor want to know.

    What we’d do: The hours on every page, in the footer or beside the number, and the same hours in openingHoursSpecification, as the Business Profile shows them.

  • !

    Site name for Google

    Nothing names the site: no WebSite schema and no og:site_name, so Google picks the name shown above each result from the title and headings.

    What we’d do: WebSite schema on the home page with the business's name, and alternateName for any other name people use, as on the Business Profile.

  • •

    Business schema completeness

    Skipped — no business node to read.

  • •

    The trade's own schema type

    Skipped — no business node to read.

  • •

    A named person

    No named person in the schema. Not required: a home-service company is known by its brand, and the business node carries what the engines tie the reviews and the pages to. A Person belongs on the About page only when the owner wants to be named.

Speed, scripts & mobile 6 of 20 points

  • ✗

    Nothing blocks the first paint

    2 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 1.6 s of the first paint on waiting for them.

    What we’d do: The styles the first screen needs are inlined and the rest load after it, every script is deferred, and the hero image is preloaded: nothing stands between the HTML and the first paint.

  • ✗

    Readable and tappable on a phone

    10 pieces of text are too faint to read against their background (“Join hundreds of satisfied customers across Middle Tennessee” 3.74:1, “LEAVE US A REVIEW ON GOOGLE” 4:1, “* Required fields. We'll contact you within 24 hours.” 3.76:1); WCAG asks 4.5:1 for text that size. Google's test read the page as a phone shows it.

    What we’d do: Every word clears WCAG AA contrast — 4.5:1, or 3:1 for large text — measured as rendered at phone and desktop widths, and every button and link is at least 44 pixels square with room around it.

  • ✗

    Pinch-to-zoom allowed

    The viewport tag blocks pinch-to-zoom (user-scalable=no or maximum-scale=1). People with low vision cannot enlarge the page, and Lighthouse's accessibility audit fails it.

    What we’d do: Pinch-to-zoom stays on; the layout is built so nothing needs it.

  • ✗

    Page weight

    3.7 MB downloaded to show the home page on a phone. On a cellular connection that is many seconds before the page settles.

    What we’d do: Our pages weigh 300–700 KB in all: 20–50 KB of HTML, two fonts, pictures sized to the box they fill in WebP or AVIF, and almost no JavaScript.

  • !

    Mobile PageSpeed score

    Lighthouse mobile performance 69/100. Google calls 50–89 “needs improvement”; lab runs vary, so we grade 70 and up as a pass.

    What we’d do: Our sites score 90 and up on mobile: static HTML from an edge network, images sized and in modern formats, almost no JavaScript.

  • !

    Lighthouse accessibility score

    Lighthouse accessibility 83/100 — the report names what to fix.

    What we’d do: Contrast, labels, landmarks and focus order are checked on every page before it ships.

  • !

    Scripts and third parties

    4 scripts, 428 KB of JavaScript, from 3 third parties (Google Tag Manager, manus-analytics.com and Facebook). Every script is a download, a parse and a run on a phone before the visitor can tap anything.

    What we’d do: Our pages load one analytics tag and the form's bot check — two third parties and under 100 KB of JavaScript — and nothing runs before the page is drawn.

  • !

    Fonts

    5 font files (77 KB) from Google Fonts.

    What we’d do: Two font families in the weights the page uses, from one host, with font-display set so the words show at once in a fallback face.

  • !

    HTML weight

    About 104 KB compressed (363 KB of HTML) — heavy for one page; the usual cause is inlined scripts and styles.

    What we’d do: Our pages are 20–50 KB compressed: the words and the markup, nothing bundled in.

  • !

    Largest Contentful Paint (LCP)

    Largest Contentful Paint 5.9 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).

    What we’d do: The hero image sized and preloaded, no render-blocking scripts, a fast first byte: our pages paint in about a second.

  • !

    What would speed it up most

    PageSpeed's biggest savings on this page: Render-blocking requests (about 1.6 s); Reduce unused JavaScript (about 1.1 s); Avoid multiple page redirects (about 0.8 s).

    What we’d do: These are the first three things we would fix.

  • •

    Image hygiene

    Only 1 raster image on the page — not enough to grade.

  • •

    Interaction to Next Paint (INP)

    No real-user INP yet — Google reports it once a page has enough visitors on Chrome. It measures how quickly the page reacts to a tap.

  • ✓

    Mobile viewport

    The viewport meta tag is set for phones.

  • ✓

    No popup on arrival

    Nothing covers the page on arrival: no popup, no email gate.

  • ✓

    No hero slider or autoplay video

    One hero: no slider and no autoplaying video in the first screen.

  • ✓

    Cumulative Layout Shift (CLS)

    Cumulative Layout Shift 0.02 (lab). Google's thresholds: 0.1 good, 0.25 poor.

  • ✓

    The hero image loads first

    The largest thing on the first screen is text or a styled block (<p data-loc="client/src/components/HeroSection.tsx:81" class="font-dis), which paints as soon as the HTML arrives.

  • ✓

    No fixed-width overflow

    No inline widths of 400px or more that would push past a phone screen.

  • ✓

    Time to first byte

    First byte in 720 ms from our server.

  • ✓

    Compression

    Compressed, as Google's PageSpeed test read the page from outside; this scan runs inside Cloudflare's network, where Cloudflare's compression never shows.

  • ✓

    HTTP/2 or HTTP/3

    HTTP/3 advertised via Alt-Svc.

  • ✓

    One chat widget at most

    No chat widget scripts on the page.

  • ✓

    Static files cached

    2 files served with a short or missing cache lifetime, 0 of them the site's own.

Conversion & lead generation 2 of 5 points

  • ✗

    Contact form

    No form and no contact link on the home page.

    What we’d do: A short quote form on every page, stored first and emailed second.

  • ✗

    Tappable phone number

    No phone number on the home page. For a service business the call is the conversion.

    What we’d do: A tappable number in the header, the hero and the footer of every page.

  • •

    Lead form wiring

    No form in the home page's HTML to read — a form a script draws in the browser can't be read from outside.

  • •

    A lead form that fits a phone

    No form on the home page to read; the contact form check says whether one is linked.

  • •

    Chat or text option

    No chat or text option. Not a fault, but a share of visitors will not call; an assistant that answers in seconds, day and night, is the cheapest lead a site can add.

  • ✓

    Call to action in the first screen

    A phone link, a form or a quote button appears in the top of the page.

  • ✓

    Analytics installed

    Measured by Google Analytics, Umami, Meta pixel.

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

Want these fixed?

Every fix above is part of the work Zorva Labs does. Tell us the business and what you want from the site, and a written, priced proposal comes back in one business day.

Want this fixed?

We can fix every issue on nashkingspc.com.

Zorva Labs builds, hosts and grows websites for businesses across the United States — including the fixes flagged above. Every engagement is priced to the project, with a written proposal in one business day.

ReplyOne business day
ProposalWritten · scoped · priced
ContractMonth to month
Proposal request

Tell us what you need

No spam · One business day reply · Month to month

nashkingspc.com — 24/100 website scan | Zorva Labs