Ship Car Pros
Need Reliable Car Shipping From West Virginia To Georgia? Skip The 593-Mile Drive! Delivery 1 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
Your analytics endpoint is completely offline, so you can't track which referral forms convert.
As a referral intermediary, understanding which transport requests lead to successful provider matches is critical for optimizing your matching algorithm and identifying drop-off points in your submission flow. Currently, you're flying blind on customer behavior.
CORS misconfiguration is blocking analytics data from even reaching your tracking service.
Even if your umami endpoint were online, the CORS policy prevents customer interaction data from being sent. This means you can't measure referral submission rates, provider match engagement, or form abandonment—all metrics vital for a referral business.
A missing 404 resource is silently breaking core features of your car shipping request form.
Your referral service depends entirely on customers submitting accurate vehicle specs and location data. If form components are failing to load, customers may abandon requests or submit incomplete information, degrading the quality of matches your providers receive.
Generic network failures suggest your Netlify hosting or third-party service integrations are unstable.
For a referral platform where customers are entrusting you with sensitive transport details (VIN, addresses, preferred dates), reliability is paramount. Network instability erodes trust and can cause referral requests to be lost entirely.
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 through their platform to be matched with appropriate shipping providers. The service collects customer information including contact details, vehicle specifications (make, model, year, VIN, condition), pickup/delivery locations, and preferred dates to facilitate these connections. According to the Privacy Policy, the platform uses this information to improve their referral matching process and connect customers with suitable transport providers in their network. The service emphasizes it is a referral intermediary 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 services specifically from West Virginia to Georgia. The page states it provides 'Door-to-door auto transport with real-time tracking and dedicated support,' with an average route distance of 593 miles and estimated transit time of 1 day. The primary call-to-action is to call for a quote at (866) 588-6325.
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 (89 chars)
Your page title for West Virginia to Georgia shipping routes is 89 characters long, exceeding the recommended 60-character limit, which means search engines will truncate it when displaying your referral service in search results for car shipping queries.
Found: 89 characters
Accessibility
100/100Functional
100/100Technical Health
Network request failed: https://umami-autotransport.monotrkmain.com/api/send
Your analytics endpoint at umami-autotransport.monotrkmain.com is failing to receive customer interaction data from your referral platform, preventing you from tracking how customers navigate your shipping request process and engage with provider matches.
CORS error detected
CORS configuration errors are preventing your analytics service from properly tracking referral submissions and customer interactions with transport provider matches, hindering your ability to monitor platform performance and user behavior.
Failed to load resource: the server responded with a status of 404 ()
A required resource failed to load with a 404 error, which may prevent certain features of your car shipping referral form or matching interface from functioning properly.
Access to fetch at 'https://umami-autotransport.monotrkmain.com/api/send' fro...
Your analytics tracking for user interactions and referral submissions is being blocked by CORS policy issues with the umami analytics service, preventing proper collection of data about how customers use your transport request matching platform.
Failed to load resource: net::ERR_FAILED
A network resource failed to load, which could impact the stability and functionality of your car shipping referral service.
Compliance
100/1001 finding suppressed (not relevant to this site type)
Key Metrics
Crawlability
Standards
Improvement Plan
Your referral platform has three critical blockers preventing normal operation, each compounding the others. The most urgent issue is that your umami analytics endpoint (umami-autotransport.monotrkmain.com/api/send) is completely failing—your entire tracking infrastructure for referral submissions is offline. This means you cannot measure whether customers are actually completing transport requests, which provider categories are most requested, or where drop-off occurs. For a referral business, this is like running blind.
The second issue is that even if that endpoint came back online, CORS policy misconfigurations would prevent data from reaching it. Your WordPress analytics script (emoji script) is returning 404 errors, and the broader CORS setup suggests your domain configuration on Netlify doesn't permit cross-origin requests to your analytics service. This needs to be fixed at the infrastructure level.
The third issue is the missing 404 resource in your referral form itself. Without knowing exactly which resource is missing, we can't confirm whether customers can submit vehicle specs, pickup/delivery locations, or dates—the core data your providers need for matching. This must be identified and restored immediately.
Start by checking your Netlify deployment logs to identify which static asset is returning 404. Next, restore your umami analytics endpoint or verify it's properly configured on your hosting provider. Then audit your CORS headers to ensure requests from your form domain can reach both your analytics service and any backend APIs. Finally, implement basic monitoring (uptime checks on your referral form endpoints) so these issues don't go undetected again.
Suggested priority order:
- Network request failed: umami analytics endpoint completely offline
- CORS error blocking analytics data transmission from referral form
- Failed to load resource: missing 404 breaking form functionality
- Generic network failures causing instability in referral submission flow
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.