Ship Car Pros

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

WordPressTailwind CSSNetlify

Report generated on April 6, 2026

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

Quote page fails to load critical resources, blocking customers from submitting transport requests.

Your referral model depends entirely on customers completing quote submissions to match with providers. When resources fail to load (404 errors and net::ERR_FAILED), potential customers cannot access the forms needed to enter vehicle and pickup/delivery information, causing them to abandon the process or call competitors instead.

CORS misconfiguration between Netlify and Umami completely blocks analytics tracking on your quote page.

You cannot see how customers interact with your referral platform, which providers they're interested in, or where they drop off during the quote process. This blindness prevents you from optimizing your matching algorithm and identifying broken funnel steps before customers leave.

Your quote page takes 848ms to respond—48ms over threshold—pushing time-sensitive customers toward competitors.

You advertise pickups available 'as early as tomorrow,' positioning your service as fast. But when customers call (866) 756-8135 after a slow page load, they're already frustrated. This delay directly reduces quote submissions and competes against your speed positioning.

Page title for Washington-to-Indiana routes is 83 characters, truncating in search results and costing clicks.

Customers searching for 'car shipping Washington to Indiana' see a cut-off title in Google results, reducing click-through rates from organic search—your lowest-friction customer acquisition channel for a referral service.

WordPress emoji script (404) signals configuration misalignment between your WordPress backend and Netlify deployment.

This indicates a broader deployment or configuration issue that could affect other WordPress-generated resources on your referral platform, risking future page breakage as you scale.

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 on their platform to be matched with suitable providers, and the service collects vehicle information (make, model, year, VIN, condition), transport details (pickup/delivery locations, preferred dates), and contact information. The Privacy Policy indicates they operate as a referral matching platform that uses collected data to improve their matching process and connect customers with transport providers from their network. The site prominently advertises that pickups are available as early as tomorrow and encourages customers to call (866) 756-8135 for quick quotes.

Based on exploring 2 pages across the site

First Impression — How clear is your site?

95
Crystal clear

This website offers car shipping services specifically from Washington to Indiana. The page states it provides "Door-to-door auto transport with real-time tracking and dedicated support," with an average route distance of 2155 miles and an estimated transit time of 4 days. The main 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.

88/ 100

Overall Score

Strong foundation.

Performance

92/100

High Time to First Byte: 848ms

medium

Your Netlify server takes 848ms to respond to customer quote requests, exceeding the recommended 800ms threshold. Slow page load times discourage customers from submitting transport requests and may cause them to call your competitors' phone numbers instead of (866) 756-8135.

Expected: Under 800ms
Found: 848ms

SEO

97/100

Page title too long (83 chars)

low

Your page title for car shipping quotes from Washington to Indiana is too long (83 characters) and will be truncated in Google search results and social media previews. This reduces click-through rates from potential customers searching for auto transport services.

Expected: 50-60 characters
Found: 83 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 ()

high

A critical resource failed to load on your car shipping quote page, preventing customers from accessing essential information needed to submit their transport request. This may block users from completing their quote inquiry.

Failed to load resource: net::ERR_FAILED

high

A network request failed while loading resources on your car shipping quote page. This could prevent customers from accessing forms or quote information needed to submit their transport request.

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

likelyhigh

Your analytics tracking service cannot send data to the monitoring server. This blocks collection of customer interaction metrics on your referral platform, preventing you from understanding how users engage with your quote submission process.

CORS error detected

high

Your analytics integration is completely blocked due to CORS policy misconfiguration between your Netlify site and your Umami analytics server. You cannot track customer quote requests, conversion data, or user behavior on your auto transport referral platform.

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

medium

Your analytics tracking service (Umami) cannot communicate with your Netlify-hosted site due to CORS policy restrictions. This prevents you from collecting data about how potential car shipping customers interact with your referral platform, impacting your ability to optimize the customer matching process.

HTTP 404 on https://shipcarfromwashingtontoindiana.netlify.app/wp-includ

medium

WordPress emoji script failed to load from your site's Netlify hosting. While not critical, this indicates a configuration issue between your WordPress backend and Netlify deployment that could affect other WordPress resources on your car shipping referral 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 Ship Car Pros referral platform is experiencing a critical conversion funnel collapse. Three separate resource-loading failures (404s and net::ERR_FAILED) are preventing customers from accessing your quote submission forms—the core action that powers your entire business model. This is your highest priority because every failed resource load is a lost referral opportunity and a customer who may call a competitor instead. Within 48 hours, audit your Netlify deployment logs to identify which resources are returning 404 errors on your car shipping quote pages, then either restore those files or remove references to them.

Second, your analytics infrastructure is completely broken. The CORS misconfiguration between your Netlify site and Umami analytics server means you have zero visibility into how customers use your referral platform. You cannot measure quote submission rates, identify which auto transport provider matches customers are clicking on, or spot where drop-off occurs. This blindness prevents you from improving your matching algorithm. Fix the CORS policy immediately by configuring your Netlify headers to allow requests from your Umami domain, or switch to a Netlify-native analytics solution.

Third, your page load time of 848ms is eroding your competitive advantage. You position Ship Car Pros as fast ('pickups available as early as tomorrow'), but a slow quote page contradicts that message and increases abandonment before customers even call your phone number. Investigate what's causing the 848ms Time to First Byte—likely database queries or third-party script delays—and optimize or defer non-critical resources.

Finally, clean up your SEO metadata. Your Washington-to-Indiana page title truncates at 83 characters, reducing organic search click-through rates. This is a quick win: shorten the title to 55-60 characters while preserving the location keywords and unique value proposition (e.g., 'Car Shipping WA to IN | Ship Car Pros'). Also resolve the WordPress emoji script 404 to prevent cascading failures as your site grows.

Start with resource loading (Day 1), then CORS/analytics (Day 2), performance (Week 1), and SEO metadata (concurrent). This sequence restores your conversion funnel first, then gives you visibility to optimize it.

Suggested priority order:

  1. Failed to load resource (404 and net::ERR_FAILED on quote page)
  2. CORS error blocking Umami analytics integration
  3. High Time to First Byte (848ms server response)
  4. Page title too long (83 chars truncating in search results)
  5. WordPress emoji script 404 (configuration misalignment)

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.