Website review, no card needed

dchousepower.com logo

dchousepower.com website review

Visit site (opens in a new tab)Reviewed 6 November 202638 issues · 89 checks

This review found 38 issues worth fixing on dchousepower.com, 12 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.4 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
122 ms102 msMay 16Oct 31115 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026106 ms
May 30, 2026110 ms
Jun 6, 2026112 ms
Jun 13, 2026109 ms
Jun 20, 2026105 ms
Jun 27, 2026106 ms
Jul 4, 2026108 ms
Jul 11, 2026110 ms
Jul 18, 2026108 ms
Jul 25, 2026105 ms
Aug 1, 2026105 ms
Aug 8, 2026108 ms
Aug 15, 2026112 ms
Aug 22, 2026117 ms
Aug 29, 2026120 ms
Sep 5, 2026116 ms
Sep 12, 2026116 ms
Sep 19, 2026113 ms
Sep 26, 2026113 ms
Oct 3, 2026113 ms
Oct 10, 2026112 ms
Oct 17, 2026113 ms
Oct 24, 2026114 ms
Oct 31, 2026115 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

Full-page screenshot of dchousepower.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dchousepower.com at 0.7 s0.7 s
  2. dchousepower.com at 1.3 s1.3 s
  3. dchousepower.com at 2.0 s2.0 s
  4. dchousepower.com at 2.6 s2.6 s
  5. dchousepower.com at 3.3 s3.3 s
  6. dchousepower.com at 3.9 s3.9 s
  7. dchousepower.com at 4.6 s4.6 s
  8. dchousepower.com at 5.3 s5.3 s

Speed

7 to fix60
  • Reduce unused JavaScript

    3.1 s · 646 KiB

    About 646 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Improve image delivery

    300 ms · 2.6 MB

    22 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, omnisnippet1.com and Shopify and others), adding 1.2 MB and 760 ms of main-thread time.

  • Google Tag Manager adds 498 ms

    498 ms

    Google Tag Manager costs a phone 498 ms of main-thread work and 668 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.

  • Render-blocking requests

    300 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Main-thread work: 2.7 s

    A phone's processor spends 2.7 s on main-thread work while loading, 932 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Use efficient cache lifetimes

    100 ms · 157 KiB

    11 files are served with short cache lifetimes, so returning visitors download them again (157 KiB).

  • Minify JavaScript

    150 ms · 51 KiB

    51 KiB could be saved by minifying JavaScript.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 196 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    150 ms · 28 KiB

    About 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 15 ms

    15 ms

    Your server sent the HTML in 15 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 30.2 s

    30.2 s

    Your largest element takes 30.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 31.6 s

    31.6 s

    The page becomes fully interactive after 31.6 s. Good is under 3.8 s.

  • Speed Index: 7.3 s

    7.3 s

    Visually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.

  • 33 images without width and height

    33 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 2.2 s

    2.2 s

    The first text or image appears after 2.2 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 278 ms

    278 ms

    Scripts block taps and scrolling for 278 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 96 ms

    96 ms

    Real 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.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 589 ms

    589 ms

    Real visitors wait 589 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix38
  • Page weight: 8.6 MB in 249 requests

    8.6 MB

    Your homepage downloads 8.6 MB in 249 requests on a phone: images 6.1 MB (58), scripts 1.3 MB (57) and other files 1.0 MB (115). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    stock-image-photograph-stock-cat-image-man-woman-dog-backgro weighs 781 KiB. On a phone connection a single image that size takes seconds.

  • 8 images below the first screen load straight away

    8 images further down the page (747 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 4 images far larger than shown

    427 KiB

    4 images are downloaded at several times the size a phone draws them, for example 04_a84820a7-b632-4bce-91c8-bf133f864a9b.jpg at 1,600 px wide, shown at 151 px. Resized copies would save about 427 KiB.

  • About 2.4 g of CO₂ per visit

    2.45 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.45 g of CO₂e: 294.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

10 to fixGoogle 7488
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • 48 images without alt text

    48 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 22 links without text

    22 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (12 elements)

    Headings should not be empty: 12 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Meta description is short (44 characters)

    Your meta description is only 44 characters: “Deep Cycle Lithium Battery | LiFePO4 Battery”. 70 to 160 characters is enough to sell the click.

  • 14 H1 headlines

    There are 14 <h1> headlines (“dchousepower”, “” and “”). One clear main headline is easier for people and search engines.

  • 125 internal links, 10 external

    The homepage links to 125 pages on dchousepower.com and 10 external pages.

6 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “DC HOUSE | Deep Cycle Lithium Battery Store”.

  • Canonical URL set

    The canonical URL is https://www.dchousepower.com/.

  • Structured data in place

    Structured data found: BreadcrumbList and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.dchousepower.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (728 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.dchousepower.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 6 pages share a meta description

    https://www.dchousepower.com/products/dc-house-sentry-g100-48v-100ah-ul2580-lifepo4-metal-case-battery-with-charger-ideal-for-golf-carts and https://www.dchousepower.com/products/dc-house-sentry-g100-48v-100ah-ul2580-lifepo4-metal-case-battery-ideal-for-golf-carts use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.dchousepower.com/pages/warranty, https://www.dchousepower.com/products/dc-house-sentry-g100-48v-100ah-ul2580-lifepo4-metal-case-battery-with-charger-ideal-for-golf-carts, https://www.dchousepower.com/products/48v-100ah-metal-case-lifepo4-lithium-golf-cart-battery-charger, https://www.dchousepower.com/products/48v-50ah-lifepo4-lithium-golf-cart-battery, https://www.dchousepower.com/products/36v-100ah-metal-case-lifepo4-lithium-golf-cart-battery-charger and https://www.dchousepower.com/collections/lifepo4-golf-cart-kit and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://www.dchousepower.com/pages/warranty, https://www.dchousepower.com/products/dc-house-sentry-g100-48v-100ah-ul2580-lifepo4-metal-case-battery-with-charger-ideal-for-golf-carts, https://www.dchousepower.com/products/48v-100ah-metal-case-lifepo4-lithium-golf-cart-battery-charger, https://www.dchousepower.com/products/48v-50ah-lifepo4-lithium-golf-cart-battery, https://www.dchousepower.com/products/36v-100ah-metal-case-lifepo4-lithium-golf-cart-battery-charger and https://www.dchousepower.com/collections/lifepo4-golf-cart-kit and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.

6 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.

  • 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

4 to fixGoogle 8877
  • 25 small tap targets

    25 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 4 JavaScript errors while loading

    4 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 ()”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 374 words of copy

    The homepage carries about 374 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Order Track”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact Us”, “Order Track” and “🛍️Shop”.

  • 13 short forms

    13 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • 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

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 30 other companies contacted

    Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 dchousepower.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 14 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Comments Plus Blog Comments · Judge Me Reviews · Impact Com · Gempages Builder · Powerful Form Builder · Simprosys Google Shopping Feed · Omnisend · Event Promotion Bar · Ease Product Attachments · recovermycart.com · goaffpro.com · trafficmanager.net · okasconcepts.com · hextom.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on dchousepower.com, including 13 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25