Website review, no card needed

polarpower.com logo

polarpower.com website review

Visit site (opens in a new tab)Reviewed 22 October 202639 issues · 83 checks

This review found 39 issues worth fixing on polarpower.com, 15 of them high impact, across 83 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
3.8 s2.4 sMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.6 s
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20263.0 s
May 30, 20263.1 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.1 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.3 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.1 s
Aug 22, 20263.2 s
Aug 29, 20263.3 s
Sep 5, 20263.7 s
Sep 12, 20263.4 s
Sep 19, 20263.3 s
Sep 26, 20263.6 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
116 ms72 msMay 2Oct 1782 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202696 ms
May 9, 2026100 ms
May 16, 2026108 ms
May 23, 2026101 ms
May 30, 2026108 ms
Jun 13, 202695 ms
Jun 20, 202693 ms
Jul 4, 202687 ms
Jul 11, 202683 ms
Jul 18, 202677 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 2026111 ms
Aug 22, 2026111 ms
Aug 29, 2026108 ms
Sep 5, 2026101 ms
Sep 12, 202697 ms
Sep 19, 202679 ms
Sep 26, 202681 ms
Oct 10, 202681 ms
Oct 17, 202682 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 polarpower.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. polarpower.com at 0.6 s0.6 s
  2. polarpower.com at 1.3 s1.3 s
  3. polarpower.com at 1.9 s1.9 s
  4. polarpower.com at 2.6 s2.6 s
  5. polarpower.com at 3.2 s3.2 s
  6. polarpower.com at 3.9 s3.9 s
  7. polarpower.com at 4.5 s4.5 s
  8. polarpower.com at 5.1 s5.1 s

Speed

7 to fix57
  • Reduce unused JavaScript

    2.3 s · 427 KiB

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

  • Render-blocking requests

    1.4 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Reduce unused CSS

    1.2 s · 204 KiB

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

  • Improve image delivery

    500 ms · 759 KiB

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    350 ms · 469 KiB

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

  • Main-thread work: 2.1 s

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

  • Legacy JavaScript

    200 ms · 10 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 280 KiB and 143 ms of main-thread time.

  • Font display

    100 ms

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

  • 6 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 93 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 63 ms

    63 ms

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

Core Web Vitals

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

  • Real-user TTFB: 2.3 s

    2.3 s

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

  • Largest Contentful Paint: 12.9 s

    12.9 s

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

  • First Contentful Paint: 5.8 s

    5.8 s

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

  • Time to Interactive: 14.0 s

    14.0 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • 1 image without width and height

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

5 checks passed
  • Real-user INP: 82 ms

    82 ms

    Real visitors wait 82 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.

  • Tap response (INP) got 17% faster for real visitors

    -17%

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

  • Total Blocking Time: 82 ms

    82 ms

    Scripts block the page for only 82 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.9 MB in 71 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 71 requests on a phone: images 3.7 MB (32), scripts 821 KiB (19) and stylesheets 221 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.40 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8592
  • 4 text elements with low contrast

    4 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 (9 elements)

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

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

7 to fixGoogle 6964
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is long (107 characters)

    Your title is 107 characters, so Google will cut it off around 60: “Polar Power – DC generators & Alternators, Hybrid Power, Solar Power, Telecommunications,…”.

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

  • 2 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 70 internal links, 7 external

    The homepage links to 70 pages on polarpower.com and 7 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://polarpower.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://polarpower.com/wp-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://polarpower.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 (390 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://polarpower.com/events is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://polarpower.com/whats-new, https://polarpower.com/about-us, https://polarpower.com/careers, https://polarpower.com/events, https://polarpower.com/blog and https://polarpower.com/products and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://polarpower.com/whats-new, https://polarpower.com/about-us, https://polarpower.com/careers, https://polarpower.com/blog, https://polarpower.com/products and https://polarpower.com/products/dc-generators have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 pages slow to respond

    https://polarpower.com/whats-new, https://polarpower.com/about-us, https://polarpower.com/events, https://polarpower.com/blog, https://polarpower.com/products and https://polarpower.com/products/dc-generators and 6 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 57 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.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7393
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to image at 'https://www.polarpower.com/wp-content/uploads/2014/08/tele2.png' from origin 'https://polarpower.co…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • Only about 188 words

    The homepage has only about 188 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Parts Order Form”, “Contact Us” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 polarpower.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 © 2024.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on polarpower.com, including 16 speed issues, 7 SEO issues and 4 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