Website review, no card needed

tarranbikes.com logo

tarranbikes.com website review

Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 78 checks

This review found 29 issues worth fixing on tarranbikes.com, 9 of them high impact, across 78 checks. The most urgent: page weight: 16.4 MB in 239 requests. 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
2.4 s1.3 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.4 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.1 s
Oct 3, 20262.2 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20261.8 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
232 ms119 msMay 16Oct 31158 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026185 ms
May 23, 2026183 ms
May 30, 2026180 ms
Jun 6, 2026150 ms
Jun 13, 2026132 ms
Jun 20, 2026148 ms
Jun 27, 2026161 ms
Jul 4, 2026155 ms
Jul 11, 2026158 ms
Jul 18, 2026142 ms
Jul 25, 2026132 ms
Aug 1, 2026136 ms
Aug 8, 2026136 ms
Aug 15, 2026137 ms
Aug 22, 2026137 ms
Aug 29, 2026164 ms
Sep 5, 2026170 ms
Sep 12, 2026219 ms
Sep 19, 2026200 ms
Sep 26, 2026194 ms
Oct 3, 2026195 ms
Oct 10, 2026175 ms
Oct 17, 2026174 ms
Oct 24, 2026162 ms
Oct 31, 2026158 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 tarranbikes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tarranbikes.com at 0.7 s0.7 s
  2. tarranbikes.com at 1.5 s1.5 s
  3. tarranbikes.com at 2.2 s2.2 s
  4. tarranbikes.com at 2.9 s2.9 s
  5. tarranbikes.com at 3.7 s3.7 s
  6. tarranbikes.com at 4.4 s4.4 s
  7. tarranbikes.com at 5.1 s5.1 s
  8. tarranbikes.com at 5.8 s5.8 s

Speed

8 to fix61
  • Reduce unused JavaScript

    1.2 s · 224 KiB

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

  • Improve image delivery

    150 ms · 3.8 MB

    15 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    650 ms · 91 KiB

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

  • Render-blocking requests

    450 ms

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

  • Reduce unused CSS

    300 ms · 49 KiB

    About 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 2.8 s

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

  • LoyaltyLion adds 66 ms

    66 ms

    LoyaltyLion costs a phone 66 ms of main-thread work and 353 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 (reddit, LoyaltyLion and Shopify and others), adding 611 KiB and 248 ms of main-thread time.

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

1 checks passed
  • Server response: 29 ms

    29 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 22.3 s

    22.3 s

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

  • Time to Interactive: 22.4 s

    22.4 s

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

  • Speed Index: 9.7 s

    9.7 s

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

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

    +20%

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

9 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: 1.2 s

    1.2 s

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

  • Real-user INP: 130 ms

    130 ms

    Real visitors wait 130 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: 1.1 s

    1.1 s

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

  • Real-user TTFB: 406 ms

    406 ms

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

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

    -13%

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

  • Cumulative Layout Shift: 0.024

    0.024

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

  • Total Blocking Time: 12 ms

    12 ms

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

Images and page weight

2 to fix60
  • Page weight: 16.4 MB in 239 requests

    16.4 MB

    Your homepage downloads 16.4 MB in 239 requests on a phone: media 8.2 MB (3), images 4.0 MB (29) and fonts 2.3 MB (1). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    81 KiB

    3 images are downloaded at several times the size a phone draws them, for example 20260410-145157.png at 1,248 px wide, shown at 358 px. Resized copies would save about 81 KiB.

  • About 4.6 g of CO₂ per visit

    4.64 g

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

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

Accessibility

6 to fixGoogle 9491
  • 5 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 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).

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 8595
  • No social preview image

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 57 internal links, 14 external

    The homepage links to 57 pages on tarranbikes.com and 14 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Experience automotive-grade mobility. Features a smart E-kickstand, advanced anti-theft security, heavy load capacity, …”.

  • One H1 headline

    Your main headline reads: “TARRAN”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Smart Electric Cargo Bike | Automotive-Grade & E-Kickstand”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://tarranbikes.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 15 pages without an H1

    https://tarranbikes.com/pages/tarran-l1h, https://tarranbikes.com/pages/tarran-l1, https://tarranbikes.com/pages/tarran-t1-pro, https://tarranbikes.com/collections/accessories, https://tarranbikes.com/pages/find-a-dealer and https://tarranbikes.com/pages/support-center 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 33 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 8 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 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 478 words of copy

    The homepage carries about 478 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy Now”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Buy Now”, “Subscribe” and “Join Our User Group”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before 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

    17

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

  • 26 other companies contacted

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

Apps your storefront loads

Loyalty Rewards And Referrals · Klaviyo Email Marketing Sms · Impact Com · Sami B2b Lock · Xcotton Guard · Powerful Form Builder · Sami Wholesale · Post Purchase Protection · Tms Prod V 71ff83e · Wholesale Lock Hide Price · goaffpro.com · amazonaws.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
Analytics
Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on tarranbikes.com, including 13 speed issues, 2 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