Programmable

Website review, no card needed

enertor.com logo

enertor.com website review

Visit site (opens in a new tab)Reviewed 10 November 202622 issues · 77 checks

This review found 22 issues worth fixing on enertor.com, 7 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

92A

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.8 s738 msMay 23Nov 7885 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.5 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.1 s
Aug 22, 20261.0 s
Aug 29, 2026997 ms
Sep 5, 2026974 ms
Sep 12, 2026988 ms
Sep 19, 2026965 ms
Sep 26, 2026946 ms
Oct 3, 2026922 ms
Oct 10, 2026864 ms
Oct 17, 2026863 ms
Oct 24, 2026856 ms
Oct 31, 2026874 ms
Nov 7, 2026885 ms
Real-visitor tap response (INP)75th percentile, phones
286 ms86 msMay 23Nov 7261 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026109 ms
May 30, 2026109 ms
Jun 6, 2026110 ms
Jun 13, 2026113 ms
Jun 20, 2026120 ms
Jun 27, 2026124 ms
Jul 4, 2026130 ms
Jul 11, 2026135 ms
Jul 18, 2026130 ms
Jul 25, 2026127 ms
Aug 1, 2026121 ms
Aug 8, 2026130 ms
Aug 15, 2026150 ms
Aug 22, 2026177 ms
Aug 29, 2026224 ms
Sep 5, 2026239 ms
Sep 12, 2026250 ms
Sep 19, 2026258 ms
Sep 26, 2026260 ms
Oct 3, 2026261 ms
Oct 10, 2026256 ms
Oct 17, 2026262 ms
Oct 24, 2026263 ms
Oct 31, 2026262 ms
Nov 7, 2026261 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

enertor.com (opens in a new tab)
Full-page screenshot of enertor.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. enertor.com at 0.4 s0.4 s
  2. enertor.com at 0.8 s0.8 s
  3. enertor.com at 1.1 s1.1 s
  4. enertor.com at 1.5 s1.5 s
  5. enertor.com at 1.9 s1.9 s
  6. enertor.com at 2.3 s2.3 s
  7. enertor.com at 2.6 s2.6 s
  8. enertor.com at 3.0 s3.0 s

Speed

2 to fix100

  • 5,025 HTML elements

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

  • Render-blocking requests

    900 ms

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

  • Improve image delivery

    91 KiB

    4 images could be 91 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    18 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Fonts, Shopify and ContentSquare and others), adding 124 KiB and 0 ms of main-thread time.

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

3 checks passed

  • Mobile performance score: 100

    100/100

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

  • Main-thread work: 0.8 s

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

  • Server response: 67 ms

    67 ms

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

Core Web Vitals

3 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 INP: 272 ms

    272 ms

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

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

    +140%

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

11 checks passed

  • Real-user LCP: 0.9 s

    0.9 s

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

  • 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 524 ms

    524 ms

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

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

    -39%

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Speed Index: 2.1 s

    2.1 s

    Visually, the page fills in at 2.1 s (Speed Index), inside the 3.4 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.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

  • Total Blocking Time: 6 ms

    6 ms

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

  • Time to Interactive: 1.4 s

    1.4 s

    The page is fully interactive after 1.4 s.

Images and page weight

1 to fix97

  • An image on the first screen is lazy-loaded

    hero-trail-runners.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).

  • About 0.6 g of CO₂ per visit

    0.55 g

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

3 checks passed

  • Page weight: 2.0 MB in 97 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 97 requests on a phone: media 842 KiB (1), images 655 KiB (16) and scripts 259 KiB (38). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8190

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 8 tap targets too small

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

  • Scrollable region must have keyboard access (4 elements)

    Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

  • 5 images without alt text

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed

  • 52 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295

  • One H1 headline

    Your <h1> is empty.

  • 53 internal links, 13 external

    The homepage links to 53 pages on enertor.com and 13 external pages.

7 checks passed

  • Meta description: 136 characters

    Your meta description is 136 characters: “Relieve pain and prevent injuries with Enertor's shock absorbing Running Insoles and Recovery Slides. Used by the world…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Enertor | Shock-Absorbing Running Insoles & Recovery Slides”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, 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://enertor.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix71

  • 2 pages point its canonical at the homepage

    https://enertor.com/products/enertor-recovery-slides and https://enertor.com/products/run-recover-bundle declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://enertor.com/products/enertor-recovery-slides and https://enertor.com/products/run-recover-bundle all use the title “Enertor | Shock-Absorbing Running Insoles & Recovery Slides”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://enertor.com/collections/cart-upsell, https://enertor.com/policies/shipping-policy, https://enertor.com/pages/science, https://enertor.com/pages/about-us, https://enertor.com/collections/insoles-1 and https://enertor.com/pages/reviews and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://enertor.com/products/enertor-recovery-slides and https://enertor.com/products/run-recover-bundle use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://enertor.com/collections/all, https://enertor.com/collections/cart-upsell, https://enertor.com/pages/science, https://enertor.com/pages/about-us, https://enertor.com/collections/insoles-1 and https://enertor.com/pages/reviews and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed

  • Linked pages load

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

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

  • 5 small tap targets

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

2 checks passed

  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100

  • About 1,309 words of copy

    The homepage carries about 1,309 words of visible text.

7 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP INSOLES” and “SHOP RECOVERY SLIDES”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop”, “Shop Insoles” and “Shop Recovery Slides”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 54 testimonial or review blocks, a star rating, 5 trust badges and “6,600+ reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • 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

  • 1 tracker load before any consent

    1

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

  • 6 cookies set on arrival

    6

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

  • 7 other companies contacted

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

Apps your storefront loads

Tinycookie · Triplewhale · Klaviyo Email Marketing Sms · Selleasy · Dealeasy · Omnisend · loox.io · adroll.com · zigpoll.com · snapchat.com · omnisnippet1.com · rechargecdn.com · cart-bot.net

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

Framework
jQuery
E-commerce
Shopify
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 22 issues on enertor.com, including 5 speed issues and 1 SEO issue. 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