threestone.com scored 96/100 on the website scan.
Strong
threestone.com · Scanned 2026-11-08
Unchanged from 2026-10-10
93 passed4 warnings0 failed
- Technical SEO & indexability10/10 of 10 points
- On-page SEO & content24/25 of 25 points
- AI search / AEO / GEO readiness35/35 of 35 points
- Local SEO & entity signals5/5 of 5 points
- Speed, scripts & mobile18/20 of 20 points
- Conversion & lead generation4/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.
Nothing failed. What to tighten
-
!
Scripts and third parties +2 points
10 scripts, 788 KB of JavaScript, from 5 third parties (static.cloudflareinsights.com, Google Tag Manager, Facebook and reCAPTCHA and more). Google Tag Manager 0.3 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.
-
!
A menu a thumb can use +1 point
16 links in the header and menu.
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.
-
!
A lead form that fits a phone +1 point
The lead form asks 11 fields. Every field costs a share of the people who start it.
What we’d do: Name, phone, what they need: three to five fields, each labeled, the phone field a tel input so the keypad comes up, and one tap to send.
-
!
Page weight +1 point
1.1 MB downloaded to show the home page on a phone. On a cellular connection that is seconds of waiting, and data the visitor pays for.
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.
Every check, by category (103 checks)
Technical SEO & indexability 10 of 10 points
-
•
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
25 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://threestone.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.
-
✓
Security headers
All four baseline security headers are set.
-
✓
Sitemap
Sitemap at https://threestone.com/sitemap.xml — 72 URLs.
-
✓
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://threestone.com/.
-
✓
Internal links resolve
All 31 internal links read (30 on the home page, 1 in llms.txt) answer.
-
✓
Language declared
<html lang="en">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
robots.txt
robots.txt is served (8 groups, 1 sitemap line, the private paths repeated in each crawler's own group).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://threestone.com/sitemap.xml.
-
✓
www and apex agree
www.threestone.com redirects (301) to threestone.com.
-
✓
Sitemap lists the live URLs
The sitemap's 72 URLs are all on https://threestone.com, and the pages read from it answer directly and are open to indexing.
-
✓
Lighthouse SEO score
Lighthouse SEO 100/100.
-
✓
Lighthouse best practices
Lighthouse best practices 100/100.
-
✓
Sitemap dates
72 pages with lastmod dates, from 2026-11-04 to 2026-11-06.
On-page SEO & content 24 of 25 points
-
!
A menu a thumb can use
16 links in the header and menu.
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.
-
•
Pages read
Read with the home page: service page https://threestone.com/commercial-painting-coatings/.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
Page title
“Franklin TN Roofing Company | Three Stone Roofing” — 49 characters, inside the 30–60 Google shows in full.
-
✓
Meta description
142 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.
-
✓
Titles across the site
Each page read has its own title of 30–60 characters.
-
✓
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.
-
✓
No stock or AI-marked pictures
None of the 30 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.
-
✓
Not a stock template
No builder or stock theme shows in the page: no template credit, demo pictures or sample text.
-
✓
Single H1
One H1: “Built to a Higher Standard.”.
-
✓
Image alt text
All 36 images have an alt attribute.
-
✓
Readable content in the HTML
1,826 words of readable text in the HTML.
-
✓
Share image loads
The share image loads (image/jpeg, 253 KB).
-
✓
Descriptions across the site
Each page read has its own description of 120–160 characters.
-
✓
Pages that repeat each other
The pages read share few sentences: at most 3 of 52 (6%) between the service and home pages.
-
✓
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.
-
✓
Pictures named and described for what they show
28 of the 28 pictures on the pages read are named and described for what they show.
-
✓
A page for each service
10 service pages in the sitemap (/commercial-painting-coatings/, /commercial-roofing/, /painting/, …).
-
✓
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.
-
✓
About and privacy pages
The home page links an About page (/about/) and a privacy policy (/privacy/).
-
✓
Titles lead with the subject
The inner pages' titles lead with their subject, not the business name.
-
✓
Service pages link each other
The service page read links 2 other service pages in its copy (/commercial-roofing/, /concrete-coatings/).
AI search / AEO / GEO readiness 35 of 35 points
-
•
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.
-
✓
FAQPage schema
FAQPage schema is present.
-
✓
FAQ questions visible on the page
All 8 questions in the FAQ schema are on the page, with the answers it shows.
-
✓
llms.txt
llms.txt is published (9 KB), headed with the name and linking 21 pages of the site — a plain statement of the business for the AI engines to read.
-
✓
Questions answered on the page
14 questions asked and answered on the pages read (8 on the home page, 6 on the service page) — the shape an AI answer is lifted from.
-
✓
FAQs on the inner pages
The inner page read carries its own FAQ with schema (6 questions on the service page), none repeated from another page.
-
✓
Specifics an engine can cite
The service page (/commercial-painting-coatings/): 923 words, 15 numbers, 8 names (HOA, Penntek, Installer, Fairview, …) — specifics only this business could publish, the kind an answer engine quotes.
-
✓
Schema on the inner pages
The inner page read carries its own schema: the business and a BreadcrumbList, with a Service on the service page.
-
✓
Readable without JavaScript
The page's 1,826 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
25 schema types: RoofingContractor, HomeAndConstructionBusiness, LocalBusiness, ImageObject, ContactPoint, PostalAddress, GeoCoordinates, OpeningHoursSpecification, ….
-
✓
Extractable structure
Structure an engine can lift: 6 H2s, 5 H3s, 61 list items.
-
✓
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.
-
✓
The first paragraph answers
The first paragraph under the H1 answers in 56 words on the home page and 34 words on the service page.
-
✓
Speakable specification
A speakable specification is present.
Local SEO & entity signals 5 of 5 points
-
✓
Business entity schema
RoofingContractor / HomeAndConstructionBusiness / LocalBusiness schema names the business.
-
✓
Service area stated by town
The service area is stated by town: Franklin, TN, Brentwood, TN, Nashville, TN and Clarksville, TN and 19 more, in the schema too.
-
✓
Business schema completeness
The business node carries name, url, telephone, address, logo or image, areaServed, openingHours.
-
✓
Linked to its profiles
The business node's sameAs names Facebook, BBB, Yelp and Nextdoor — the links the engines use to know this site and those profiles are one business.
-
✓
Address and phone on the page
The phone ((615) 434-3333) and where the business is (6100 Tower Circle) are on the page as text, and the phone matches the schema's.
-
✓
Site name for Google
WebSite schema names the site “Three Stone” — the name Google shows above each result.
-
✓
The trade's own schema type
RoofingContractor / HomeAndConstructionBusiness: schema.org's own type for what the business does.
-
✓
A named person
A named person in the schema: Todd Massey.
-
✓
Trust signals
Trust language present: licensed, insured, warranty, bbb, accredited.
-
✓
Reviews on the page
Reviews on the home page: a rating and count in the schema, reviews quoted, and a link to where they live.
-
✓
Hours shown and in schema
The hours are on the page and in the business schema.
Speed, scripts & mobile 18 of 20 points
-
!
Scripts and third parties
10 scripts, 788 KB of JavaScript, from 5 third parties (static.cloudflareinsights.com, Google Tag Manager, Facebook and reCAPTCHA and more). Google Tag Manager 0.3 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.
-
!
Page weight
1.1 MB downloaded to show the home page on a phone. On a cellular connection that is seconds of waiting, and data the visitor pays for.
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.
-
•
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.
-
✓
Readable and tappable on a phone
Every piece of text Google's test measured on a phone clears WCAG AA contrast, and the buttons and links are big enough, and far enough apart, to tap.
-
✓
Mobile PageSpeed score
Lighthouse mobile performance 92/100. Google's own bands: 90 and up is good, 50–89 needs improvement.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 100/100.
-
✓
Nothing blocks the first paint
1 file loads before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.3 s of the first paint on waiting for it.
-
✓
Image hygiene
36 images: 36 with dimensions, 36 in a modern format or through an image service, 28 lazy-loaded.
-
✓
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.
-
✓
Fonts
2 font files (98 KB) from threestone.com.
-
✓
The hero image loads first
The hero image is asked for early and not lazy-loaded (<img srcset="/assets/img/work/hero-estate-640.webp 640w, /assets/img/w).
-
✓
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 212 ms from our server.
-
✓
HTML weight
About 17 KB compressed (72 KB of HTML).
-
✓
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/2 — Google's PageSpeed test loaded the page over it (this scan cannot read the protocol itself).
-
✓
One chat widget at most
No chat widget scripts on the page.
-
✓
Largest Contentful Paint (LCP)
Largest Contentful Paint 2.5 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
-
✓
Static files cached
5 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: Improve image delivery (about 0.3 s); Render-blocking requests (about 0.3 s); Reduce unused CSS (about 0.1 s).
Conversion & lead generation 4 of 5 points
-
!
A lead form that fits a phone
The lead form asks 11 fields. Every field costs a share of the people who start it.
What we’d do: Name, phone, what they need: three to five fields, each labeled, the phone field a tel input so the keypad comes up, and one tap to send.
-
•
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.
-
✓
Contact form
1 form on the home page.
-
✓
Call to action in the first screen
A phone link, a form or a quote button appears in the top of the page.
-
✓
Lead form wiring
The form posts to /api/lead, guarded by a honeypot.
-
✓
Analytics installed
Measured by Google Tag Manager, Google Analytics, Meta pixel.
-
✓
Tappable phone number
7 tel: links — the number dials from a phone.
-
✓
No CAPTCHA puzzle
No CAPTCHA puzzle on the page.
Read with the home page: service page threestone.com/commercial-painting-coatings/
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 threestone.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.