A slow first screen on a phone sends the homeowner to the next shop. What to cut, what to keep, and how to check.
A homeowner types "AC repair near me" with one thumb. The shop that should get the job is the one whose first screen can be used. If that first screen takes four seconds and a video starts on its own, the homeowner calls the next shop. Nobody in the office sees the visit. The job is already gone.
That miss is what a slow website costing local jobs looks like: a call that went to a neighbor because their page let someone tap a number. A speed grade can wait. The hallway cannot.
Trade shops hit the same wall on that first screen. Ethical AI is in Frisco, and the check works for a shop anywhere in the country.
The first screen is the job
The homeowner is in a warm hallway or a wet kitchen. They need three things in the first view: the trade, proof this is a real shop, and a way to call.
A useful first screen shows the trade in the heading, one short paragraph, and a tap-to-call number a thumb can hit. A single form or a single button can sit with that number. The page has loaded enough to be used.
Four seconds with an autoplay video is already past that moment. The clip is still spinning up. The number sits under it, or the video covers the tap. The homeowner goes back to the list and calls someone else.
Open the homepage the way they do. Use a phone, on a weak connection if you can stand where the signal drops. The office computer on fast internet hides the wait.
What to check, in order
Do this in one sitting. Write what you see. Hold the edits until the list is honest.
1. Open the homepage on a phone. Note the time from the tap until you can read the trade and hit the phone number. If a video starts by itself and that screen is still not ready around four seconds, this is the failure.
2. Watch what moves on its own. A video that starts without a tap is the first suspect. A second background video on the homepage is the cut. One looping clip behind the heading is already heavy. Two clips are how the call button loses.
3. Find the hero image. A full-size PNG makes the phone download a print-weight picture before the number is reliable. A photo of a real truck can stay. The file weight is the problem. If the builder already has a lighter image path, use that field and keep the raw upload out of the page code.
4. Look for a logo carousel or a strip of placeholder logos that are not real customers. Those rows are extra requests, and they teach the visitor to doubt the page.
5. Read the heading. One H1, and it names the trade. "AC repair" is a heading. "Welcome to our family of solutions" makes the visitor hunt. Extra H1s become ordinary subheadings.
6. Put a thumb on the phone number. It has to be a real link that opens the dialer. Plain text fails. The number belongs with the heading, visible before any scroll.
7. Read the first paragraph out loud. It says what you do and the area you actually cover, in a few lines. Then one form or one button.
8. Hold the page beside the business profile the map listing uses. Trade, phone number, and honest service area match. A fast page with a different trade or a different number still loses the homeowner. The site behind a map listing is the same shop.
9. Scroll once. Note anything that jumps, covers the number, or asks for a chat and a discount before the call is possible.
Any line that fails is the edit. If the theme will not allow that edit, the theme is the problem. Stop decorating it.
What to cut first
Cut in this order. Stop when the first screen is usable.
Cut the logo carousel and any placeholder client row. Stock logos and random stock photos of people who are not customers add weight. A real photo of your crew, with permission, can live further down. It does not belong in a moving strip at the top.
Cut the second background video. If one clip must stay, it waits for a tap and stays off the phone number.
Cut uncompressed PNG heroes. Put the photo through the builder's image field so the lighter path can run. Keep the picture. A PNG saved for a printed banner has no job on a phone homepage.
Cut autoplay. A page that feels alive only when a video starts itself is performing for the owner. A still screen with a clear number lets the homeowner act.
Load the phone again. Trade readable. Number tappable. No surprise video.
What to keep
Keep one H1 that names the trade, so the map result and the page name the same business.
Keep the tap-to-call number, large enough for a thumb. A simple header can carry it once.
Keep a short first paragraph. Name the work and the customer you serve. One honest line about the area you cover is enough. A block that names twenty towns is harder to read on a phone, and reading time is part of the cost.
Keep one form or one button on that first screen. "Call now" beside a short form is plenty when both are real. The form asks for name, phone, and the problem in one line.
Keep the match between the page and the business profile. Same name, same phone, same trade. If the profile says you answer until 7 and the page says the same, the person who calls at 6:40 is not surprised. Confusion sends people back to the list as surely as a spinning video.
What to leave out
Leave the score chase for later. A speed report is a clue. A flattering grade can still hide the phone number under a video. A modest grade can still win the call when the first screen is plain. Fix the first screen first.
Leave out a slider in place of the video you removed. A slider is another wait. One still photograph is enough.
Leave out chat bubbles, exit banners, and discount covers on the first screen. They are new files to load and new boxes to close. Say the offer on the call, if you offer one.
Leave out a town name in every paragraph. Say the service area once. Repeating towns does not make the page faster to load.
Leave out any promise that a faster page will rank first. Speed helps a person finish the call. It does not hand you a position on the map.
Leave the about page, the service list, and the company story for another sitting. Those pages matter. The call is dying on the homepage first screen.
A worked example
An AC repair homepage, as a template often ships it. A wide video of a van plays on its own. Under it, a second clip shows a technician with a gauge. A carousel of gray logos loops between them. The logos came with the template. They are not customers. The heading says "Comfort solutions for every season." The phone number lives in the footer. The hero is a PNG large enough for a banner. On the office computer the page looks busy. On a phone, the first four seconds are video startup, a jumping carousel, and a picture that has not finished. The heading never names the trade. The number is a scroll away. The homeowner calls the next shop.
The same shop, after the cuts, still has the same trucks. The only H1 reads "AC repair when the house will not cool." Two sentences follow: residential repair, and the area you actually serve, named once. The phone number is a tap-to-call button under those sentences. A short form sits beside it: name, phone, and what the system is doing. No second video. No logo row. One still photo of a real truck goes through the builder's image field. The photo arrives with the heading. Nothing plays until a person asks it to.
The next test is the same test. A phone, a weak signal, a number you can hit before those four seconds run out. If the template will not let the video stop, will not allow a single H1, and will not serve a light image, patching one file will not save the page.
If the listing opens another page
The website button on the business profile does not always open the homepage. Sometimes it opens a service page. That address is the one the homeowner sees.
From a phone, tap the website control on the profile and note the address that loads. Run the same checks there. One H1 that names the trade. The same phone number as the profile. No autoplay sitting on the number. A fast homepage does not rescue a heavy service page the listing sends people to.
Walk the same screen with a short review
The phone test stands on its own. For a second set of eyes, use the tools you already have, in this order. Each one gets a narrow job. You keep the decision.
Start with Claude. Paste the notes: what moved, where the number sat, what the heading said, whether the hero was a heavy PNG. Ask Claude to separate "cut now" from "keep," and to mark placeholder logos apart from real crew photos.
Hand that list to GPT. Ask for the edit order the person who can log in will follow this week. One edit per step. Skip the redesign essay.
Hand the same list to Grok. Ask which lines are theater. A grade with no phone number is theater. A new slogan with autoplay still on is theater. Keep the notes that point back to the tap-to-call test.
Show a phone screenshot to Gemini. Ask what covers the number, what starts on its own, and whether the heading names the trade.
Use Perplexity last, and only for a how-to in the builder you already use: how to turn off autoplay, or how to run an image through the lighter path that builder already offers. If the answer sends you to a stack you do not have, ignore it.
Don't have Claude? No problem. Don't have GPT? No problem. Start with the tool you do have and keep the same jobs in order: cut versus keep, then the edit steps, then what is theater, then the screenshot, then the builder how-to.
Ask none of them for a fake customer, a review count, or a rank. If a draft adds a logo row or a town list, delete that part. Your name, your phone, and your real service area stay yours.
When the theme cannot hold the call
A theme that locks two videos, a logo carousel, a heavy PNG, and a pile of pop-ups will keep costing jobs. A new font will not change that.
Look at the presence as one shop: the business profile, the page the map listing opens, and the phone path the homeowner uses. Ethical AI does that work with trades owners from Frisco. The first screen is the call. The work is what to remove and what has to match. Rank stays outside any promise.
To walk your own first screen, book a short call. Bring the page on your phone. The check is the same: what moves, where the number sits, what the heading says, and whether this theme can be saved.
Ethical AI · Frisco, TX · 469-669-2728
