Who are we, and why start with our own site?
Mesa Valley Marketing is run by a Grand Valley local who ran restaurants before building websites and automation. We've built websites, phone and voice AI answering, booking tools, customer portals, dashboards, iOS and Android apps, and lead follow up automation.
Mesa Valley Marketing is new, and we don't have a local client project to show yet. So the honest place to start is the one site we fully control: ours. Everything below is measured, dated and repeatable. You can run the same tests on our site, or yours, for free.
What did we build it with?
The short version, in plain words:
- Plain pages, no page builder. The site is a small set of prebuilt pages served from Cloudflare's network. There's no database behind a page view, which helps speed and leaves less to break or hack.
- A small code library. We use Preact, a lightweight library, so phones download less code.
- Real photos of the valley, credited. The big photo at the top of each page is one of Carol M. Highsmith's Colorado photographs from the Library of Congress, which she gave to the public domain. A few others come from Wikimedia Commons under their own licenses, credited in the footer. The illustrations are our own.
- One web address. Typing www sends you to the same site with a single permanent redirect, so Google sees one address, not two.
- A phone number you can tap. (970) 314-6088 sits in the header, the top of the page and the contact section.
- Text big enough to read. Nothing smaller than 12 pixels on a phone.
We use AI to map out tests and prototypes so we can try an idea quickly. Every page, number and line of code still gets checked by hand before it goes live.
How do Google and AI assistants read it?
We built for search engines and AI assistants at the same time. Here's what that means on our site.
- Structured data. Every main page carries a block of structured data that says, in a format machines read, that we're a professional service, what we do, our phone number and the towns we serve.
- An llms.txt file. At mesavalleymarketing.com/llms.txt there's a short plain text summary of who we are and what's on each page. It's a proposed convention, not a standard, and not every AI tool reads it. It costs nothing to have.
- Search Console and Bing. We verified the site with Google Search Console and Bing Webmaster Tools on October 5, 2026, and submitted our sitemap to both.
- Words as text. Our services and towns are written on the page, not baked into images.
When we ran Google's Rich Results Test on our home page on October 8, 2026, it reported "2 valid items detected": one local business and one organization. It also listed two non-critical issues, both optional fields we left out on purpose: "priceRange" and "address." We go to our customers, so we don't publish a street address.
What does it score?
We ran our home page through Google's PageSpeed Insights at 12:26 PM Mountain on October 8, 2026:
| Test | Speed | Accessibility | Best practices | SEO | Main content loaded (LCP) |
|---|---|---|---|---|---|
| Phone (Mobile tab) | 94 | 100 | 100 | 100 | 2.2 s |
| Computer (Desktop tab) | 99 | 100 | 100 | 100 | 0.6 s |
Google calls a load time (LCP) of 2.5 seconds or less "good" and over 4 seconds "poor". On the phone test, 2.2 seconds is in "good." It wasn't always: two days earlier, three Lighthouse runs on a simulated phone gave us 3.8, 3.9 and 2.9 seconds, so only one of three made "good." One run is a snapshot, and the number moves from run to run.
PageSpeed Insights didn't have real visitor data for our site yet. That part of the report said "No Data," which is normal for a new site with few visitors.
What changed along the way?
Earlier on October 5, our home page opened with short animated clips made from those same valley photos. They looked good. When we tested a saved copy of that version the same way on October 6, the page weighed 8.34 MB. Swapping the clips for still photos brought it to 0.62 MB, about 93% less to download.
Here's the part we didn't expect: the speed score barely moved. The old version scored 87, 87 and 73 across three runs; the new one 84, 85 and 94. The speed score is built from timing measures, like how soon the biggest thing on screen shows up, and none of them count the total megabytes. The clips arrived after those moments were measured. But a visitor on a phone plan still had to download 8 MB. A score isn't the whole story, which is why we also track page weight.
The same evening we found 47 bits of text on phones under 12 pixels and fixed them.