Website review, no card needed
pedalelectric.com website review
Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 94 checks
This review found 43 issues worth fixing on pedalelectric.com, 11 of them high impact, across 94 checks. The most urgent: 13,586 HTML elements. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79C- #44,586 of 98,215 reviewed websitesbeats 49%
- #28,428 of 53,591 online storesbeats 41%
- #27,195 of 48,604 Shopify storesbeats 38%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.4 s |
| Oct 31, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 164 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 163 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 163 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 169 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 171 ms |
| Aug 15, 2026 | 175 ms |
| Aug 22, 2026 | 178 ms |
| Aug 29, 2026 | 172 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 175 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 186 ms |
| Oct 3, 2026 | 187 ms |
| Oct 10, 2026 | 183 ms |
| Oct 17, 2026 | 179 ms |
| Oct 24, 2026 | 171 ms |
| Oct 31, 2026 | 170 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
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.2 s
4.9 s
5.6 s
Speed
13,586 HTML elements
The page has 13,586 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and reddit and others), adding 1.8 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
450 ms · 954 KiBAbout 954 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
1.1 MB23 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
770 KiB25 files are served with short cache lifetimes, so returning visitors download them again (770 KiB).
Google Tag Manager adds 500 ms
500 msGoogle Tag Manager costs a phone 500 ms of main-thread work and 705 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
350 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
alia-prod.com adds 268 ms
268 msalia-prod.com costs a phone 268 ms of main-thread work and 337 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.
rebuyengine.com adds 107 ms
107 msrebuyengine.com costs a phone 107 ms of main-thread work and 297 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 216 ms. During a long task the page ignores taps.
Legacy JavaScript
100 KiBPolyfills for old browsers add 100 KiB JavaScript that modern phones do not need.
Reduce unused CSS
51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 34 ms
34 msYour server sent the HTML in 34 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 37.5 s
37.5 sThe page becomes fully interactive after 37.5 s. Good is under 3.8 s.
Speed Index: 13.7 s
13.7 sVisually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 497 ms
497 msScripts block taps and scrolling for 497 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 164 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 187 ms
187 msReal visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 597 ms
597 msReal visitors wait 597 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 2.5 s
2.5 sYour largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Premium Crafted Electric Bikes”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.1 MB in 426 requests
9.1 MBYour homepage downloads 9.1 MB in 426 requests on a phone: images 5.3 MB (159), scripts 2.6 MB (82) and other files 836 KiB (166). Under 2 MB keeps phones on slow connections fast.
About 2.6 g of CO₂ per visit
2.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.59 g of CO₂e: 310.5 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Hidden but focusable
41 elements hidden from screen readers can still receive keyboard focus.
28 text elements with low contrast
28 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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 (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 192 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
One H1 headline
Your <h1> is empty.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
399 internal links, 0 external
The homepage links to 399 pages on pedalelectric.com and 0 external pages.
5 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “In the market for an electric bike? Pedal Electric offers three luxury e-bikes designed for the long haul & all conditi…”.
Title: 52 characters
Your title is a healthy 52 characters: “Electric Pedal Bike: Premium E-Bike | Pedal Electric”.
Canonical URL set
The canonical URL is https://pedalelectric.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://pedalelectric.com/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,272 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pedalelectric.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages share 2 titles
https://pedalelectric.com/collections/s-t, https://pedalelectric.com/products/the-s-t-terra-brown, https://pedalelectric.com/products/the-s-t and https://pedalelectric.com/products/the-s-t-bone-white all use the title “S/T”, and 1 other title repeat too. 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://pedalelectric.com/pages/discounts, https://pedalelectric.com/collections/all-products-pedal, https://pedalelectric.com/collections/mega-menu-collection, https://pedalelectric.com/collections/h-t, https://pedalelectric.com/collections/s-t and https://pedalelectric.com/collections/core and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://pedalelectric.com/products/all-wheel-drive-s, https://pedalelectric.com/products/pedal-electric-awd, https://pedalelectric.com/products/all-wheel-drive-s-vintage-gloss and https://pedalelectric.com/products/all-wheel-drive-grn use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://pedalelectric.com/pages/discounts, https://pedalelectric.com/collections/all-products-pedal, https://pedalelectric.com/collections/mega-menu-collection, https://pedalelectric.com/collections/h-t, https://pedalelectric.com/collections/s-t and https://pedalelectric.com/collections/core and 9 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 84 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
153 small tap targets
153 of 277 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
58 distorted images
58 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 1,544 words of copy
The homepage carries about 1,544 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “🏁 Early Access | Shop up to $1,200 OFF” and “Shop Deals”.
13 calls to action
The homepage has 13 calls to action, for example “🏁 Early Access | Shop up to $1,200 OFF”, “Shop All” and “Shop [eco] system”.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
44 other companies contacted
Loading the homepage contacts 44 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 pedalelectric.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Okendo · Klaviyo Email Marketing Sms · Checkmate · Elevar Conversion Tracking · Pedal Electric Extensions · nofraud.com · getsitecontrol.com · attn.tv · govx.com · amazonaws.com · rebuyengine.com
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
- Hosting
- Shopify
Company
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on pedalelectric.com, including 19 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.