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

www.speakeasyaesthetics.com scored 36/100 on the website scan.

Major issues

speakeasyaesthetics.com · Scanned 2026-11-19

53 passed21 warnings18 failed

  • Technical SEO & indexability8 of 10 points
  • On-page SEO & content12 of 25 points
  • AI search / AEO / GEO readiness5 of 35 points
  • Local SEO & entity signals2 of 5 points
  • Speed, scripts & mobile7 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

  • ✗

    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.

  • !

    llms.txt +3 points

    llms.txt is published (3 KB) but links only 2 pages of the site. The format is a heading with the name, a summary, then the pages worth reading, each linked, so an engine knows where to look.

    What we’d do: Every site ships an llms.txt written from its facts — who, what, where, the proof — with a link to every service, area and post page, rewritten when the pages change.

  • ✗

    Meta description +2 points

    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.

Every check, by category (103 checks)

Technical SEO & indexability 8 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.

  • ✗

    Lighthouse best practices

    Lighthouse best practices 58/100.

    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.

  • ✓

    Indexable by search engines

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

  • ✓

    Structured data Google accepts

    7 schema types on the 2 pages read, and nothing Google would reject: ratings only where they belong and shown on the page, every reference typed, every value filled.

  • ✓

    Canonical URL

    Canonical is https://www.speakeasyaesthetics.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://www.speakeasyaesthetics.com/sitemap.xml — an index of 2 sitemaps.

  • ✓

    Missing pages return 404

    A made-up URL returns 404, so Google never indexes ghost pages.

  • ✓

    HTTP redirects to HTTPS

    http:// redirects (301) to https://speakeasyaesthetics.com/.

  • ✓

    Internal links resolve

    All 30 internal links read on the home page answer.

  • ✓

    Language declared

    <html lang="en">.

  • ✓

    Redirect chain

    One redirect (301) to https://www.speakeasyaesthetics.com/.

  • ✓

    robots.txt

    robots.txt is served (5 groups, 1 sitemap line).

  • ✓

    Sitemap named in robots.txt

    robots.txt names the sitemap: https://www.speakeasyaesthetics.com/sitemap.xml.

  • ✓

    www and apex agree

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

  • ✓

    Sitemap lists the live URLs

    The sitemap's 4 URLs are all on https://www.speakeasyaesthetics.com, and the pages read from it answer directly and are open to indexing.

  • ✓

    Lighthouse SEO score

    Lighthouse SEO 92/100.

  • ✓

    Sitemap dates

    4 pages with lastmod dates, from 2021-08-08 to 2021-10-06.

On-page SEO & content 12 of 25 points

  • ✗

    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.

  • ✗

    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.

  • ✗

    Service pages link each other

    The service page read links none of the other 3 service pages in its copy. Each stands alone, so nothing moves between them but the menu.

    What we’d do: Every service page names the related services in its own copy — the repair page links the replacement page, the inspection page the repair — so a visitor and a crawler move between them without the menu.

  • ✗

    A menu a thumb can use

    43 links in the header and menu; the service page read (/product-page/scented-candle) is not linked from the home page. A phone shows about seven menu items before the visitor has to scroll the menu itself.

    What we’d do: A menu of five to eight items a thumb can hit — the services, the area, about, contact — with the number beside it, and every service page one tap from the home page.

  • !

    Page title

    “Home | Speakeasyaesthetics” is only 26 characters. There is room for the service and the place, which is what people search.

    What we’d do: We write titles of 30–60 characters with the service, the place and the name.

  • !

    Pictures named and described for what they show

    Of the 14 pictures on the pages read, 5 with a camera's, a template's or an upload's name (11062b_f4e3e7f537ff4762a1914aa14e3e36b9~mv2.png, 11062b_603340b7bcb14e7785c7b65b233cd9f9~mv2.png, f0600e_61de694d131141d5b592800a4a94d2b9~mv2.jpg, …) and 11 with alt text that describes nothing (“header2.jpg”, the file's own name; “speakeasy.jpg”, the file's own name). Google's image guidelines ask for file names and alt text that say what the picture shows.

    What we’d do: Every picture is named for what it shows, in the business's own words (franklin-standing-seam-metal-roof.webp, never IMG_4411.jpg), and its alt text says what is in it — the job, the place, the material — rather than a keyword.

  • !

    No stock phrases

    The home page: “tailored to your”.

    What we’d do: Every sentence is written from the business's own facts — what the crew found, what it cost, what the owner says — so none of it is a line any competitor could use.

  • !

    Not a stock template

    Built with Wix, from templates thousands of businesses share. Nothing is left over from the template, but the layout says “Wix” 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.

  • !

    About and privacy pages

    The home page links a privacy policy but no About page. Google's quality raters are told to find out who is behind a site; an About page with the owner's name, the crew and the years is where a business answers that.

    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.

  • •

    Pages read

    Read with the home page: service page https://www.speakeasyaesthetics.com/product-page/scented-candle.

  • •

    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.

  • ✓

    Titles across the site

    Each page read has its own title of 30–60 characters.

  • ✓

    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.

  • ✓

    No stock or AI-marked pictures

    None of the 16 pictures on the pages read is marked as bought stock or AI-made — not by where it is served from, its name, its alt text, or the credits inside the 6 files opened.

  • ✓

    Single H1

    One H1: “Where Confidence Meets Care”.

  • ✓

    Image alt text

    All 15 images have an alt attribute.

  • ✓

    Readable content in the HTML

    450 words of readable text in the HTML.

  • ✓

    Share image loads

    The share image loads (image/png, 13 KB).

  • ✓

    Pages that repeat each other

    The pages read share no sentences beyond the header, footer and calls to action.

  • ✓

    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.

  • ✓

    A page for each service

    4 service pages in the sitemap (/product-page/scented-candle, /product-page/hands-cream, /product-page/massage-oil, …).

  • ✓

    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.

