Website review, no card needed

powerhome.com logo

powerhome.com website review

Visit site (opens in a new tab)Reviewed 18 November 202638 issues · 80 checks

This review found 38 issues worth fixing on powerhome.com, 14 of them high impact, across 80 checks. The most urgent: improve image delivery. 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
2.5 s1.9 sMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.2 s
Oct 31, 20262.2 s
Nov 7, 20262.1 s
Nov 14, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
115 ms87 msMay 30Nov 14112 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202692 ms
Jun 6, 202695 ms
Jun 13, 202699 ms
Jun 20, 202699 ms
Jun 27, 2026102 ms
Jul 4, 202699 ms
Jul 11, 202696 ms
Jul 18, 202695 ms
Jul 25, 202694 ms
Aug 1, 202690 ms
Aug 8, 202693 ms
Aug 15, 202695 ms
Aug 22, 2026103 ms
Aug 29, 2026103 ms
Sep 5, 2026100 ms
Sep 12, 202695 ms
Sep 19, 202693 ms
Sep 26, 202695 ms
Oct 3, 202692 ms
Oct 10, 202690 ms
Oct 17, 202695 ms
Oct 24, 2026107 ms
Oct 31, 2026105 ms
Nov 7, 2026112 ms
Nov 14, 2026112 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 powerhome.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. powerhome.com at 0.6 s0.6 s
  2. powerhome.com at 1.2 s1.2 s
  3. powerhome.com at 1.8 s1.8 s
  4. powerhome.com at 2.4 s2.4 s
  5. powerhome.com at 3.0 s3.0 s
  6. powerhome.com at 3.6 s3.6 s
  7. powerhome.com at 4.2 s4.2 s
  8. powerhome.com at 4.8 s4.8 s

Speed

5 to fix49
  • Improve image delivery

    4.8 s · 1.9 MB

    23 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.8 s faster on a phone.

  • Reduce unused JavaScript

    2.1 s · 400 KiB

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

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Google Tag Manager adds 391 ms

    391 ms

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

    400 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Fonts and others), adding 560 KiB and 394 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 52 KiB

    About 52 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.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 644 ms of it running JavaScript. That is comfortably low.

  • Server response: 44 ms

    44 ms

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

Core Web Vitals

12 to fix67
  • 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.

  • Largest Contentful Paint: 22.2 s

    22.2 s

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

  • Time to Interactive: 23.1 s

    23.1 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user CLS: 0.17

    0.17

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

  • Tap response (INP) got 20% slower for real visitors

    +20%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Total Blocking Time: 323 ms

    323 ms

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

  • Cumulative Layout Shift: 0.142

    0.142

    The layout shifts by 0.142 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 11 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

2 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 113 ms

    113 ms

    Real visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 5.8 MB in 64 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 64 requests on a phone: images 4.9 MB (46), scripts 801 KiB (6) and stylesheets 62 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 34 images in older formats

    34 images (3.7 MB) 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.

  • 17 images below the first screen load straight away

    17 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.65 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8790
  • 13 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 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 favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 219 internal links, 3 external

    The homepage links to 219 pages on powerhome.com and 3 external pages.

5 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “PowerHome.com provides professional power supply equipment and renewable power solutions for industrial and home applic…”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Power Supply & Solutions | Power Home”.

  • Canonical URL set

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

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

  • No llms.txt

    There is no https://www.powerhome.com/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.

2 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 (1,697 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    https://www.powerhome.com/solar-power and https://www.powerhome.com/solar-inverter all use the title “Solar Power Supplies | Power Home”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://www.powerhome.com/wishlist, https://www.powerhome.com/solar-power, https://www.powerhome.com/solar-panel, https://www.powerhome.com/portable-solar-panel, https://www.powerhome.com/flexible-pv-panel and https://www.powerhome.com/solar-charge-controller and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 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 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 14 pages that loaded have a <title>.

Best practices

Google 96100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    91 of 91 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 683 words of copy

    The homepage carries about 683 words of visible text.

3 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Register”, “SHOP NOW” and “Contact us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
nopCommerce
Analytics
Google Tag Manager
Hosting
AWS

Hiring

Hiring
3 open roles
Job board
careers page

Company

Employees
120
Headquarters
Mooresville

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 powerhome.com, including 17 speed issues, 4 SEO issues and 3 conversion gaps. 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