Ship Car Pros

Need Reliable Car Shipping From Maine To New Mexico? Skip The 2373-Mile Drive! Delivery 5 Days Door-To-Door.

WordPressTailwind CSSNetlify

Report generated on April 6, 2026

shipcarfrommainetonewmexico.netlify.app
Screenshot of shipcarfrommainetonewmexico.netlify.app

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

Missing 404 resource is blocking core transport request form interactions

Customers attempting to submit vehicle details and transport specifics may encounter broken functionality, directly preventing them from connecting with your referral network and generating leads for your provider partners.

Umami analytics server is completely unreachable due to CORS misconfigurations

You're blind to how customers navigate your referral matching process and which form fields cause drop-offs. This data loss prevents you from optimizing the transport request flow that drives your referral business.

Network request failures are occurring on critical customer submission paths

When customers input vehicle details or transport specifics, some data requests are failing silently. This creates unreliable referral matching and may leave transport requests incomplete before reaching your provider network.

Your analytics infrastructure is down, eliminating your ability to measure referral conversion quality

Without device information and usage pattern data flowing to your analytics backend, you cannot track which provider matches result in successful transactions or identify friction points in your matching algorithm.

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. The platform allows users to submit transport requests by providing contact information, vehicle details (make, model, year, VIN, condition), and transport specifics like pickup/delivery locations and preferred dates. The service is designed to match customers with suitable transport providers from their network. Users must be at least 18 years old to use the service, and they agree to provide accurate information about their vehicles and transport needs when submitting requests. The company collects both voluntarily provided information and automatically collected data (such as device information, IP address, and usage patterns) to improve their referral matching process and website functionality.

Based on exploring 2 pages across the site

First Impression — How clear is your site?

95
Crystal clear

This website offers car shipping services from Maine to New Mexico. The page explicitly states it provides "Door-to-door auto transport with real-time tracking and dedicated support." The average route is 2373 miles with an estimated transit time of 5 days, and visitors can "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.

89/ 100

Overall Score

Strong foundation.

Performance

100/100
All clear — no issues found in this category.

SEO

97/100

Page title too long (79 chars)

low

The page title is 79 characters long, exceeding the recommended 60-character limit. When Ship Car Pros' service pages are shared on social media or appear in search results for auto transport services, the title will be truncated, reducing visibility and click-through rates.

Expected: 50-60 characters
Found: 79 characters

Accessibility

100/100
All clear — no issues found in this category.

Functional

100/100
All clear — no issues found in this category.

Technical Health

Failed to load resource: the server responded with a status of 404 ()

medium

A critical resource is missing from the website, preventing some functionality from loading properly. This could affect the transport request form or referral matching interface that customers rely on to connect with car shipping providers.

Failed to load resource: net::ERR_FAILED

medium

A network request failed to complete, which could prevent certain features or data from loading. This may impact the customer experience when submitting vehicle details or transport specifics for the referral matching process.

Network request failed: https://umami-autotransport.monotrkmain.com/api/send

likelymedium

The analytics data submission to the Umami tracking service is failing consistently. This prevents Ship Car Pros from collecting usage patterns and device information needed to optimize the referral matching algorithm and website performance.

Access to fetch at 'https://umami-autotransport.monotrkmain.com/api/send' fro...

low

The analytics tracking system (Umami) cannot communicate with its server due to a CORS policy block. While this prevents usage data collection for improving the referral matching process, it does not directly impact customer ability to submit transport requests.

CORS error detected

low

The analytics tracking system (Umami) is blocked by CORS policy errors, preventing Ship Car Pros from sending usage analytics to its tracking server. This limits the company's ability to collect data on how customers interact with transport request forms and referral matching.

Compliance

100/100
All clear — no issues found in this category.

1 finding suppressed (not relevant to this site type)

Key Metrics

Crawlability

Sitemap.xml
Robots.txt
Broken Links0

Standards

HTTPS
Mobile Responsive
Images Missing Alt0

Improvement Plan

Your referral matching platform has suffered a critical infrastructure breakdown that's affecting both customer experience and your ability to optimize your core business. The most pressing issue is the 404 error on a critical resource—this directly blocks customers from completing transport requests, which means your referral pipeline is likely experiencing severe leakage. Start by identifying which asset is returning 404 (check your server logs and asset manifest) and restore it immediately. This single fix could recover a significant portion of lost lead submissions.

Second, your analytics tracking system (Umami) is completely disconnected due to CORS policy blocks and server communication failures. While this isn't immediately breaking customer submissions, it's blinding you to conversion metrics and user behavior patterns that you desperately need to optimize your referral matching algorithm. Configure your CORS policy on the umami-autotransport.monotrkmain.com endpoint to allow requests from your main domain, and verify the Umami server is actually running. This needs to be resolved within 48 hours so you can resume collecting device information and usage patterns that inform your provider-customer matching.

Third, there are broader network request failures happening during the transport request submission process (net::ERR_FAILED). These appear to be separate from the analytics issue and suggest either DNS resolution problems or timeouts on backend services. Review your application logs and CDN configuration to identify which specific API endpoints are failing when customers submit vehicle details. Prioritize fixing the critical path first (the form submission endpoints), then address secondary data collection.

Finally, the WordPress emoji script 404 is cosmetic and can wait—focus your team on the three items above. Once the missing 404 resource is restored and analytics is flowing again, you'll have visibility into which referral matches are converting and where customers are abandoning the transport request form.

Suggested priority order:

  1. Failed to load resource: the server responded with a status of 404
  2. Network request failed: https://umami-autotransport.monotrkmain.com/api/send
  3. Access to fetch at 'https://umami-autotransport.monotrkmain.com/api/send' (CORS error)
  4. Failed to load resource: net::ERR_FAILED
  5. CORS error detected: WordPress emoji script returning 404

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.