Ship Car Pros
Need Reliable Car Shipping From Montana To Connecticut? Skip The 2187-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
Your referral form has a 404 error blocking customer transport requests entirely
As a referral service, your core product is the request submission form. When customers can't complete their transport queries, they can't be matched with providers—directly breaking your business model.
CORS policy is preventing you from tracking any customer referral conversions or provider matches
You're collecting detailed vehicle and logistics data, but your analytics endpoint is completely blocked. You have no visibility into which referral matches succeed, fail, or convert—making it impossible to optimize your matching algorithm or measure ROI.
A secondary resource is failing to load, potentially degrading the provider discovery experience
Customers trying to browse available auto transport providers may see incomplete or missing options, reducing their confidence in your service and likelihood of completing a referral.
WordPress emoji 404 errors reveal misconfiguration on your Netlify deployment affecting page load speed
Slow pages during the transport request process increase abandonment. Your Netlify setup isn't correctly serving WordPress assets, creating friction at the moment customers decide whether to submit their shipment details.
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 must be at least 18 years old to use the service. The Privacy Policy indicates the company collects customer information including contact details, vehicle specifications (make, model, year, VIN, condition), transport logistics (pickup/delivery locations and preferred dates), and special transport requirements. The service appears to operate as a middleman platform that gathers customer transport needs and connects them with a network of auto transport providers, collecting data to improve their referral matching process.
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 Montana to Connecticut. The site explicitly states it offers "Door-to-door auto transport with real-time tracking and dedicated support," with an average route distance of 2187 miles and an estimated transit time of 4 days. The main call-to-action is to "Get Your Quote in Minutes" by calling the provided phone number.
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 (85 chars)
Your page title for this car shipping route is 85 characters long and will be truncated in search results, reducing visibility when potential customers search for 'ship car from Montana to Connecticut' or similar transport queries.
Found: 85 characters
Accessibility
100/100Functional
100/100Technical Health
Network request failed: https://umami-autotransport.monotrkmain.com/api/send
The analytics endpoint for tracking customer transport requests and referral conversions is failing completely, preventing the platform from monitoring how customers interact with the provider matching system.
CORS error detected
Your customer analytics and referral tracking system is completely blocked by CORS configuration errors, preventing the platform from monitoring customer transport requests, provider matches, and referral conversion data.
Failed to load resource: the server responded with a status of 404 ()
A critical resource needed for the car shipping referral form or customer request submission is returning a 404 error, which could prevent users from completing transport requests or accessing key platform features.
Access to fetch at 'https://umami-autotransport.monotrkmain.com/api/send' fro...
Your analytics tracking for customer transport requests and referral activity is blocked by CORS policy errors, preventing the platform from properly logging user interactions when customers submit car shipping quotes or transport details.
Failed to load resource: net::ERR_FAILED
A network resource failed to load, which may impact the referral matching experience or prevent customers from seeing available 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 broken in ways that directly impact revenue. The most critical issue is the 404 error on a resource needed for the car shipping request form—this is preventing customers from submitting transport details, which means zero referrals are being generated. This must be your immediate priority: identify which form endpoint is returning 404 and restore it.
Simultaneously, your analytics infrastructure is completely non-functional due to CORS errors blocking the Umami tracking endpoint. This means you're flying blind—you don't know if your provider matches are actually working, which referrals convert, or where customers drop off. Without this data, you can't improve your matching algorithm or make informed business decisions. Fix the CORS configuration on your analytics endpoint immediately after restoring the form.
The secondary resource failure (net::ERR_FAILED) is preventing some customers from viewing available providers. While you're fixing the critical issues, investigate this resource and determine if it's essential to the provider discovery flow. If it is, prioritize it in your fixes.
Finally, address the WordPress emoji configuration issue on your Netlify deployment. While lower-impact than the form and analytics failures, it's a symptom of broader configuration problems. Pages are likely loading slower than they should during the critical moment when customers are filling out their transport details, contributing to abandonment.
Start with the form 404 (immediate revenue impact), then CORS analytics (business intelligence), then secondary resource failure (user experience), then WordPress configuration (performance optimization). Each fix will restore critical platform functionality.
Suggested priority order:
- Failed to load resource returning 404 on car shipping referral form
- CORS policy blocking analytics endpoint for referral conversions
- Network resource failure (net::ERR_FAILED) preventing provider display
- WordPress emoji 404 errors and Netlify configuration issues
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.