Website review, no card needed

rapilockoutdoor.com logo

rapilockoutdoor.com website review

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

This review found 32 issues worth fixing on rapilockoutdoor.com, 12 of them high impact, across 73 checks. The most urgent: avoid multiple page redirects. 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

Full-page screenshot of rapilockoutdoor.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rapilockoutdoor.com at 0.4 s0.4 s
  2. rapilockoutdoor.com at 0.8 s0.8 s
  3. rapilockoutdoor.com at 1.1 s1.1 s
  4. rapilockoutdoor.com at 1.5 s1.5 s
  5. rapilockoutdoor.com at 1.9 s1.9 s
  6. rapilockoutdoor.com at 2.3 s2.3 s
  7. rapilockoutdoor.com at 2.6 s2.6 s
  8. rapilockoutdoor.com at 3.0 s3.0 s

Speed

7 to fix67
  • Avoid multiple page redirects

    20.0 s

    The page goes through 2 redirects before it starts loading, costing about 20.0 s. Link and advertise the final URL directly.

  • Improve image delivery

    2.4 s · 1.9 MB

    6 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

  • Reduce unused JavaScript

    1.6 s · 195 KiB

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

  • Main-thread work: 4.4 s

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

  • Mobile performance score: 67

    67/100

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

  • Render-blocking requests

    450 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

  • Shopify adds 159 ms

    159 ms

    Shopify costs a phone 159 ms of main-thread work and 450 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Shopify, Hexton and Google CDN and others), adding 609 KiB and 233 ms of main-thread time.

  • Document request latency

    200 ms

    The HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Use efficient cache lifetimes

    150 ms · 31 KiB

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

  • Minify JavaScript

    150 ms · 12 KiB

    12 KiB could be saved by minifying JavaScript.

  • 2 long tasks on the main thread

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

  • 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: 7 ms

    7 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 27.9 s

    27.9 s

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

  • Time to Interactive: 28.9 s

    28.9 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 66 ms

    66 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 7.9 MB in 527 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 527 requests on a phone: images 5.1 MB (38), scripts 1.4 MB (252) and other files 1.1 MB (208). Under 2 MB keeps phones on slow connections fast.

  • About 2.2 g of CO₂ per visit

    2.24 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.24 g of CO₂e: 268.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

3 to fixGoogle 8596
  • 3 images without alt text

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

  • 19 links without text

    19 visible links have no text or label, so screen readers cannot say where they go.

  • 2 tap targets too small

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 9278
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “RapiLock — Universal Thru Axles & Twist-Lock Quick Release for Road &”.

  • Meta description is long (206 characters)

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

  • 77 internal links, 4 external

    The homepage links to 77 pages on rapilockoutdoor.com and 4 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • 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://rapilockoutdoor.com/sitemap.xml.

AI search readiness

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

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

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

  • llms.txt published

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

Other pages

4 to fix81
  • 2 pages share a title

    https://rapilockoutdoor.com/collections/axles and https://rapilockoutdoor.com/collections/road-disc-thru-axles all use the title “Road Disc Thru Axles — Universal Fit, Tool-Free Design | RapiLock”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://rapilockoutdoor.com/collections/trailer and https://rapilockoutdoor.com/collections/quik-axle have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://rapilockoutdoor.com/collections/axles and https://rapilockoutdoor.com/collections/road-disc-thru-axles use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://rapilockoutdoor.com/collections/axles and https://rapilockoutdoor.com/pages/contact 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 45 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • Only about 205 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

2 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “CONTACT US”, “Shop Now” and “Shop the collection”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 1 of them by other companies (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.

  • 14 other companies contacted

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

Apps your storefront loads

Sami B2b Lock · Sami Wholesale · Tms Prod V 71ff83e · Wholesale Lock Hide Price

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
jQuery
E-commerce
Shopify
Hosting
Shopify

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 rapilockoutdoor.com, including 11 speed issues, 3 SEO issues and 7 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