Website review, no card needed

segway.la logo

segway.la website review

Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 73 checks

This review found 32 issues worth fixing on segway.la, 7 of them high impact, across 73 checks. The most urgent: page weight: 13.6 MB in 216 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.9 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
149 ms116 msMay 16Oct 31145 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026120 ms
May 23, 2026120 ms
May 30, 2026120 ms
Jun 6, 2026120 ms
Jun 13, 2026121 ms
Jun 20, 2026120 ms
Jun 27, 2026120 ms
Jul 4, 2026122 ms
Jul 11, 2026121 ms
Jul 18, 2026122 ms
Jul 25, 2026125 ms
Aug 1, 2026127 ms
Aug 8, 2026122 ms
Aug 15, 2026125 ms
Aug 22, 2026121 ms
Aug 29, 2026120 ms
Sep 5, 2026121 ms
Sep 12, 2026121 ms
Sep 19, 2026124 ms
Sep 26, 2026128 ms
Oct 3, 2026129 ms
Oct 10, 2026133 ms
Oct 17, 2026135 ms
Oct 24, 2026141 ms
Oct 31, 2026145 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 segway.la (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. segway.la at 0.6 s0.6 s
  2. segway.la at 1.1 s1.1 s
  3. segway.la at 1.7 s1.7 s
  4. segway.la at 2.2 s2.2 s
  5. segway.la at 2.8 s2.8 s
  6. segway.la at 3.3 s3.3 s
  7. segway.la at 3.9 s3.9 s
  8. segway.la at 4.5 s4.5 s

Speed

10 to fix67
  • Render-blocking requests

    1.4 s

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

  • Reduce unused JavaScript

    600 ms · 908 KiB

    About 908 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Mobile performance score: 67

    67/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Klaviyo and Google Tag Manager and others), adding 1.4 MB and 715 ms of main-thread time.

  • Improve image delivery

    150 ms · 537 KiB

    10 images could be 537 KiB 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.

  • Use efficient cache lifetimes

    100 ms · 287 KiB

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

  • Main-thread work: 3.5 s

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

  • Google CDN adds 197 ms

    197 ms

    Google CDN costs a phone 197 ms of main-thread work and 299 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.

  • 2,159 HTML elements

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

  • Klaviyo adds 127 ms

    127 ms

    Klaviyo costs a phone 127 ms of main-thread work and 311 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.

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    120 ms · 23 KiB

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

  • Legacy JavaScript

    32 KiB

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

10 to fix33
  • 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: 16.8 s

    16.8 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Largest Contentful Paint: 5.0 s

    5.0 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user INP: 231 ms

    231 ms

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Total Blocking Time: 280 ms

    280 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

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

    +19%

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

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

    +11%

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

2 checks passed
  • Real-user CLS: 0.04

    0.04

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

  • Cumulative Layout Shift: 0.033

    0.033

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

Images and page weight

1 to fix0
  • Page weight: 13.6 MB in 216 requests

    13.6 MB

    Your homepage downloads 13.6 MB in 216 requests on a phone: media 8.7 MB (1), images 2.5 MB (22) and scripts 1.4 MB (83). Under 2 MB keeps phones on slow connections fast.

  • About 3.8 g of CO₂ per visit

    3.85 g

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

Accessibility

3 to fix92
  • 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.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 link without text

    1 link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (7 elements).

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

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • Every image has alt text

    All 60 images in the HTML carry an alt attribute.

SEO

2 to fixGoogle 10088
  • Title is short (18 characters)

    Your title is only 18 characters: “Segway Los Angeles”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (181 characters)

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

  • 106 internal links, 3 external

    The homepage links to 106 pages on segway.la and 3 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Meet the New MAX G3 Plus”.

  • Canonical URL set

    The canonical URL is https://www.segway.la/.

  • Structured data in place

    Structured data found: BreadcrumbList, OnlineStore 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://www.segway.la/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

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

  • llms.txt published

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

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.segway.la/products/segway-max-g3-plus-electric-scooter, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages without a meta description

    https://www.segway.la/pages/contact-us, https://www.segway.la/collections/superscooter and https://www.segway.la/collections/ebike have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • 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 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 console error

    1 error was logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 429 (Too Many Requests)”).

1 checks passed
  • 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.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 391 words of visible text.

5 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop Now”, “Learn More About MAX G3 Plus” and “Shop GT3 Pro”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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 segway.la, 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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Tinyseo Ai Seo Speed · Simprosys Google Shopping Feed · Okendo · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Assortion · Back In Stock · joinclyde.com · cloudfront.net · hubapi.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

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Santa Monica

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on segway.la, including 20 speed issues, 2 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