Website review, no card needed

powrparts.com logo

powrparts.com website review

Visit site (opens in a new tab)Reviewed 10 November 202627 issues · 86 checks

This review found 27 issues worth fixing on powrparts.com, 4 of them high impact, across 86 checks. The most urgent: 10 text elements with low contrast. 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.1 s606 msMay 23Nov 7660 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026857 ms
May 30, 2026863 ms
Jun 6, 2026844 ms
Jun 13, 2026796 ms
Jun 20, 2026785 ms
Jun 27, 2026781 ms
Jul 4, 2026776 ms
Jul 11, 2026817 ms
Jul 18, 2026831 ms
Jul 25, 2026829 ms
Aug 1, 2026828 ms
Aug 8, 2026853 ms
Aug 15, 2026829 ms
Aug 22, 2026875 ms
Aug 29, 2026991 ms
Sep 5, 2026991 ms
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 2026922 ms
Oct 3, 2026820 ms
Oct 10, 2026790 ms
Oct 17, 2026752 ms
Oct 24, 2026729 ms
Oct 31, 2026707 ms
Nov 7, 2026660 ms
Real-visitor tap response (INP)75th percentile, phones
133 ms89 msMay 23Nov 794 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026103 ms
May 30, 2026105 ms
Jun 6, 2026105 ms
Jun 13, 202696 ms
Jun 20, 202694 ms
Jun 27, 202696 ms
Jul 4, 202699 ms
Jul 11, 2026113 ms
Jul 18, 2026120 ms
Jul 25, 2026121 ms
Aug 1, 2026128 ms
Aug 8, 2026115 ms
Aug 15, 2026114 ms
Aug 22, 2026120 ms
Aug 29, 2026123 ms
Sep 5, 2026119 ms
Sep 12, 2026120 ms
Sep 19, 2026119 ms
Sep 26, 2026118 ms
Oct 3, 2026113 ms
Oct 10, 2026118 ms
Oct 17, 2026113 ms
Oct 24, 2026100 ms
Oct 31, 2026100 ms
Nov 7, 202694 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 powrparts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. powrparts.com at 0.8 s0.8 s
  2. powrparts.com at 1.6 s1.6 s
  3. powrparts.com at 2.3 s2.3 s
  4. powrparts.com at 3.1 s3.1 s
  5. powrparts.com at 3.9 s3.9 s
  6. powrparts.com at 4.7 s4.7 s
  7. powrparts.com at 5.5 s5.5 s
  8. powrparts.com at 6.2 s6.2 s

Speed

5 to fix93
  • 2 long tasks on the main thread

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

  • Reduce unused JavaScript

    274 KiB

    About 274 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 2.7 s

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

  • 1,755 HTML elements

    The page has 1,755 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Shopify adds 58 ms

    58 ms

    Shopify costs a phone 58 ms of main-thread work and 320 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and boostcommerce.io and others), adding 661 KiB and 201 ms of main-thread time.

  • Reduce unused CSS

    139 KiB

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

  • Improve image delivery

    42 KiB

    1 image could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    20 KiB

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

  • Legacy JavaScript

    7 KiB

    Polyfills for old browsers add 7 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
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Server response: 23 ms

    23 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 9.9 s

    9.9 s

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

  • Speed Index: 4.7 s

    4.7 s

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

  • Total Blocking Time: 227 ms

    227 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

10 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: 0.6 s

    0.6 s

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

  • Real-user INP: 94 ms

    94 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 0.6 s

    0.6 s

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

  • Real-user TTFB: 475 ms

    475 ms

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

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

    -21%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold.

Images and page weight

3 to fix69
  • Page weight: 3.5 MB in 199 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 199 requests on a phone: images 1.4 MB (9), other files 803 KiB (101) and scripts 752 KiB (71). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    AdobeStock_903129263_2000x1334.jpg 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).

  • 1 image far larger than shown

    223 KiB

    1 image is downloaded at several times the size a phone draws it, for example AdobeStock_903129263_2000x1334.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 223 KiB.

  • About 1.0 g of CO₂ per visit

    0.99 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 119.1 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

7 to fixGoogle 8591
  • 10 text elements with low contrast

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

  • Hidden but focusable

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Facility Power & OEM Parts | Batteries, Chargers & More — powRparts”.

  • Meta description is long (209 characters)

    Your meta description is 209 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • 177 internal links, 11 external

    The homepage links to 177 pages on powrparts.com and 11 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Forklift Batteries, Chargers & Industrial Parts”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization 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://powrparts.com/sitemap.xml.

AI search readiness

100
4 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,277 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “SyntaxError: Failed to execute 'querySelector' on 'Document': '[name=' is not a valid selector.”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 784 words of copy

    The homepage carries about 784 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: “Shop Rentals” and “Shop Used Inventory”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop Rentals”, “Shop Used Inventory” and “Shop Batteries”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 5 email links.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and LinkedIn Insight (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, 1 of them by other companies (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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 powrparts.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Boost Ai Search Filter · Avada Seo Suite · Air Reviews · Selleasy · Circuly Subscriptions

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 Tag Manager
Hosting
Shopify

Company

Headquarters
Memphis

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on powrparts.com, including 9 speed issues, 3 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