Website review, no card needed

horizonpwr.com logo

horizonpwr.com website review

Visit site (opens in a new tab)Reviewed 20 October 202637 issues · 80 checks

This review found 37 issues worth fixing on horizonpwr.com, 12 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of horizonpwr.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. horizonpwr.com at 0.5 s0.5 s
  2. horizonpwr.com at 0.9 s0.9 s
  3. horizonpwr.com at 1.4 s1.4 s
  4. horizonpwr.com at 1.8 s1.8 s
  5. horizonpwr.com at 2.3 s2.3 s
  6. horizonpwr.com at 2.7 s2.7 s
  7. horizonpwr.com at 3.2 s3.2 s
  8. horizonpwr.com at 3.6 s3.6 s

Speed

7 to fix58
  • Use efficient cache lifetimes

    2.1 s · 1.9 MB

    26 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

  • Font display

    2.3 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.3 s).

  • Reduce unused JavaScript

    1.6 s · 513 KiB

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

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58 (desktop: 78). 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, Facebook and Google Analytics and others), adding 761 KiB and 715 ms of main-thread time.

  • Improve image delivery

    600 ms · 119 KiB

    4 images could be 119 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Google Tag Manager adds 434 ms

    434 ms

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    46 KiB

    About 46 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 514 ms

    514 ms

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

Core Web Vitals

6 to fix55
  • Largest Contentful Paint: 9.1 s

    9.1 s

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

  • Time to Interactive: 14.3 s

    14.3 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • Total Blocking Time: 446 ms

    446 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 6 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix33
  • 1 image over 500 KB

    Horizon-PWR-Residential-Solar-3.png weighs 710 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    527 KiB

    2 images are downloaded at several times the size a phone draws them, for example Horizon-PWR-Residential-Solar-3.png at 1,080 px wide, shown at 312 px. Resized copies would save about 527 KiB.

  • Page weight: 2.9 MB in 52 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 52 requests on a phone: scripts 1.3 MB (20), images 1.3 MB (9) and fonts 341 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.2 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.

  • 4 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.83 g

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

Accessibility

8 to fixGoogle 6285
  • 33 text elements with low contrast

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

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

    All page content should be contained by landmarks: 21 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.

  • Zoom is disabled

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

  • 1 link without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

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

SEO

4 to fixGoogle 9287
  • Structured data has 2 problems

    Structured data found (BreadcrumbList, ImageObject, Organization and ProfessionalService) but with 2 problems, for example “Organization: logo is not an absolute URL ("wp-content/uploads/2020/10/logo500.png")”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://horizonpwr.com/sitemap.xml, so Google discovers your pages only by following links.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 61 internal links, 9 external

    The homepage links to 61 pages on horizonpwr.com and 9 external pages.

5 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Hundreds Of Families In Idaho And Oregon Are Switching To Solar Power In 2022 With Horizon PWR - Top-Rated Local Solar …”.

  • One H1 headline

    Your main headline reads: “Award-Winning Solar Power Company”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Solar Panel Installation Company | Idaho & Oregon Solar Power”.

  • Canonical URL set

    The canonical URL is https://horizonpwr.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

    There is no https://horizonpwr.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.

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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

3 to fix75
  • 11 pages without a title

    https://horizonpwr.com/backup-battery, https://horizonpwr.com/tax-credits, https://horizonpwr.com/idaho-solar-power, https://horizonpwr.com/blackfoot-solar-power, https://horizonpwr.com/caldwell-solar-power and https://horizonpwr.com/eagle-idaho-solar-power and 5 others have no <title>, so Google invents the link text in results.

  • 12 pages without a meta description

    https://horizonpwr.com/backup-battery, https://horizonpwr.com/tax-credits, https://horizonpwr.com/idaho-solar-power, https://horizonpwr.com/blackfoot-solar-power, https://horizonpwr.com/boise-solar-power and https://horizonpwr.com/caldwell-solar-power and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://horizonpwr.com/home-solar-installation, https://horizonpwr.com/commercial-solar-power-energy, https://horizonpwr.com/agriculture-solar, https://horizonpwr.com/backup-battery, https://horizonpwr.com/tax-credits and https://horizonpwr.com/idaho-solar-power and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages with very little text

    https://horizonpwr.com/backup-battery, https://horizonpwr.com/tax-credits, https://horizonpwr.com/idaho-solar-power, https://horizonpwr.com/blackfoot-solar-power, https://horizonpwr.com/caldwell-solar-power and https://horizonpwr.com/eagle-idaho-solar-power and 5 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 32 found) and read each the way a search engine does.

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

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

Best practices

2 to fixGoogle 9688
  • 3 JavaScript errors while loading

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

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix95
  • Thin social proof

    Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • About 1,239 words of copy

    The homepage carries about 1,239 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: “REQUEST A QUOTE”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “GET A QUOTE”, “Request a Quote” and “Learn More”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, HubSpot and Cloudflare Web Analytics.

  • 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

1 to fix
  • 5 trackers load before any consent

    5

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

  • 7 cookies set on arrival

    7

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

  • 14 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on horizonpwr.com, including 13 speed issues, 4 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