Ship Car Pros
Need Reliable Car Shipping From South Dakota To California? Skip The 1638-Mile Drive! Delivery 3 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
Request matching interface returns 404 errors, blocking customer submissions
As a referral platform, your core value is connecting customers with providers. If the request submission interface is broken, customers can't create transport requests, which directly prevents revenue generation and defeats the platform's purpose.
Analytics tracking completely fails due to CORS and server errors on Umami endpoint
You can't measure which customers actually submit requests, which provider matches convert, or where users drop off. This blindness prevents you from optimizing your matching algorithm or identifying which providers perform best.
Multiple critical network resources fail to load, fragmenting the customer experience
Between the 404 errors and net::ERR_FAILED responses, customers likely encounter partial page loads or broken workflows, increasing bounce rates before they even attempt to request a match.
WordPress static assets (emoji script) missing on Netlify deployment—sign of incomplete build
While cosmetic, this indicates your deployment pipeline may not be fully synced. If static files aren't deploying correctly, critical application files could be silently broken without alerting you.
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 the platform to be matched with providers, and they must be at least 18 years old to use the service. The Privacy Policy indicates the company collects customer contact information, vehicle details (make, model, year, VIN, condition), transport logistics (pickup/delivery locations and preferred dates), and special requirements to facilitate these connections. The service appears to operate as a middleman matching platform rather than directly providing transportation, as it explicitly describes itself as connecting customers with 'qualified auto transport and car shipping providers' in their network.
Based on exploring 2 pages across the site
First Impression — How clear is your site?
This is a car shipping service that transports vehicles from South Dakota to California. The site explicitly states it offers 'Door-to-door auto transport with real-time tracking and dedicated support,' with an average route distance of 1638 miles and estimated transit time of 3 days. The primary call-to-action is to 'Get Your Quote in Minutes' by calling (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 (93 chars)
The page title for your car shipping service is 93 characters long, which will be truncated in Google search results and other search engines, potentially reducing click-through rates for potential customers searching for auto transport services.
Found: 93 characters
Accessibility
100/100Functional
100/100Technical Health
Network request failed: https://umami-autotransport.monotrkmain.com/api/send
Analytics data from customer transport request submissions is failing to send to the tracking server, preventing the platform from monitoring matching performance and user behavior.
CORS error detected
CORS policy blocking prevents analytics from tracking customer transport requests and provider matches, which impacts the platform's ability to monitor service quality and user interactions.
Failed to load resource: the server responded with a status of 404 ()
A resource required for the car shipping request matching interface is returning a 404 error, which may prevent customers from properly submitting transport requests or viewing available providers.
Access to fetch at 'https://umami-autotransport.monotrkmain.com/api/send' fro...
Analytics tracking for customer transport requests is blocked by CORS policy errors, preventing the platform from logging user interactions and transport request submissions.
Failed to load resource: net::ERR_FAILED
A network resource required for the car shipping matching service is failing to load, which may impact core functionality needed for connecting customers with auto transport providers.
Compliance
100/1001 finding suppressed (not relevant to this site type)
Key Metrics
Crawlability
Standards
Improvement Plan
Your referral platform is currently unable to perform its fundamental function: matching customers with transport providers. The most urgent issue is the 404 error on the request matching interface. This isn't a cosmetic bug—it's a complete blocker that prevents customers from submitting transport requests. Start by checking your server logs and Netlify deployment history to identify when this resource stopped loading. Verify the file exists and is being deployed with each build.
Your second priority must be the analytics infrastructure. The Umami tracking server is failing with both CORS errors and request failures. This means you have zero visibility into customer behavior, request submission success rates, or provider matching performance. Without this data, you're flying blind when trying to improve your matching algorithm or identify bottlenecks. Check the Umami server configuration, verify CORS headers are properly set for requests from your domain, and test the `/api/send` endpoint directly.
The third issue—the general net::ERR_FAILED network errors—suggests multiple resources aren't loading. This could indicate DNS issues, certificate problems, or misconfigured API endpoints. Run a comprehensive network audit of your request matching interface to identify all failing resources, then prioritize fixing those that appear during the customer submission workflow.
Finally, address the WordPress deployment issue by ensuring your Netlify build process fully captures all WordPress static assets. While emoji script failures are low-priority, they're a symptom of incomplete deployments that could leave more critical files broken.
Once these issues are resolved, implement monitoring alerts so future outages are caught immediately rather than silently degrading your service.
Suggested priority order:
- Failed to load resource: 404 error on car shipping request matching interface
- Analytics data failing to send to Umami server and CORS policy blocking
- Failed to load resource: net::ERR_FAILED network resource
- WordPress emoji script 404 error and incomplete static file deployment
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.