Ship Car Pros

Need Reliable Car Shipping From Wisconsin To Washington? Skip The 1851-Mile Drive! Delivery 4 Days Door-To-Door.

WordPressTailwind CSSNetlify

Report generated on April 6, 2026

shipcarfromwisconsintowashington.netlify.app
Screenshot of shipcarfromwisconsintowashington.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 Umami analytics is completely blind to customer behavior due to CORS and network failures.

As a referral service, you need visibility into how customers submit transport requests and which providers they engage with. Currently, both CORS policy blocking and failed API connections mean you're getting zero data on customer interactions, making it impossible to optimize your matching algorithm or identify bottlenecks in the referral process.

Critical 404 errors are likely breaking your transport request submission forms.

Your platform's core value is converting customers into referrals. If key resources (likely form elements or dynamic content) are returning 404 errors, potential customers may be unable to submit their vehicle details and shipping preferences, directly reducing referrals and revenue.

906ms server response time creates friction at the exact moment customers try to submit requests.

In a referral service, every second of latency increases form abandonment. When customers are trying to input their vehicle make, model, VIN, and transport dates, a slow Time to First Byte signals an unreliable service and pushes them toward competitors.

WordPress files aren't migrated to your Netlify static deployment, causing emoji 404s.

This indicates a incomplete migration from WordPress to your Netlify hosting. While emoji errors are visual, they're a symptom of mismatched hosting setups that could be causing the broader 404 and network failures affecting your referral forms.

87-character page titles get truncated in search results, losing clicks from high-intent searches like 'ship car from Wisconsin to Washington.'

Regional car shipping searches are high-intent queries from customers actively looking for transport providers. Truncated titles reduce your click-through rate from organic search, limiting the qualified traffic that feeds your referral network.

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. Users submit transport requests through the platform, providing information about their vehicle (make, model, year, VIN, condition), pickup and delivery locations, and preferred dates. The service then matches customers with suitable transport providers from their network. Users must be at least 18 years old to use the service, and the platform collects contact information, vehicle details, transport preferences, and feedback to facilitate these connections. The company emphasizes that it is a referral service rather than a direct transport provider, as stated in both their Terms and Conditions and Privacy Policy introductions.

Based on exploring 2 pages across the site

First Impression — How clear is your site?

92
Crystal clear

This website offers car shipping services from Wisconsin to Washington. It explicitly states "The easy way to move your car from Wisconsin to Washington" with "Door-to-door auto transport with real-time tracking and dedicated support." The site shows an average route distance of 1851 miles with an estimated transit time of 4 days, and prompts visitors to call for a quote.

This score measures how quickly a first-time visitor understands what your site does — based on visible headings, navigation, and visual hierarchy alone.

88/ 100

Overall Score

Strong foundation.

Performance

92/100

High Time to First Byte: 906ms

medium

Your server response time (906ms) is slower than optimal for a referral platform, which may cause delays when customers submit transport requests or browse available shipping providers.

Expected: Under 800ms
Found: 906ms

SEO

97/100

Page title too long (87 chars)

low

Your page title for car shipping routes (87 characters) is too long and will be truncated in search results, reducing click-through rates when potential customers search for regional car transport services like 'ship car from Wisconsin to Washington.'

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

Analytics data from your Umami tracking service is failing to send, preventing you from monitoring how customers interact with your car transport referral service and submit shipping requests.

CORS error detected

high

Your analytics service cannot send data to its remote endpoint due to CORS policy restrictions, blocking visibility into customer behavior and transport request patterns on your referral platform.

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

medium

A critical resource failed to load (404 error), which may prevent transport request forms or key functionality from displaying properly on your car shipping referral platform.

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

medium

Your analytics tracking service (Umami) cannot communicate with its server due to CORS policy blocking, preventing data collection on customer transport requests and user interactions on your referral platform.

Failed to load resource: net::ERR_FAILED

medium

A network resource failed to load entirely, which could disrupt the submission of vehicle details or transport preferences on your car shipping matching platform.

HTTP 404 on https://shipcarfromwisconsintowashington.netlify.app/wp-incl

medium

WordPress emoji resources are returning 404 errors on your static Netlify deployment, suggesting your WordPress installation files may not be properly migrated to your hosting environment.

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 is suffering from a hosting migration gone wrong, compounded by broken analytics. Start immediately by fixing the WordPress-to-Netlify migration: your emoji 404 errors suggest WordPress files (wp-includes directory) are still being referenced but missing from your static deployment. This is likely the root cause of the broader 404 errors breaking your transport request forms. Once deployed files are aligned, the cascading 404 and network failures should reduce significantly.

Next, restore analytics visibility by addressing the Umami CORS policy blocking. This likely requires updating your Umami API endpoint configuration to allow requests from your Netlify domain, or switching to a CORS-compatible analytics setup. Without this, you're flying blind on how customers interact with provider matches and submit requests—critical data for optimizing your referral matching algorithm.

The 906ms Time to First Byte is slower than acceptable for a referral service where milliseconds matter during form submission. Audit your server-side rendering or API calls during page load; this is likely exacerbated by the failed Umami requests hanging your page. Optimizing server response time will compound the benefits of fixing the broken resources above.

Finally, trim your page titles to 60 characters or less. For regional routes like Wisconsin to Washington, test titles like "Ship Car from Wisconsin to Washington | Auto Transport" to capture search intent while staying within search result display limits.

Execute these fixes in this order: (1) hosting migration, (2) analytics restoration, (3) server response optimization, (4) SEO title refinement. The first two are blocking revenue; the latter two amplify growth.

Suggested priority order:

  1. HTTP 404 on WordPress emoji resources / incomplete Netlify migration
  2. Failed to load resource: 404 errors breaking form functionality
  3. CORS error and Umami analytics failures preventing data collection
  4. High Time to First Byte (906ms) slowing form submission
  5. Page title too long (87 chars) reducing search visibility

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.