Ship Car Pros
Need Reliable Car Shipping From New Mexico To Utah? Skip The 695-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're blind to which referral matches actually convert.
Ship Car Pros depends on understanding customer behavior to optimize provider matching. Without analytics data from your umami-autotransport endpoint, you cannot identify which customer-provider pairs succeed, making it impossible to improve your matching algorithm or prove ROI to transport providers in your network.
Critical 404 errors are breaking the car shipping request form that customers need to submit transport details.
Your primary revenue driver is the referral request submission process. When customers attempt to input their vehicle specifications, pickup/delivery locations, and preferred dates, missing resources prevent form completion, directly losing referrals before they reach your provider network.
CORS policy is blocking your ability to track form submissions and referral conversions across your referral funnel.
Beyond the offline analytics endpoint, CORS restrictions prevent you from measuring how many customers complete transport requests versus drop off mid-form. This data gap makes it impossible to calculate your actual conversion rate or identify where customers abandon the referral process.
Your Utah shipping page title gets cut off in Google, losing clicks from customers searching 'auto transport New Mexico to Utah'.
At 77 characters, your page title exceeds Google's display limit and gets truncated in search results. Since referral services compete heavily on location-specific keywords, a truncated title loses potential customers searching for this specific route before they even click through.
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 suitable providers in their network. The service collects customer information including contact details, vehicle specifications (make, model, year, VIN, condition), pickup/delivery locations, and preferred dates to facilitate these referral matches. According to the Privacy Policy, they also automatically collect device information, IP addresses, and usage data to improve their matching process. The platform requires users to be at least 18 years old and emphasizes that customers must provide accurate information about their vehicles and transport needs.
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 New Mexico to Utah. The page states it offers "Door-to-door auto transport with real-time tracking and dedicated support" with an average route distance of 695 miles and estimated transit time of 1 day. The primary call-to-action is to "Get Your Quote in Minutes" by calling the toll-free 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 (77 chars)
Your page title for the Utah car shipping service is 77 characters, which will be truncated in search results when potential customers search for auto transport from New Mexico to Utah, reducing click-through rates.
Found: 77 characters
Accessibility
100/100Functional
100/100Technical Health
Access to fetch at 'https://umami-autotransport.monotrkmain.com/api/send' fro...
Your analytics tracking for user transport requests and referral matching is blocked by a CORS policy error with your analytics endpoint. This prevents you from collecting data on how customers interact with your shipping quote requests, which impairs your ability to optimize the referral matching process.
Network request failed: https://umami-autotransport.monotrkmain.com/api/send
Your analytics endpoint is failing to receive data from car shipping requests and user interactions. This prevents you from tracking customer behavior patterns needed to improve your provider matching algorithm and service quality.
CORS error detected
Your analytics service is blocked by CORS policy, preventing collection of data on customer transport requests, form submissions, and referral conversions. This significantly impacts your ability to measure referral service performance and optimize the matching process.
Failed to load resource: the server responded with a status of 404 ()
A resource failed to load with a 404 error, which could impact the functionality of the car shipping request form or related features that customers need to submit their transport information.
Failed to load resource: net::ERR_FAILED
A network resource failed to load, which could prevent critical features of the car shipping referral service from functioning properly for customers submitting transport requests.
HTTP 404 on https://shipcarfromnewmexicotoutah.netlify.app/wp-includes/j
WordPress emoji functionality is returning a 404 error. While not critical to core referral matching, this may affect the display of content and comments related to customer reviews or vehicle descriptions.
Compliance
100/100Key Metrics
Crawlability
Standards
Improvement Plan
Ship Car Pros' core vulnerability is the breakdown between customer acquisition and performance measurement. You're losing referrals at the form submission stage due to 404 errors, which means fewer requests to send to your provider network. Simultaneously, your analytics infrastructure is offline, so even when referrals do go through, you cannot track which provider matches succeed or fail. This creates a dangerous blind spot: you're acquiring fewer referrals while unable to optimize the ones you do get.
Start by restoring your form functionality. The 404 errors on critical form resources must be resolved immediately—audit your hosting environment and verify all assets referenced by your shipping quote form are accessible. Test the complete customer journey from landing to form submission to confirm all required files load without errors.
Next, restore your analytics pipeline. Your umami endpoint at umami-autotransport.monotrkmain.com is failing, and CORS policy is preventing data collection. Work with your development team to: (1) verify the analytics server is running, (2) configure CORS headers to allow requests from your main domain, and (3) test that form submissions, provider matches, and referral outcomes are being logged. Without this data, you cannot optimize your matching algorithm or report on service quality to providers.
Finally, address the search visibility issue. Reduce your Utah shipping page title from 77 to 55-60 characters while keeping your target keywords ('auto transport New Mexico Utah'). This ensures the full title displays in search results and improves click-through rates from local searches—a high-value traffic source for referral services.
The recommended sequence is: form functionality (lost revenue today) → analytics restoration (lost insight into what works) → SEO optimization (future traffic recovery). These fixes directly support your referral matching mission by ensuring customers can submit transport requests and you can measure provider performance.
Suggested priority order:
- Failed to load resource: the server responded with a status of 404 () — form submission broken
- Network request failed: https://umami-autotransport.monotrkmain.com/api/send — analytics endpoint offline
- CORS error detected: analytics service blocked by CORS policy
- Access to fetch at 'https://umami-autotransport.monotrkmain.com/api/send' CORS policy error
- Page title too long (77 chars) — truncated in search results
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.