Ship Car Pros
Need Reliable Car Shipping From Alabama To Utah? Skip The 1852-Mile Drive! Delivery 4 Days Door-To-Door.
Report generated on April 6, 2026
A note on how to read this
This report is ProdPoke's take on your site — think of it as a first impression from a very opinionated robot. We check real things (load times, broken links, accessibility patterns), but we also try to understand what your site is trying to do and whether the technical details support that goal. Some of our observations might not apply to your specific situation, and that's okay. We're getting sharper with every scan. If something feels off, tell us — it makes us better.
Key Insights for Ship Car Pros
A 404 error is blocking your referral matching interface, preventing customers from submitting transport requests.
Since Ship Car Pros operates entirely on referral submissions, a broken request form directly blocks revenue. Customers calling 866-813-9521 expecting a seamless online experience will abandon the process if they can't complete their vehicle and logistics details online.
CORS misconfiguration blocks all analytics tracking to your Umami backend, leaving you blind to how customers navigate your referral process.
You cannot see which steps customers complete, where they drop off, or which provider matches convert—critical data for optimizing your matching algorithm and sales funnel. This is especially damaging for a referral service where understanding conversion paths directly impacts provider partnerships.
A critical resource failed to load (net::ERR_FAILED), degrading the user experience when customers attempt to enter their vehicle and transport details.
This cascading failure compounds the 404 issue. Even if customers reach your form, missing critical resources prevent smooth data submission, increasing friction at the exact moment you need to capture their transport requirements for provider matching.
Your analytics endpoint (umami-autotransport.monotrkmain.com) is misconfigured and unreachable from your Netlify-hosted site.
POST requests to track customer interactions are failing silently. You're losing visibility into referral request completions, provider match clicks, and phone call triggers—data essential for measuring ROI and scaling your service.
What ProdPoke understands about Ship Car Pros
Ship Car Pros is a referral service that connects customers with qualified auto transport and car shipping providers. Based on the Terms & Conditions page, users submit transport requests to be matched with providers, providing vehicle details (make, model, year, VIN, condition), pickup and delivery locations, and preferred dates. The Privacy Policy confirms the service collects contact information, vehicle specifications, transport logistics, and special requirements to facilitate these referral matches. The site emphasizes quick turnaround, advertising pickups available as early as tomorrow via their toll-free number (866) 813-9521. The business operates as an intermediary platform rather than a direct transport provider.
Based on exploring 2 pages across the site
First Impression — How clear is your site?
This website offers car shipping/auto transport services specifically from Alabama to Utah. The page explicitly states it provides "Door-to-door auto transport with real-time tracking and dedicated support" with an average route distance of 1852 miles and estimated transit time of 4 days. The primary call-to-action is to call for a quote at (866) 813-9521.
This score measures how quickly a first-time visitor understands what your site does — based on visible headings, navigation, and visual hierarchy alone.
Overall Score
Strong foundation.
Performance
100/100SEO
97/100Page title too long (71 chars)
Your page title (71 characters) is too long and will be truncated in Google search results when potential customers search for car shipping services, reducing click-through rates to your referral platform.
Found: 71 characters
Accessibility
100/100Functional
100/100Technical Health
Network request failed: https://umami-autotransport.monotrkmain.com/api/send
POST requests to your analytics endpoint (umami-autotransport.monotrkmain.com) are failing completely, preventing tracking of customer interactions with your referral request forms and provider listings.
CORS error detected
The analytics tracking service cannot communicate with your site due to CORS configuration errors, blocking data collection about customer referral requests, form completions, and provider matches.
Failed to load resource: the server responded with a status of 404 ()
A resource required for the referral matching interface is returning a 404 error, which may prevent customers from completing their transport request submission or viewing available provider matches.
Access to fetch at 'https://umami-autotransport.monotrkmain.com/api/send' fro...
The analytics tracking service (Umami) cannot send user behavior data due to a CORS policy mismatch between your Netlify-hosted site and the analytics backend. This blocks visibility into how potential customers navigate your referral request process.
Failed to load resource: net::ERR_FAILED
A critical resource failed to load, likely impacting the user experience when customers attempt to submit their vehicle and transport details for provider matching.
Compliance
100/1001 finding suppressed (not relevant to this site type)
Key Metrics
Crawlability
Standards
Improvement Plan
Ship Car Pros faces a critical trio of interconnected issues that directly threaten customer conversions. Your referral matching system—the core of your business—has a broken 404 resource preventing customers from submitting transport requests, combined with missing critical assets that degrade the experience. These aren't cosmetic issues; they're blocking the exact workflows customers need to complete to generate provider matches and sales.
Second, your analytics infrastructure is completely non-functional due to CORS misconfiguration between your Netlify site and the Umami backend. This means you cannot track whether customers are completing referral forms, which providers they select, or where drop-off occurs. For a referral service, this blindness is expensive—you cannot optimize matching quality, identify high-converting provider combinations, or measure campaign effectiveness.
Your remediation sequence should be: (1) immediately restore the 404 resource in your referral matching interface and verify all assets load correctly end-to-end; (2) test the complete form submission flow manually before considering it fixed; (3) resolve the CORS policy mismatch between Netlify and umami-autotransport.monotrkmain.com by adjusting Access-Control-Allow-Origin headers or redeploying your analytics endpoint with correct origin allowlists; (4) verify POST requests to the analytics endpoint succeed and telemetry flows for form completions and provider selections.
Once fixed, prioritize monitoring these systems daily. A referral service lives or dies by form completion rates and provider match visibility. Set alerts for 404s and failed analytics POSTs, and establish a weekly review of customer conversion metrics to ensure the matching logic is working as intended. The quick turnaround advantage you advertise (pickups as early as tomorrow) only converts if customers can actually submit their requests without friction.
Suggested priority order:
- Failed to load resource: the server responded with a status of 404 (referral matching interface)
- Failed to load resource: net::ERR_FAILED (critical resources)
- CORS error: Analytics endpoint POST requests failing to umami-autotransport.monotrkmain.com
- Access to fetch CORS policy mismatch blocking Umami analytics data collection
This is your site? Get the full picture.
Claim this report to unlock ongoing monitoring, deeper analysis, and actionable alerts.
What is ProdPoke?Automated analysis generated on April 6, 2026. Not professional advice. Contact us to modify or remove this report.