www.simpleturfllc.com scored 48/100 on the website scan.

Lighthouse best practices

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

Single H1

12 H1 headings. One is the convention search engines and screen readers expect.

What we’d do: One H1 per page; the rest become H2s.

No stock phrases

The home page: “look no further”.

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.

Pictures named and described for what they show

Of the 45 pictures on the pages read, 42 with a camera's, a template's or an upload's name (ab043e_0e6e1609a08c483ca20f5aee26d2ae2b~mv2.jpeg, ab043e_36cc2e64ebc94f0cb7f41b6627fea9f6~mv2.jpg, ab043e_0041eb35cd9144e89cd90043d24eb88a~mv2.jpg, …) and 6 with alt text that describes nothing (“DJI_0068.jpeg”, the file's own name; “TURF” on 3 pictures). Google's image guidelines ask for file names and alt text that say what the picture shows.

What we’d do: Every picture is named for what it shows, in the business's own words (franklin-standing-seam-metal-roof.webp, never IMG_4411.jpg), and its alt text says what is in it — the job, the place, the material — rather than a keyword.

Questions answered on the page

Only 1 question asked and answered on the pages read (1 on the home page). Answer engines quote pages that ask the customer's 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.

llms.txt

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

Business schema completeness

The business node has name, url, telephone, address, logo or image but not areaServed, openingHours.

What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.

Linked to its profiles

The page links Facebook and Instagram, but the business node has no sameAs naming them, 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.

Address and phone on the page

The phone is on the page, but not the town or the street address. Map search and the answer engines place a business by what its pages say.

What we’d do: The business name, phone and town — or street address — in the footer of every page, exactly as the Google Business Profile has them, and the same in the schema.

Service area stated

The home page does not say which towns the business serves — visitors and engines both need it.

What we’d do: A service-area line in the hero and footer, a page per town, and areaServed in the schema.

Mobile PageSpeed score

Lighthouse mobile performance 67/100 (measured 2026-09-29). 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.

Readable and tappable on a phone

One button or link is too small or too close to another to tap reliably (“Powered by Usercentrics Consent Management”).

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.

Image hygiene

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

Trust signals

Only guarantee — a visitor comparing three sites wants license, insurance, guarantee and years stated plainly.

What we’d do: License number, insurance, warranty and founding year on every page, and in the schema.

About and privacy pages

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

No stock or AI-marked pictures

1 picture marked as AI-made on the pages read: ChatGPT Image Sep 6, 2026 at 08_39_57 PM.png (ChatGPT's download name). Visitors comparing businesses, and Google's quality raters, look for photos of the business's own work.

What we’d do: The owner's own photos of real jobs are the proof of work, in every section that shows the work; a stock or generated picture only ever sets the mood, and it is named and described for what it shows.

Not a stock template

Built with Wix, from templates thousands of businesses share. Nothing is left over from the template, but the layout says “Wix” before it says anything about the business.

What we’d do: A site designed for this business — its own layout, type and colors, written from its own facts — with nothing left of whatever it was built from.

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.