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

designs-of-nature.com scored 25/100 on the website scan.

Major issues

designs-of-nature.com · Scanned 2026-10-24

40 passed23 warnings21 failed

  • Technical SEO & indexability6 of 10 points
  • On-page SEO & content3 of 25 points
  • AI search / AEO / GEO readiness6 of 35 points
  • Local SEO & entity signals1 of 5 points
  • Speed, scripts & mobile8 of 20 points
  • Conversion & lead generation1 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 (/hello-world/) 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.

  • ✗

    Scripts and third parties +2 points

    24 scripts, 995 KB of JavaScript, from 3 third parties (YouTube, Google Ads and www.google.com). YouTube 0.3 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.

Every check, by category (103 checks)

Technical SEO & indexability 6 of 10 points

  • ✗

    Security headers

    Missing 4 of the four baseline security headers: Content-Security-Policy, X-Content-Type-Options, 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.

  • !

    HSTS header

    No Strict-Transport-Security header. Browsers still use HTTPS, but a first visit typed without it can be intercepted.

    What we’d do: HSTS with a one-year max-age on every response.

  • !

    Missing pages return 404

    A made-up URL redirects (301) instead of returning 404. Better than a soft 404, but a redirect to the home page still teaches Google the site has no missing pages.

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

  • !

    robots.txt

    robots.txt is served, but OAI-SearchBot, ChatGPT-User, GPTBot and PerplexityBot and others have groups of their own that don't repeat the * group's Disallow: /wp-admin/. A crawler named in its own group follows only that group, so they may read what the site keeps from every other crawler.

    What we’d do: Every group in robots.txt repeats the private paths, so a crawler named on its own is kept out of them too.

  • !

    Lighthouse best practices

    Lighthouse best practices 77/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.

  • ✓

    Indexable by search engines

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

  • ✓

    Canonical URL

    Canonical is https://designs-of-nature.com/.

  • ✓

    Mixed content

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

  • ✓

    Sitemap

    Sitemap at https://designs-of-nature.com/wp-sitemap.xml — an index of 3 sitemaps.

  • ✓

    HTTP redirects to HTTPS

    http:// redirects (301) to https://designs-of-nature.com/.

  • ✓

    Internal links resolve

    All 9 internal links read (8 on the home page, 1 in llms.txt) answer.

  • ✓

    Language declared

    <html lang="en-US">.

  • ✓

    Redirect chain

    The URL answers directly, with no redirect.

  • ✓

    Sitemap named in robots.txt

    robots.txt names the sitemap: https://designs-of-nature.com/wp-sitemap.xml.

  • ✓

    www and apex agree

    www.designs-of-nature.com redirects (301) to designs-of-nature.com.

  • ✓

    Sitemap lists the live URLs

    The sitemap's 1 URL is on https://designs-of-nature.com, and the pages read from it answer directly and are open to indexing.

  • ✓

    Lighthouse SEO score

    Lighthouse SEO 92/100.

  • ✓

    Sitemap dates

    1 page with lastmod dates.

