Website review, no card needed
servicechampions.net website review
Visit site (opens in a new tab)Reviewed 24 October 202636 issues · 90 checks
This review found 36 issues worth fixing on servicechampions.net, 15 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.9 s |
| May 9, 2026 | 4.0 s |
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 115 ms |
| May 9, 2026 | 116 ms |
| May 16, 2026 | 115 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 103 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 93 ms |
| Jul 11, 2026 | 92 ms |
| Jul 18, 2026 | 90 ms |
| Jul 25, 2026 | 90 ms |
| Aug 1, 2026 | 92 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 107 ms |
| Aug 29, 2026 | 107 ms |
| Sep 5, 2026 | 105 ms |
| Sep 12, 2026 | 106 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 106 ms |
| Oct 10, 2026 | 106 ms |
| Oct 17, 2026 | 110 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.5 s
2.2 s
2.9 s
3.7 s
4.4 s
5.1 s
5.9 s
Speed
Reduce unused JavaScript
5.1 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.
Use efficient cache lifetimes
2.1 s · 1.3 MB90 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Render-blocking requests
2.3 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Reduce unused CSS
1.2 s · 271 KiBAbout 271 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 33
33/100Your mobile performance score is 33 (desktop: 32). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, servicetitan.com and purechatcdn.com and others), adding 3.0 MB and 1.1 s of main-thread time.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 404 ms. During a long task the page ignores taps.
Google Tag Manager adds 350 ms
350 msGoogle Tag Manager costs a phone 350 ms of main-thread work and 507 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Legacy JavaScript
300 ms · 94 KiBPolyfills for old browsers add 94 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
servicetitan.com adds 258 ms
258 msservicetitan.com costs a phone 258 ms of main-thread work and 1.3 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
351 KiB6 images could be 351 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
localimpact.com adds 98 ms
98 mslocalimpact.com costs a phone 98 ms of main-thread work and 327 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 8.3 s
8.3 sThe first text or image appears after 8.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 32.5 s
32.5 sYour largest element takes 32.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “$58 Furnace or AC Tune-up. Click to schedule our visit.”.
Time to Interactive: 42.5 s
42.5 sThe page becomes fully interactive after 42.5 s. Good is under 3.8 s.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 115 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.9 MB in 192 requests
6.9 MBYour homepage downloads 6.9 MB in 192 requests on a phone: scripts 3.5 MB (74), other files 1.8 MB (42) and images 1.0 MB (38). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
hero-same-day-free-sc25wi001wg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
4 images far larger than shown
376 KiB4 images are downloaded at several times the size a phone draws them, for example hero-same-day-free-sc25wi001wg at 1,920 px wide, shown at 388 px. Resized copies would save about 376 KiB.
2 images in older formats
2 images (271 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 2.0 g of CO₂ per visit
1.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.97 g of CO₂e: 236.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Links must have discernible text (3 elements)
Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (191 characters)
Your meta description is 191 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
132 internal links, 12 external
The homepage links to 132 pages on servicechampions.net and 12 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Top-Rated Plumber, HVAC, and Electrical Contractor in Alameda County, Santa Clara, Contra Costa & Sacramento Counties”.
Title: 50 characters
Your title is a healthy 50 characters: “HVAC, Plumbing, and Electrical | Service Champions”.
Canonical URL set
The canonical URL is https://www.servicechampions.net/.
Structured data in place
Structured data found: HomeAndConstructionBusiness.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.servicechampions.net/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.servicechampions.net/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (686 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
17 of 17 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 510 words of copy
The homepage carries about 510 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Schedule My Visit” and “Learn more >”.
15 calls to action
The homepage has 15 calls to action, for example “Schedule My Visit”, “Learn more >” and “Schedule my visit”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 2 customer or partner logos and 5 trust badges.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
26 cookies set on arrival
26Opening the homepage sets 26 cookies (measured from a US location before any click).
47 other companies contacted
Loading the homepage contacts 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at servicechampions.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Hiring
- Hiring
- 8 open roles
- Teams
- Administrative (1), Customer Service (1), Dispatch (1), Plumbing Install (1)
- Job board
- greenhouse
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on servicechampions.net, including 24 speed issues, 2 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.