Ship Car Pros

Need Reliable Car Shipping From Missouri To California? Skip The 1848-Mile Drive! Delivery 4 Days Door-To-Door.

WordPressTailwind CSSNetlify

Report generated on April 6, 2026

shipcarfrommissouritocalifornia.netlify.app
Screenshot of shipcarfrommissouritocalifornia.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

Your referral form is broken: 404 errors prevent customers from submitting transport requests

As a referral platform, your core value proposition depends on customers successfully submitting transport requests to match with providers. A 404 error blocks this critical conversion point entirely, meaning potential referrals are being lost before they reach your network.

CORS misconfiguration silences your analytics—you can't see if referral matching actually works

Your Umami analytics endpoint is completely unreachable due to CORS errors, so you have no visibility into whether customers are submitting requests, which providers are being matched, or where the referral process breaks down. This blinds your ability to optimize provider matching effectiveness.

A secondary network resource is failing to load, degrading the referral form experience

Beyond the primary 404 error, an additional network resource failure (net::ERR_FAILED) is impacting form functionality or UX. Combined with the 404 issue, this suggests multiple critical paths in your referral workflow are broken.

Route-specific page titles are truncated (85 chars), losing searchability for 'Missouri to California' shipping queries

Customers searching for car shipping on specific routes are a high-intent audience. Truncated titles in search results reduce click-through rates for these geo-targeted landing pages, especially since route specificity is a key differentiator for shipping services.

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 providers in their network, and the service collects vehicle information (make, model, year, VIN, condition), contact details, pickup/delivery locations, and preferred dates. The Privacy Policy indicates they also collect automatically generated data like IP address, device information, and usage patterns to improve their referral matching process. The service requires users to be at least 18 years old and emphasizes that it operates as a referral platform rather than directly providing transport services themselves.

Based on exploring 2 pages across the site

First Impression — How clear is your site?

92
Crystal clear

This site offers car shipping services from Missouri to California. The hero section states 'The easy way to move your car from Missouri to California' with 'Door-to-door auto transport with real-time tracking and dedicated support.' The service promises an average route distance of 1848 miles with an estimated transit time of 4 days.

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 (85 chars)

low

Your page title for this car shipping route is 85 characters long and will be truncated in search results, reducing the visibility of this specific route (Missouri to California) when potential customers search for car shipping services.

Expected: 50-60 characters
Found: 85 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

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

likelyhigh

Your analytics API endpoint for tracking referral submissions and user behavior is completely unreachable, preventing collection of critical data on referral form usage and provider matching effectiveness.

CORS error detected

high

Your analytics service is completely inaccessible due to CORS misconfiguration with the Umami server, preventing you from tracking how effectively your referral matching process converts visitors into transport requests.

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

medium

A critical resource required for the car shipping referral form is returning a 404 error, which could prevent users from submitting transport requests or viewing key page elements.

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

medium

Your analytics tracking for user interactions (such as referral form submissions and provider matching engagement) is being blocked by CORS policy issues with the Umami analytics server, preventing you from collecting data on how customers use the referral matching service.

Failed to load resource: net::ERR_FAILED

medium

A network resource failed to load, which may impact the functionality of your car shipping referral form or user experience on the site.

HTTP 404 on https://shipcarfrommissouritocalifornia.netlify.app/wp-inclu

low

WordPress emoji support files are missing from your Netlify deployment, which is a minor visual issue but indicates incomplete WordPress asset migration to your hosting platform.

Compliance

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

Key Metrics

Crawlability

Sitemap.xml
Robots.txt
Broken Links0

Standards

HTTPS
Mobile Responsive
Images Missing Alt0

Improvement Plan

Your referral platform faces two critical blockers that are preventing both customer conversions and business intelligence. First, investigate and fix the 404 error affecting your referral form immediately—this is your primary revenue driver. Check your Netlify deployment logs to identify which form resource is missing, verify the correct asset paths in your HTML, and ensure all form dependencies uploaded correctly during migration. This single issue is likely eliminating a significant percentage of potential referrals.

Second, address the Umami analytics CORS misconfiguration with equal urgency. Your analytics endpoint (umami-autotransport.monotrkmain.com/api/send) is unreachable, which means you're flying blind on referral performance. Contact your Umami hosting provider or your development team to whitelist your Netlify domain (shipcarfrommissouritocalifornia.netlify.app) in CORS settings and verify the API endpoint is actually responding. Once analytics flows, you'll gain visibility into whether your referral matching is effective and where users drop off.

Third, address the secondary net::ERR_FAILED network resource failure. Audit all external dependencies loaded by your referral form—CSS, JavaScript, images—and ensure they're either locally hosted or pointing to reliable CDNs. The WordPress emoji file error indicates incomplete asset migration, so do a full audit of your wp-includes directory on Netlify and either migrate missing assets or disable WordPress emoji support.

Finally, optimize your route-specific page titles for SEO. Reduce the Missouri-to-California title to under 60 characters while keeping the key differentiators (route, service type) so it displays fully in search results. This is lower priority than fixing functionality, but once your form works, you'll want search traffic to land on fully optimized pages. Consider creating individual optimized titles for each high-value shipping route.

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 (HIGH CORS error)
  3. Failed to load resource: net::ERR_FAILED
  4. Access to fetch CORS blocking (Umami analytics)
  5. Page title too long (85 chars)

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.