Website review, no card needed

gpxmoto.com logo

gpxmoto.com website review

Visit site (opens in a new tab)Reviewed 24 October 202638 issues · 84 checks

This review found 38 issues worth fixing on gpxmoto.com, 14 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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 s820 msMay 2Oct 17885 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026928 ms
May 9, 2026918 ms
May 16, 2026921 ms
May 23, 2026921 ms
May 30, 2026933 ms
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 2026916 ms
Jul 25, 2026887 ms
Aug 1, 2026865 ms
Aug 8, 2026855 ms
Aug 15, 2026907 ms
Aug 22, 2026939 ms
Aug 29, 20261.0 s
Sep 5, 20261.0 s
Sep 12, 2026942 ms
Sep 19, 2026933 ms
Sep 26, 2026881 ms
Oct 3, 2026878 ms
Oct 10, 2026885 ms
Oct 17, 2026885 ms
Real-visitor tap response (INP)75th percentile, phones
68 ms60 msMay 2Oct 1762 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202666 ms
May 9, 202666 ms
May 16, 202664 ms
May 23, 202663 ms
May 30, 202664 ms
Jun 6, 202664 ms
Jun 13, 202663 ms
Jun 20, 202663 ms
Jun 27, 202667 ms
Jul 4, 202666 ms
Jul 11, 202667 ms
Jul 18, 202665 ms
Jul 25, 202662 ms
Aug 1, 202661 ms
Aug 8, 202662 ms
Aug 15, 202662 ms
Aug 22, 202662 ms
Aug 29, 202663 ms
Sep 5, 202662 ms
Sep 12, 202663 ms
Sep 19, 202663 ms
Sep 26, 202663 ms
Oct 3, 202663 ms
Oct 10, 202662 ms
Oct 17, 202662 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 gpxmoto.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gpxmoto.com at 0.6 s0.6 s
  2. gpxmoto.com at 1.2 s1.2 s
  3. gpxmoto.com at 1.9 s1.9 s
  4. gpxmoto.com at 2.5 s2.5 s
  5. gpxmoto.com at 3.1 s3.1 s
  6. gpxmoto.com at 3.7 s3.7 s
  7. gpxmoto.com at 4.4 s4.4 s
  8. gpxmoto.com at 5.0 s5.0 s

Speed

13 to fix47
  • Reduce unused JavaScript

    6.3 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Use efficient cache lifetimes

    1.1 s · 363 KiB

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47 (desktop: 71). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, Google CDN and podium.com and others), adding 3.6 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    910 ms · 161 KiB

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

  • Squarespace adds 526 ms

    526 ms

    Squarespace costs a phone 526 ms of main-thread work and 1.2 MB 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.

  • Improve image delivery

    150 ms · 426 KiB

    9 images could be 426 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.

  • Legacy JavaScript

    300 ms · 119 KiB

    Polyfills for old browsers add 119 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Google CDN adds 287 ms

    287 ms

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

  • Main-thread work: 3.2 s

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

  • podium.com adds 160 ms

    160 ms

    podium.com costs a phone 160 ms of main-thread work and 539 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.

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 723 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.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

1 checks passed
  • Server response: 75 ms

    75 ms

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

Core Web Vitals

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

  • First Contentful Paint: 15.2 s

    15.2 s

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

  • Largest Contentful Paint: 20.3 s

    20.3 s

    Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AFFORDABLE, QUALITY OFF-ROAD MOTORCYCLES”.

  • Speed Index: 15.2 s

    15.2 s

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

  • Time to Interactive: 22.0 s

    22.0 s

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

  • Real-user CLS: 0.20

    0.20

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

  • Total Blocking Time: 321 ms

    321 ms

    Scripts block taps and scrolling for 321 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

    -6%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

5 checks passed
  • 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: 54 ms

    54 ms

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 442 ms

    442 ms

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

  • Cumulative Layout Shift: 0.062

    0.062

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

Images and page weight

1 to fix85
  • Page weight: 4.0 MB in 129 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 129 requests on a phone: scripts 2.1 MB (67), images 741 KiB (11) and other files 439 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (40 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.13 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.13 g of CO₂e: 135.8 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 are sized for phones

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

Accessibility

2 to fixGoogle 9597
  • 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.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 9274
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (12 characters)

    Your title is only 12 characters: “GPX Moto USA”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“AFFORDABLE, QUALITY OFF-ROAD MOTORCYCLES” and “LATEST NEWS”). One clear main headline is easier for people and search engines.

  • Structured data has 3 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 3 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/648bcf26627c2c54dc8…”.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 49 internal links, 0 external

    The homepage links to 49 pages on gpxmoto.com and 0 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.gpxmoto.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://www.gpxmoto.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.gpxmoto.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 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 (296 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.gpxmoto.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.gpxmoto.com/home all use the title “GPX Moto USA”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.gpxmoto.com/about, https://www.gpxmoto.com/current-models, https://www.gpxmoto.com/latest-news, https://www.gpxmoto.com/support, https://www.gpxmoto.com/store and https://www.gpxmoto.com/dealers and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.gpxmoto.com/store has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.gpxmoto.com/current-models, https://www.gpxmoto.com/latest-news/new-dealer-announcement-scuderia-west and https://www.gpxmoto.com/home have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix70
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • Only about 213 words

    The homepage has only about 213 words of visible text; thin pages give Google and first-time buyers little to go on.

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

6 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop Now” and “Sign Up”.

  • 1 short form

    A short form (3 fields at most) is 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.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 17 other companies contacted

    Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 gpxmoto.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

CMS
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on gpxmoto.com, including 21 speed issues, 4 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

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