A lawn care site whose estimate can't disagree with its own price list

A yard gets priced by looking at it

The person this site is for has a yard, a rough idea of what mowing costs, and a suspicion that the number will climb once someone pulls into the driveway. Size changes the job. A big corner lot and a townhouse patch take different hours, and homeowners know that. One flat rate for everyone would read as a trick.

So the services page gives example per-visit prices for three yard sizes, with a line beneath the list saying a real quote comes after someone has seen the property. The same page opens with a four-step outline of what happens. The visitor sends an address and a sentence, the operator looks the property over, a price arrives in writing, and work starts on a set day. A visitor can see the whole path to a price before sending anything.

One list of prices, one calculator

Below the price list sits a small calculator. It asks for yard size (small, medium or large), how often the crew comes (weekly or every other week), and two optional add-ons, hedge trimming and bed weeding. It opens on a medium yard, weekly, so a figure is on screen before the visitor touches anything. Weekly counts as four visits a month and every other week as two. On the opening setting, the page shows four visits at the example $55, which makes $220 a month. Mulch stays out of the monthly number because it's a one-time job, and a line under the total says so.

The calculator holds no prices of its own. Its script reads each number out of the example price list on the same page, so the two can't disagree, and if a price goes missing from the list the calculator stays hidden. It starts hidden for anyone whose script doesn't run, too, which leaves the full price list on the page. The form has nowhere to send anything, and the script makes no network request. The heading above the result is a polite live region, so a screen reader announces the new figure when a choice changes.

Where each service stops

Every service on that page follows one pattern: what's included, what's left out, and a short note with the reason where a reason helps. The left-out lines do the real work. Tree removal, stump grinding and anything that needs a climber or a lift go to a licensed arborist. New irrigation zones, pump work and backflow certification go to a licensed irrigation contractor. Hauling away clippings is quoted separately because it's a disposal cost.

The FAQ treats chemicals the same way. It says fertilizer and weed treatment are licensed work in Florida, that this business doesn't hold that license, and that it will point the visitor to someone who does.

A small patch, said out loud

The home page lists seven towns, from Gibsonton down to Wimauma, and gives a reason for the short list: a smaller area means shorter drives and visits that land on their day. The About page adds the customer's side of it. The same person comes each time, so they learn where the sprinkler heads are and which corner floods. The page also says the inbox is read Monday to Friday, 8 to 5, and makes no promise of an answer at night. The page's structured data lists the same seven towns and the same hours, so a search engine reads what a visitor reads.

Photos that say what they are

Every photo on the demo is licensed stock. The footer says so and credits the photographers and the three sources, and none of the images is this business's own work. The three gallery images have alt text that describes what's in them and no captions. They show a cut lawn edge, a trimmed bed and a palm-lined street, and nothing on the page claims them as the business's work. The structured data describes the business as a fictional demonstration brand. The demo is also set to noindex, so search engines are asked not to list a company that doesn't exist.

What a real company would change

A real company would change four things. The licensed-and-insured answer on the demo says there's nothing to license, because the business is fictional. On a real build it would carry the actual license number and insurer, or the question would come off the page. The stock gallery would give way to the owner's own before-and-after photos. The example prices would become the owner's real ones, kept in the same single list so the calculator keeps following them. And the lawn advice, such as how St. Augustine gets cut in summer, would be confirmed by the owner before it went live, because I design the site and I'm not the lawn professional.

The measured scores

PageSpeed Insights, mobile, October 22, 2026. I ran the live demo through Google's PageSpeed Insights three times on mobile and saved all three reports. The medians are 100 for Performance, 100 for Accessibility, 100 for Best Practices and 69 for SEO, and all three runs scored 100 on the first three. SEO reads 69 because the one check that fails is "Page is blocked from indexing": every concept site carries a noindex tag on purpose, so search engines don't list a business that isn't real.