On-page SEO & content 3 of 25 points

  • ✗

    Page title

    “DESIGNS of NATURE Custom Water Features & Hardscaping – Premium Outdoor Architecture & Lux…” is 105 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.

  • ✗

    Social share cards

    No Open Graph or Twitter card tags. A share in Messages, LinkedIn, Facebook or Slack shows a bare link.

    What we’d do: Every page carries og:title, og:image, twitter:card and twitter:image, with a real picture.

  • ✗

    Titles across the site

    the service page's title is 68 characters.

    What we’d do: Every page gets its own 30–60 character title, checked in the build.

  • ✗

    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.

  • ✗

    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.

  • ✗

    No placeholder or template text

    The service page shows WordPress's sample content. Left on a live page, it tells every visitor nobody finished the site.

    What we’d do: Nothing ships with a placeholder in it: every value comes from the business's own facts, and the build fails a page that still carries one.

  • !

    Canonical and share card on every page

    The service page (/hello-world/) has no share image, no Twitter card and no H1.

    What we’d do: Every page names itself as its canonical, carries its own og:image and twitter:image, and opens with one H1 — checked on every page before the site ships.

  • !

    A page for each service

    Only 1 service page in the sitemap (/hello-world/). A service with no page of its own has nothing to rank for it.

    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

    The home page links an About page (/about-us/) 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.

  • !

    A menu a thumb can use

    The service page read (/hello-world/) is not linked from the home page.

    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.

  • !

    No stock phrases

    The home page: “we take pride in”.

    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.

  • •

    Share image loads

    Skipped — no og:image to fetch.

  • •

    Pages that repeat each other

    Not enough copy on the pages read to compare.

  • •

    Title and H1 differ

    Skipped — no title or no H1 to compare.

  • •

    Titles lead with the subject

    No business name in the schema to compare the titles against.

  • •

    Service pages link each other

    Skipped — fewer than three service pages to link between.

  • •

    Pages read

    Read with the home page: service page https://designs-of-nature.com/hello-world/.

  • •

    Article schema on the post

    No post found in the sitemap to check.

  • ✓

    No stock or AI-marked pictures

    None of the 5 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 3 files opened.

  • ✓

    Not a stock template

    WordPress, with a theme of its own (hello-biz) and Elementor; nothing of a stock template shows — no theme credit, demo pictures or sample text.

  • ✓

    Image alt text

    All 10 images have an alt attribute.

  • ✓

    Readable content in the HTML

    756 words of readable text in the HTML.

  • ✓

    Pictures named and described for what they show

    3 of the 3 pictures on the pages read are named and described for what they show.

  • ✓

    Favicon

    A favicon is linked — it shows in the tab and beside the site in Google's results.

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 (/hello-world/) 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 has no H1 to answer under; the service 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.

  • !

    Specifics an engine can cite

    The service page (/hello-world/): 57 words, 3 numbers, 1 name (WordPress) — 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.

  • !

    AI crawlers allowed

    robots.txt blocks CCBot (Common Crawl (training data for many models)). A defensible choice for training data, but every answer engine is allowed. GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot each get the home page from the edge, as a browser does.

    What we’d do: We block nothing an answer engine reads.

  • •

    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 2 pages of the site — a plain statement of the business for the AI engines to read.

  • ✓

    Readable without JavaScript

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

  • ✓

    Extractable structure

    Structure an engine can lift: 36 H2s, 7 H3s, 33 list items.

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.

  • ✗

    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.

  • !

    Service area stated by town

    The page says it serves an area (“we serve every client today”) but names no town.

    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

    The page links Facebook, 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.

  • !

    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.

  • !

    Reviews on the page

    The home page mentions “Testimonials” 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.

  • ✓

    Address and phone on the page

    The phone ((870) 790-0061) and where the business is (Cookeville, Tennessee) are on the page as text.

  • ✓

    Trust signals

    Trust language present: family-owned, since <year>, 15 years.

Speed, scripts & mobile 8 of 20 points

  • ✗

    Scripts and third parties

    24 scripts, 995 KB of JavaScript, from 3 third parties (YouTube, Google Ads and www.google.com). YouTube 0.3 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.

  • ✗

    Nothing blocks the first paint

    25 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 2.0 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.

  • ✗

    Time to first byte

    First byte took 2.0 s from our server — the page cannot be fast if the server is slow to start.

    What we’d do: Static pages served from an edge network answer in well under half a second.

  • ✗

    Largest Contentful Paint (LCP)

    Largest Contentful Paint 12.1 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.

  • ✗

    Static files cached

    41 files served with a short or missing cache lifetime, 40 of them the site's own. Every visit downloads the site again.

    What we’d do: Every static file — styles, scripts, fonts, pictures — is served with a year-long cache header and a fingerprinted name, so a return visit downloads only the HTML.

  • !

    Mobile PageSpeed score

    Lighthouse mobile performance 56/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.

  • !

    Cumulative Layout Shift (CLS)

    Cumulative Layout Shift 0.19 (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.

  • !

    Fonts

    3 font files (97 KB) from Google Fonts. 1 face 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.

  • !

    Page weight

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

  • !

    What would speed it up most

    PageSpeed's biggest savings on this page: Reduce unused JavaScript (about 2.6 s); Use efficient cache lifetimes (about 2.3 s); Render-blocking requests (about 2.0 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.

  • ✓

    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.

  • ✓

    Lighthouse accessibility score

    Lighthouse accessibility 100/100.

  • ✓

    Image hygiene

    10 images: 10 with dimensions, 3 in a modern format or through an image service, 2 lazy-loaded.

  • ✓

    No hero slider or autoplay video

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

  • ✓

    The hero image loads first

    The largest thing on the first screen is text or a styled block (<h2 class="elementor-heading-title elementor-size-default">), which paints as soon as the HTML arrives.

  • ✓

    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.

  • ✓

    HTML weight

    About 20 KB compressed (116 KB of HTML).

  • ✓

    Compression

    Responses are compressed (gzip).

  • ✓

    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.

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

  • !

    Call to action in the first screen

    Nothing in the top of the page asks for the call — no number, form or quote button before the visitor scrolls.

    What we’d do: Our heroes carry the number and the quote button; most visitors decide there.

  • !

    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.

  • •

    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.

  • ✓

    Tappable phone number

    2 tel: links — the number dials from a phone.

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

Read with the home page: service page designs-of-nature.com/hello-world/

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 designs-of-nature.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