ride509.com website review

Not measured in this review.

• Tap response (INP) held steady for real visitors

  -5%

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

• Page weight: 3.3 MB

  3.3 MB

  Your homepage downloads 3.3 MB on a phone, 837 KiB of it images (25%). Under 2 MB keeps phones on slow connections fast.

• 8 images below the first screen load straight away

  8 images further down the page (511 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• 1 image far larger than shown

  13 KiB

  1 image is downloaded at several times the size a phone draws it, for example ether-mono-banner-1026.jpg at 1,200 px wide, shown at 358 px. Resized copies would save about 13 KiB.

  Elements (1)

• About 0.9 g of CO₂ per visit

  0.93 g

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

• ARIA attributes must conform to valid names (16 elements)

  ARIA attributes must conform to valid names: 16 elements on the page fail this check, rated critical by axe-core.

  Elements (3)

• 15 tap targets too small

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

  Elements (3)

• 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 (1)

• 9 images without alt text

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

  View sourceElements (3)

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

  Elements (3)

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

  Elements (1)

• 1 link without text

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

  Elements (1)

• 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 (1)

• Headings skip levels

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

  View source

• Title is short (27 characters)

  Your title is only 27 characters: “509 - Fueling Your Passion™”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• Meta description is long (162 characters)

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

  View source

• 369 internal links, 12 external

  The homepage links to 369 pages on ride509.com and 12 external pages.

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

• No llms.txt

  There is no https://ride509.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.

• 1 page without a meta description

  https://ride509.com/pages/product-feedback has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 1 page without an H1

  https://ride509.com/pages/product-feedback has 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 133 found) and read each the way a search engine does.

• 8 broken images

  8 images failed to load on a phone, for example https://ride509.com/.

• 13 small tap targets

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

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

  The homepage carries about 803 words of visible text.

• 2 trackers load before any consent

  2

  Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

• 12 cookies set on arrival

  12

  Opening the homepage sets 12 cookies (measured from a US location before any click).

• 31 other companies contacted

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