—The clearest local signal is not that every contractor needs a redesign. Among 95 home pages that returned HTTP 200, 59 lacked at least one of two detected conversion paths—a telephone link or an HTML form—and 28 lacked both. Those are verification flags, not proof of missed business.
The sample is useful because it shows variation, not because it is a market census.
Workahead harvested 105 unique website hosts from electrician-related directory pages for 10 DFW cities, then fetched and scored the home pages on July 25, 2026. Forty-two were placed in the weakest gap class, 36 in the middle class, and 27 in the polished class.
That distribution supports a narrow conclusion: DFW contractors present very different digital buying experiences. It does not tell us how many electrical contractors operate in DFW, how much revenue any site produces, or whether the directory sample represents businesses with no website.
See the full DFW cluster →Ten city lists produced one website sample, with uneven city representation.
The 105 unique hosts came from electrician-related directory lists for Dallas, Fort Worth, Arlington, Plano, Irving, Frisco, McKinney, Denton, Garland, and Mesquite. Arlington contributed 18 hosts, Dallas 17, Denton 15, Garland 14, Fort Worth 10, Frisco 8, Irving and Plano 7 each, Mesquite 6, and McKinney 3.
Those counts describe the harvested sample, not the size of each city market. Directory inclusion, duplicates removed at the host level, and the availability of a website all shape the denominator.
| City list | Hosts | Share of sample |
|---|---|---|
| Arlington | 18 | 17.1% |
| Dallas | 17 | 16.2% |
| Denton | 15 | 14.3% |
| Garland | 14 | 13.3% |
| Fort Worth | 10 | 9.5% |
| Frisco | 8 | 7.6% |
| Irving | 7 | 6.7% |
| Plano | 7 | 6.7% |
| Mesquite | 6 | 5.7% |
| McKinney | 3 | 2.9% |
The response path is the first thing to verify, not the last.
Among the 95 home pages that returned HTTP 200, 59 lacked at least one of two detected conversion paths: a telephone link or a literal HTML form. Twenty-eight lacked both, while 36 had both. Across the full 105-site audit, 36 pages carried the explicit NO_TEL_LINK flag and 23 of those were in the weakest gap class.
These are homepage implementation signals. JavaScript widgets, embedded booking tools, unconventional call controls, and secondary-page forms can evade a bounded HTML audit. Presence also does not prove visibility, correct routing, successful submission, response time, or booking conversion. Manual mobile and operational verification comes before any business-level claim.
Read the emergency-demand field note →A detected control is different from a working customer path.
Of the 95 home pages returning HTTP 200, 36 showed both a telephone link and a literal HTML form, 31 showed exactly one of those controls, and 28 showed neither. The last two groups produce the 59-page verification set.
The screen cannot prove placement, tap behavior, form delivery, call routing, after-hours coverage, response time, or booked revenue. It narrows the manual review queue; it does not score the business.
| Detected path | Pages | Share of reachable |
|---|---|---|
| Telephone link + HTML form | 36 | 37.9% |
| Exactly one of the two | 31 | 32.6% |
| Neither detected | 28 | 29.5% |
| Reachable denominator | 95 | 100% |
Thin pages and access failures are separate problems.
Forty-five reviewed pages triggered the audit’s thin-or-light-content rules. Ten hosts returned a 403, 404, DNS, TLS, or timeout result during the bounded fetch. Those groups overlap, but they should not be collapsed into one diagnosis.
A thin page raises questions about service clarity, proof, and local relevance. An access failure raises questions about availability, security configuration, or crawler compatibility. Both deserve verification; neither proves business weakness.
Review the live mobile home page before diagnosing a company.
Test the primary telephone and form paths with permission.
Separate design quality from access, content depth, and operational follow-up.
Ten hosts failed the bounded fetch; 45 pages triggered thin-or-light content rules.
Five hosts returned HTTP 403, one returned HTTP 404, and four produced DNS, TLS, or timeout failures. Separately, 45 reviewed pages triggered the audit’s thin-or-light-content heuristics and seven carried a missing-viewport flag.
These observations should remain separate. An HTTP failure can reflect security or crawler compatibility. A low word count can be appropriate for a focused page or can signal missing service proof. Neither observation establishes customer harm without a browser and workflow review.
| Observation | Count | Required follow-up |
|---|---|---|
| HTTP 200 | 95 | Inspect mobile controls and service clarity |
| HTTP 403 | 5 | Check normal-browser access and security posture |
| HTTP 404 | 1 | Confirm current destination and redirects |
| DNS, TLS, or timeout | 4 | Recheck availability from a normal client |
| Thin-or-light rule triggered | 45 | Review service detail, proof, and local relevance |
| Missing viewport flag | 7 | Test actual mobile rendering |
Audit the path from search to answered call before buying more attention.
For an owner, the next useful measurement is not a generic website score. It is a short funnel: qualified source, landing experience, call or form action, response time, booked estimate, won job, and collected revenue. The website audit identifies where to look; the operating ledger establishes whether fixing it matters.
The audit sample and the regulated market denominator answer different questions.
TDLR’s active Electrical Contractor file dated August 11, 2026 contained 2,956 license rows with business addresses in the 11-county DFW frame. Dallas County accounted for 922 rows and Tarrant County 710; together they represented 55.2% of those DFW-address rows.
That administrative denominator is not interchangeable with the 105-host web sample. A license row is not a unique consumer brand, establishment, service area, crew, or active residential operator. It is useful for showing why a directory-derived website sample cannot support market-share claims.
| Geography | License rows | Share of DFW rows |
|---|---|---|
| Dallas County | 922 | 31.2% |
| Tarrant County | 710 | 24.0% |
| Other nine DFW counties | 1,324 | 44.8% |
| 11-county DFW frame | 2,956 | 100% |
| Texas statewide | 14,013 | — |
Verify the mobile call and intake path on your own site, then connect it to response and booked-job data before funding a redesign or more traffic.
Read the methodology →What supports this report
105 unique hosts sourced from Expertise.com city pages; automated fetch and heuristic screen, not a census or full UX review.
Texas normalized relative interest, not DFW search volume.
Source ↗Active license and business-address records; not unique brands, establishments, service areas, crew counts, or market share.
Source ↗