Ship Car Pros
Need Reliable Car Shipping From Colorado To Vermont? Skip The 1994-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
Critical 404 error is blocking your referral form submission—customers can't request transport matches.
As a referral platform, your core revenue depends on customers successfully submitting transport requests. If the form resource is returning 404, you're losing referral opportunities and provider connections at the point of conversion.
Analytics API is unreachable, so you're blind to whether your matching service is actually converting referrals.
Without tracking referral submissions and provider conversions, you can't measure platform performance, optimize the matching process, or demonstrate ROI to providers. You're operating without visibility into your core business metric.
CORS misconfiguration is blocking Umami analytics from sending conversion data—your tracking layer is silenced.
Even if referrals are happening, the analytics service can't report them back to you. This creates a gap between actual customer activity and what you can measure, audit, or improve.
Generic network failures (net::ERR_FAILED) suggest intermittent infrastructure problems affecting form stability.
For a referral service dependent on reliable form submissions, sporadic network errors will drop requests mid-process, frustrating customers and reducing your match volume without explanation.
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, and must be at least 18 years old to use the platform. The Privacy Policy reveals the company collects customer contact information, vehicle details (make, model, year, VIN, condition), transport logistics (pickup/delivery locations, preferred dates), and special requirements to facilitate these connections. The service appears to operate as a middleman referral platform rather than directly providing transportation itself, as stated in their introduction: 'a referral service designed to connect customers with qualified auto transport and car shipping providers.'
Based on exploring 2 pages across the site
First Impression — How clear is your site?
This website offers car shipping services from Colorado to Vermont. The page explicitly states it provides "Door-to-door auto transport with real-time tracking and dedicated support." The service advertises an average route distance of 1994 miles with an estimated transit time of 4 days.
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 (79 chars)
The page title for Ship Car Pros' main landing page is 79 characters and will be truncated in search results, reducing click-through rates from customers searching for car shipping services from Colorado to Vermont.
Found: 79 characters
Accessibility
100/100Functional
100/100Technical Health
Network request failed: https://umami-autotransport.monotrkmain.com/api/send
The analytics API endpoint for tracking customer referral conversions and user behavior is unreachable, preventing Ship Car Pros from monitoring the effectiveness of their matching service and provider connections.
CORS error detected
CORS misconfiguration is blocking the analytics service that tracks customer referral submissions and provider conversion metrics, preventing Ship Car Pros from understanding how their matching service is performing.
Failed to load resource: the server responded with a status of 404 ()
A critical resource needed for Ship Car Pros' referral form or page functionality is returning a 404 error, which may prevent customers from submitting transport requests or accessing key features.
Access to fetch at 'https://umami-autotransport.monotrkmain.com/api/send' fro...
The analytics tracking service (Umami) used to monitor customer interactions and referral conversions is being blocked by CORS policy, preventing Ship Car Pros from collecting data on how users engage with the transport request submission process.
Failed to load resource: net::ERR_FAILED
A network request required for site functionality has failed, which may impact the ability to load parts of the referral matching interface or customer submission forms.
Compliance
100/1001 finding suppressed (not relevant to this site type)
Key Metrics
Crawlability
Standards
Improvement Plan
Your referral platform is experiencing a critical infrastructure breakdown that's silencing both customer submissions and your ability to track them. The immediate priority is restoring form functionality—the 404 error and network failures are preventing the core transaction (customer submitting a transport request) from completing. This is your highest-impact issue because without successful submissions, you have no referrals to send to providers and no revenue.
Secondly, your analytics layer has collapsed. The Umami API is unreachable, and CORS misconfiguration is preventing data from flowing back to your dashboard even when requests do go through. For a referral platform, losing visibility into conversion metrics means you can't prove the service works, optimize the matching algorithm, or justify provider partnerships. You're essentially operating blind.
The root cause appears to be infrastructure degradation on your Netlify-hosted setup and the monotrkmain.com analytics backend. I recommend: (1) immediately audit and restore the missing 404 resource (likely a critical form endpoint or API route), (2) verify the Umami API endpoint is accessible and responding, and (3) fix CORS headers to allow analytics data to transmit from your frontend to the tracking service. Once forms are submitting again, restore your analytics pipeline so you can measure success.
Third, address the generic network failures by reviewing your server logs for timeouts or dependency failures. These intermittent errors will continue dropping referrals unless the underlying cause is fixed—likely a misconfigured proxy, missing environment variables, or overloaded backend service.
Suggested priority order:
- Failed to load resource returning 404 (referral form/submission endpoint)
- Network request failed: Umami analytics API unreachable
- CORS error blocking analytics service data transmission
- Generic net::ERR_FAILED network failures affecting form stability
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.