avantavl.com scored 31/100 on the website scan.
Major issues
avantavl.com · Scanned 2026-10-26
45 passed21 warnings20 failed
- Technical SEO & indexability9/10 of 10 points
- On-page SEO & content6/25 of 25 points
- AI search / AEO / GEO readiness6/35 of 35 points
- Local SEO & entity signals1/5 of 5 points
- Speed, scripts & mobile6/20 of 20 points
- Conversion & lead generation3/5 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
-
✗
FAQPage schema +4 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.
-
✗
Questions answered on the page +4 points
No question is asked and answered on the 2 pages 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.
-
✗
FAQs on the inner pages +4 points
The service page read carries no FAQ. The questions people ask about a service are what the answer engines quote.
What we’d do: Every service, area and post page carries its own researched questions — four or more, the ones people ask about that subject, none repeated from another page — visible and in FAQPage schema.
-
✗
Schema on the inner pages +3 points
The service page (/services) has no structured data. Past the home page the engines get no structured statement of what a page is or whose it is.
What we’d do: Every page carries the business node, a BreadcrumbList and its own type — a Service on each service page, BlogPosting on each post — so an engine knows what each page is and whose it is.
-
!
Specifics an engine can cite +2 points
The service page (/services): 196 words, 9 numbers, 0 names — thin for a page an answer engine should quote. They quote prices, timelines, counts, and named places, products and people.
What we’d do: Every page is written from the business's own facts: real prices or ranges, timelines, how many and how big, the products and brands used, the towns and neighborhoods worked in, the people by name — 300 words or more that no competitor could publish unchanged.
Every check, by category (103 checks)
Technical SEO & indexability 9 of 10 points
-
!
Security headers
Missing: X-Content-Type-Options, Referrer-Policy.
What we’d do: Content-Security-Policy, X-Content-Type-Options, frame protection and Referrer-Policy on every response.
-
!
Lighthouse SEO score
Lighthouse SEO 85/100 — the report names what to fix.
What we’d do: Our sites score 100 on Lighthouse SEO: every page crawlable, titled, described, with valid links and alt text.
-
!
Sitemap dates
Every page in the sitemap carries the same date (2026-10-17) — a build stamp, not the day each page changed. Google ignores dates it has learned not to trust.
What we’d do: Each page's lastmod is the day its own content last changed, written from the content's hash, never the build date.
-
•
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.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
Canonical URL
Canonical is https://avantavl.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.
-
✓
Sitemap
Sitemap at https://avantavl.com/sitemap.xml — an index of 3 sitemaps.
-
✓
Missing pages return 404
A made-up URL returns 404, so Google never indexes ghost pages.
-
✓
HTTP redirects to HTTPS
http:// redirects (308) to https://avantavl.com/.
-
✓
Internal links resolve
All 4 internal links read on the home page answer.
-
✓
Language declared
<html lang="en-US">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
robots.txt
robots.txt is served (1 group, 1 sitemap line).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://avantavl.com/sitemap.xml.
-
✓
www and apex agree
www.avantavl.com redirects (301) to avantavl.com.
-
✓
Sitemap lists the live URLs
The sitemap's 5 URLs are all on https://avantavl.com, and the pages read from it answer directly and are open to indexing.
-
✓
Lighthouse best practices
Lighthouse best practices 96/100.
On-page SEO & content 6 of 25 points
-
✗
Page title
“Audio/Video and Networking Installation servicing Nashville and Surrounding Areas” is 81 characters — a third of it is cut in search results.
What we’d do: We write titles of 30–60 characters, the topic first and the brand last.
-
✗
Meta description
The home page has no meta description, so Google writes its own from the page.
What we’d do: Every page gets a 120–160 character description written to earn the click.
-
✗
Titles across the site
the service page's title is 8 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
Image alt text
5 of 7 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="".
-
✗
Descriptions across the site
the service page has no description.
What we’d do: Every page gets its own 120–160 character description, checked in the build.
-
✗
A page for each service
No service pages in the sitemap: 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.
-
!
Single H1
2 H1 headings. One is the convention search engines and screen readers expect.
What we’d do: One H1 per page; the rest become H2s.
-
!
Readable content in the HTML
210 words of readable text on the home page — thin for a page that has to explain a business.
What we’d do: Home pages we write carry the services, the places, the proof and the questions people ask.
-
!
Pages that repeat each other
2 of the 6 sentences on the home page also appear on the service page (33%).
What we’d do: Every page is written once, for its own subject.
-
!
About and privacy pages
The home page links an About page (/about) but no privacy policy — a site whose form takes names, phone numbers and emails says what it does with them.
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.
-
!
Not a stock template
Built with GoDaddy's Website Builder, from templates thousands of businesses share. Nothing is left over from the template, but the layout says “GoDaddy's Website Builder” before it says anything about the business.
What we’d do: A site designed for this business — its own layout, type and colors, written from its own facts — with nothing left of whatever it was built from.
-
•
No stock or AI-marked pictures
No pictures on the pages read.
-
•
Pictures named and described for what they show
No pictures on the pages read.
-
•
Service pages link each other
Skipped — fewer than three service pages to link between.
-
•
Pages read
Read with the home page: service page https://avantavl.com/services.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
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 2 pages read.
-
✓
No placeholder or template text
No template or placeholder text on the 2 pages read — no lorem ipsum, sample address or number, “add your text here”, or “undefined” where a value should be.
-
✓
Share image loads
The share image loads (image/webp, 87 KB).
-
✓
Canonical and share card on every page
The inner page read names itself as its canonical, carries a share image and a Twitter card, and has one H1.
-
✓
Favicon
A favicon is linked — it shows in the tab and beside the site in Google's results.
-
✓
Title and H1 differ
The title and the H1 are different, each doing its own job.
-
✓
Titles lead with the subject
The inner pages' titles lead with their subject, not the business name.
-
✓
A menu a thumb can use
4 links in the header and menu, and the service page read is one tap from the home page.
AI search / AEO / GEO readiness 6 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.
-
✗
Questions answered on the page
No question is asked and answered on the 2 pages 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.
-
✗
FAQs on the inner pages
The service page read carries no FAQ. The questions people ask about a service are what the answer engines quote.
What we’d do: Every service, area and post page carries its own researched questions — four or more, the ones people ask about that subject, none repeated from another page — visible and in FAQPage schema.
-
✗
Schema on the inner pages
The service page (/services) has no structured data. Past the home page the engines get no structured statement of what a page is or whose it is.
What we’d do: Every page carries the business node, a BreadcrumbList and its own type — a Service on each service page, BlogPosting on each post — so an engine knows what each page is and whose it is.
-
✗
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.
-
✗
The first paragraph answers
The home page's headline is followed by buttons and pictures, not a sentence; the service page's first paragraph does not say what its headline is about. 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.
-
!
Specifics an engine can cite
The service page (/services): 196 words, 9 numbers, 0 names — thin for a page an answer engine should quote. They quote prices, timelines, counts, and named places, products and people.
What we’d do: Every page is written from the business's own facts: real prices or ranges, timelines, how many and how big, the products and brands used, the towns and neighborhoods worked in, the people by name — 300 words or more that no competitor could publish unchanged.
-
!
Extractable structure
Little for an engine to lift: 2 H2s, 1 H3s, 16 list items. Answer engines quote headed sections, lists and question-and-answer blocks.
What we’d do: Every page is written in headed sections with lists and question headings, so an answer can be lifted whole.
-
•
FAQ questions visible on the page
Skipped — no FAQ schema to compare.
-
•
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.
-
✓
llms.txt
llms.txt is published (1 KB), headed with the name and linking 5 pages of the site — a plain statement of the business for the AI engines to read.
-
✓
Readable without JavaScript
The page's 210 words are in the HTML the server sends, so a crawler that runs no JavaScript reads them.
-
✓
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
robots.txt lets every answer engine in: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User and the rest. GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot each get the home page from the edge, as a browser does.
Local SEO & entity signals 1 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.
-
✗
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.
-
✗
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.
-
!
Linked to its profiles
The page links Instagram, but there is no business node to carry a sameAs naming it, so the engines have to guess that they are the same business.
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
The phone is on the page, but not the town or the street address. Map search and the answer engines place a business 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.
-
!
Site name for Google
Only og:site_name (“Avant”) names the site. Google asks for WebSite schema on the home page to choose the name it shows above each result.
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.
-
!
Reviews on the page
The home page mentions “real reviews” but shows none. For a new business that is the right start; the first three go on the page as they come in.
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.
-
•
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.
-
✓
Service area stated by town
The service area is stated by town: Sumner County, Nashville and Middle Tennessee.
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 2.1 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.
-
✗
Image hygiene
3 images: 0 with dimensions, 0 in a modern format or through an image service, 0 lazy-loaded. 3 of 3 images have no width and height, so the page jumps as they load; none are WebP or AVIF, which are half the size of JPEG and PNG.
What we’d do: Every image has width and height, is served as WebP or AVIF at the size it is shown, and loads lazily below the fold.
-
✗
Fonts
9 font files (169 KB) from GoDaddy.
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.
-
✗
Readable and tappable on a phone
5 pieces of text are too faint to read against their background (“AVANT Audio Video & Lighting” 4.41:1, “View All 46 Reviews” 4:1, “Copyright © 2026 Avant - All Rights Reserved.” 3.94: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.
-
✗
Largest Contentful Paint (LCP)
Largest Contentful Paint 6.0 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.
-
!
Mobile PageSpeed score
Lighthouse mobile performance 67/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 86/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
39 scripts, 358 KB of JavaScript, from 2 third parties (GoDaddy and cdn.reamaze.com). GoDaddy 0.9 s held the phone's main thread while the page loaded. 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.
-
!
The hero image loads first
The hero image is not preloaded or marked high priority, so the browser finds it late.
What we’d do: The hero picture is the first thing the HTML asks for: sized, in a modern format, preloaded with fetchpriority=high and never lazy-loaded, so the first screen paints in about a second.
-
!
HTTP/2 or HTTP/3
Google's PageSpeed test loaded the page over http/1.1 — HTTP/1.1 loads one resource at a time per connection.
What we’d do: Every host we use speaks HTTP/2 and HTTP/3.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Render-blocking requests (about 1.3 s); Reduce unused JavaScript (about 0.5 s); Improve image delivery (about 0.5 s).
What we’d do: These are the first three things we would fix.
-
•
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.00 (lab). Google's thresholds: 0.1 good, 0.25 poor.
-
✓
Pinch-to-zoom allowed
Pinch-to-zoom is allowed.
-
✓
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 131 ms from our server.
-
✓
HTML weight
About 22 KB compressed (123 KB of HTML).
-
✓
Compression
Responses are compressed (gzip).
-
✓
One chat widget at most
No chat widget scripts on the page.
-
✓
Page weight
739 KB downloaded to show the home page on a phone.
-
✓
Static files cached
8 files served with a short or missing cache lifetime, 0 of them the site's own.
Conversion & lead generation 3 of 5 points
-
!
Contact form
No form on the home page; a contact or quote page is linked. Every extra tap loses a share of visitors.
What we’d do: Our home pages carry the quote form itself — name, phone, what they need — stored before it is emailed, so nothing is lost.
-
•
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.
-
✓
Tappable phone number
4 tel: links — the number dials from a phone.
-
✓
No CAPTCHA puzzle
No CAPTCHA puzzle on the page.
Read with the home page: service page avantavl.com/services
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.
We can fix every issue on avantavl.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.