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

mrenclosuresunrooms.com scored 31/100 on the website scan.

Major issues

mrenclosuresunrooms.com · Scanned 2026-10-24

53 passed20 warnings20 failed

  • Technical SEO & indexability6 of 10 points
  • On-page SEO & content9 of 25 points
  • AI search / AEO / GEO readiness5 of 35 points
  • Local SEO & entity signals3 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

  • ✗

    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 post 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 (1 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 +3 points

    The post page (/top-roofing-materials-for-every-home-project/) gives no number — no price, timeline, size or count — and names nothing beyond the business and its town. A competitor could publish it unchanged, and the answer engines quote pages with specifics they can check.

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

  • !

    Structured data Google accepts

    An article's author or publisher written as a bare {"@id"} with no type beside it (the post page).

    What we’d do: Structured data generated from the page's own content and checked against Google's rules before every deploy: a rating only on the business and only where the page shows it, every reference typed, no empty values.

  • !

    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.

  • !

    Lighthouse SEO score

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

  • •

    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.

  • ✓

    Canonical URL

    Canonical is https://mrenclosuresunrooms.com/.

  • ✓

    Mixed content

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

  • ✓

    Sitemap

    Sitemap at https://mrenclosuresunrooms.com/sitemap_index.xml — an index of 7 sitemaps.

  • ✓

    HTTP redirects to HTTPS

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

  • ✓

    Internal links resolve

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

  • ✓

    Language declared

    <html lang="en-US">.

  • ✓

    Redirect chain

    The URL answers directly, with no redirect.

  • ✓

    robots.txt

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

  • ✓

    Sitemap named in robots.txt

    robots.txt names the sitemap: https://mrenclosuresunrooms.com/sitemap_index.xml.

  • ✓

    www and apex agree

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

  • ✓

    Sitemap lists the live URLs

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

  • ✓

    Lighthouse best practices

    Lighthouse best practices 96/100.

  • ✓

    Sitemap dates

    4 pages with lastmod dates, from 2025-03-11 to 2025-03-11.

On-page SEO & content 9 of 25 points

  • ✗

    Page title

    “Home | Mr. Enclosure Sunrooms - Mr Enclosure | Sunrooms | Enclosed Patios | Screen Rooms P…” is 541 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 post page's title is 555 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 post page has no description.

    What we’d do: Every page gets its own 120–160 character description, checked in the build.

  • ✗

    No stock phrases

    The home page: “whether you’re looking”, “we take pride in” and 4 brochure phrases (“unparalleled”, “transform your”, “you can trust”, …). This is what copy written without facts sounds like: nothing in it only this business could say.

    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.

  • !

    Canonical and share card on every page

    The post page (/top-roofing-materials-for-every-home-project/) has 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.

  • !

    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

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

  • •

    Title and H1 differ

    Skipped — no title or no H1 to compare.

  • •

    Service pages link each other

    Skipped — no service page read.

  • •

    Pages read

    Read with the home page: post page https://mrenclosuresunrooms.com/top-roofing-materials-for-every-home-project/.

  • ✓

    Social share cards

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

  • ✓

    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 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 4 files opened.

  • ✓

    Not a stock template

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

  • ✓

    Image alt text

    All 7 images have an alt attribute.

  • ✓

    Readable content in the HTML

    2,112 words of readable text in the HTML.

  • ✓

    Share image loads

    The share image loads (image/jpeg, 164 KB).

  • ✓

    Pages that repeat each other

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

  • ✓

    Pictures named and described for what they show

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

  • ✓

    A page for each service

    3 service pages in the sitemap (/top-roofing-materials-for-every-home-project/, /indoor-swim-spa/, /franklin-outdoor-living-at-its-finest/).

  • ✓

    Favicon

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

  • ✓

    Titles lead with the subject

    The inner pages' titles lead with their subject, not the business name.

  • ✓

    Article schema on the post

    Article schema with an author on the post.

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

  • ✗

    Specifics an engine can cite

    The post page (/top-roofing-materials-for-every-home-project/) gives no number — no price, timeline, size or count — and names nothing beyond the business and its town. A competitor could publish it unchanged, and the answer engines quote pages with specifics they can check.

    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.

  • ✗

    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.

  • !

    llms.txt

    llms.txt is published (1 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.

  • !

    Schema on the inner pages

    The post page (/top-roofing-materials-for-every-home-project/) has nothing naming the business.

    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.

  • !

    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.

  • •

    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 2,112 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

    13 schema types: WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, ….

  • ✓

    Freshness dates in schema

    Newest date in the schema: 2026-10-17.

  • ✓

    Extractable structure

    Structure an engine can lift: 20 H2s, 23 H3s, 48 list items.

Local SEO & entity signals 3 of 5 points

  • ✗

    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.

  • ✗

    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

    Two towns are named (Areas Sunrooms and Screen Rooms). A service business is found town by town; three or more, on the page and in areaServed, is the floor.

    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.

  • !

    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 / HomeAndConstructionBusiness schema names the business.

  • ✓

    Business schema completeness

    The business node carries name, url, telephone, address, logo or image, areaServed.

  • ✓

    Address and phone on the page

    The phone ((615) 736-9626) and where the business is (Nashville, TN) are on the page as text, and the phone matches the schema's.

  • ✓

    Site name for Google

    WebSite schema names the site “Mr Enclosure | Sunrooms | Enclosed Patios | Screen Rooms PHP” — the name Google shows above each result.

  • ✓

    The trade's own schema type

    HomeAndConstructionBusiness: schema.org's own type for what the business does.

  • ✓

    Trust signals

    Trust language present: warranty, years in business, locally owned, 63 years.

Speed, scripts & mobile 6 of 20 points

  • ✗

    Nothing blocks the first paint

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

  • ✗

    Fonts

    10 font files (749 KB) from cyan-kudu-665011.hostingersite.com, mrenclosuresunrooms.com and Google Fonts. 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.

  • ✗

    Time to first byte

    First byte took 3.1 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 15.5 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

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

  • ✗

    Static files cached

    130 files served with a short or missing cache lifetime, 130 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 60/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 89/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.

  • !

    Image hygiene

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

  • !

    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

    4 pieces of text are too faint to read against their background (“615-736-9626” 3.44:1, “Contact Us” 3.44:1, “SERVICE AREA” 3.66:1); WCAG asks 4.5:1 for text that size. 9 buttons or links are too small or too close to others to tap reliably (“Go to slide 1”, “Go to slide 2”, “Go to slide 3”).

    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.

  • !

    What would speed it up most

    PageSpeed's biggest savings on this page: Use efficient cache lifetimes (about 11.9 s); Render-blocking requests (about 6.0 s); Improve image delivery (about 1.8 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.

  • ✓

    Scripts and third parties

    40 scripts, 286 KB of JavaScript, from no third party.

  • ✓

    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.

  • ✓

    HTML weight

    About 27 KB compressed (176 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 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.

  • •

    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.

  • ✓

    Call to action in the first screen

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

  • ✓

    Tappable phone number

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

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

  • ✓

    Chat or text option

    A chat widget, an assistant or a text link is present — a way to ask without calling.

Read with the home page: post page mrenclosuresunrooms.com/top-roofing-materials-for-every-home-project/

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