AI search / AEO / GEO readiness 5 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.

  • ✗

    The first paragraph answers

    The home page's headline is followed by buttons and pictures, not a sentence; the service page's headline is followed by buttons and pictures, not a sentence. 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.

  • !

    llms.txt

    llms.txt is published (3 KB) but links only 2 pages of the site. The format is a heading with the name, a summary, then the pages worth reading, each linked, so an engine knows where to look.

    What we’d do: Every site ships an llms.txt written from its facts — who, what, where, the proof — with a link to every service, area and post page, rewritten when the pages change.

  • !

    Specifics an engine can cite

    The service page (/product-page/scented-candle): 181 words, 2 numbers, 1 name (Return) — 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.

  • !

    Schema on the inner pages

    The service page (/product-page/scented-candle) has no BreadcrumbList.

    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.

  • !

    Extractable structure

    Little for an engine to lift: 2 H2s, 2 H3s, 109 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.

  • ✓

    Readable without JavaScript

    The page's 450 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.

  • ✓

    JSON-LD present and valid

    3 schema types: LocalBusiness, PostalAddress, WebSite.

  • ✓

    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 2 of 5 points

  • ✗

    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.

  • ✗

    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.

  • !

    Business schema completeness

    The business node has name, url, telephone, address, logo or image but not areaServed, openingHours.

    What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.

  • !

    Linked to its profiles

    The page links Facebook and Instagram, but the business node has no sameAs naming them, 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.

  • !

    The trade's own schema type

    LocalBusiness — a generic type. schema.org has one for nearly every trade, and the engines file a business by it.

    What we’d do: The business node uses schema.org's own type for the trade — RoofingContractor, Plumber, HVACBusiness, Electrician, HousePainter, GeneralContractor, MovingCompany, Locksmith and the rest under HomeAndConstructionBusiness and LocalBusiness — so the engines file it under what it does, not only that it exists.

  • !

    Reviews on the page

    Reviews are quoted but there is no rating or count beside them, and nothing says how many there are.

    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.

  • •

    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.

  • ✓

    Business entity schema

    LocalBusiness schema names the business.

  • ✓

    Address and phone on the page

    The phone ((615) 473-1931) and where the business is (804 N Thompson Lane Suite) are on the page as text, and the phone matches the schema's.

  • ✓

    Site name for Google

    WebSite schema names the site “Speakeasyaesthetics” — the name Google shows above each result.

Speed, scripts & mobile 7 of 20 points

  • ✗

    Scripts and third parties

    129 scripts, 1601 KB of JavaScript, from 8 third parties (browser.sentry-cdn.com, Wix, cdn-scripts.docovia.com and speakeasyaesthetics.docovia.com and more). Wix 0.8 s held the phone's main thread while the page loaded. A phone downloads, parses and runs all of it before the page settles.

    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.

  • ✗

    Cumulative Layout Shift (CLS)

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

    What we’d do: Every image and embed has its size in the HTML and fonts load with size-adjust, so nothing moves as the page loads.

  • ✗

    HTML weight

    About 173 KB compressed (859 KB of HTML) — every visit downloads this before anything is drawn.

    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 6.4 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.

  • ✗

    Page weight

    3.2 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 44/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.

  • !

    Image hygiene

    15 images: 15 with dimensions, 0 in a modern format or through an image service, 9 lazy-loaded. 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

    7 font files (204 KB) from Wix and Adobe Fonts or Font Awesome. 3 faces without font-display, so the words wait for the file.

    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.

  • !

    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.

  • !

    Readable and tappable on a phone

    3 buttons or links are too small or too close to others to tap reliably (“Section1SlideShowItem3MediaImage1RuleNoFaceImage”, “Copy of Section1SlideShowItem3MediaImage1RuleNoFaceImage”, “Copy of Copy of Section1SlideShowItem3MediaImage1RuleNoFaceImage”).

    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.

  • •

    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.

  • ✓

    Lighthouse accessibility score

    Lighthouse accessibility 92/100.

  • ✓

    Nothing blocks the first paint

    Nothing blocks the first paint: the page is drawn as soon as the HTML arrives.

  • ✓

    No hero slider or autoplay video

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

  • ✓

    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 138 ms from our server.

  • ✓

    Compression

    Responses are compressed (br).

  • ✓

    HTTP/2 or HTTP/3

    HTTP/2 — Google's PageSpeed test loaded the page over it (this scan cannot read the protocol itself).

  • ✓

    One chat widget at most

    One chat widget (a chat widget).

  • ✓

    Static files cached

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

  • ✓

    What would speed it up most

    Nothing large left to fix. PageSpeed's remaining suggestions: Avoid multiple page redirects (about 0.8 s); Document request latency (about 0.1 s).

Conversion & lead generation 2 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.

  • !

    Analytics installed

    No analytics tag found — nothing counts the visits, the calls or the forms, so nothing can be improved on evidence.

    What we’d do: First-party traffic logging on every site, and GA4 as the second source.

  • !

    Tappable phone number

    A phone number is shown but is not a tel: link — on a phone it has to be copied, not tapped.

    What we’d do: Every number on our sites is a tel: link, and every tap is counted as a lead.

  • •

    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.

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

Read with the home page: service page www.speakeasyaesthetics.com/product-page/scented-candle

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 www.speakeasyaesthetics.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