Ship Car Pros

Need Reliable Car Shipping From Nevada To Tennessee? Skip The 2024-Mile Drive! Delivery 4 Days Door-To-Door.

WordPressTailwind CSSNetlify

Report generated on April 6, 2026

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

CORS misconfiguration is blinding you to which transport requests convert

Your Umami analytics endpoint cannot communicate with your Netlify deployment, meaning you have zero visibility into customer behavior patterns, which transport providers get matched most often, or where your referral process is breaking down. For a referral service, this data is critical to optimizing your provider matching algorithm.

Missing 404 resources are silently breaking your request submission flow

Customers attempting to submit car shipping requests or view matched providers are encountering failed resource loads that degrade the experience. Since your entire business model depends on smooth request submission and provider discovery, these errors directly impact conversion and customer satisfaction.

WordPress artifact errors suggest incomplete migration to static hosting

404 errors on WordPress emoji script files indicate your site wasn't fully cleaned up during migration to Netlify. While cosmetic, this signals incomplete infrastructure work that could mask other underlying issues and suggests your hosting environment isn't fully optimized.

Your route-specific page titles are cut off in Google search results

Your Nevada-to-Tennessee page title is 79 characters and will be truncated in SERPs, reducing click-through rates from customers searching for regional car shipping services. This is lost organic traffic to a key customer segment.

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 their contact information, vehicle details (make, model, year, VIN, condition), pickup and delivery locations, and preferred dates. The service collects this information to match customers with suitable transport providers in their network. The platform emphasizes that it is a referral service rather than a direct transport provider, and operates under specific terms requiring users to be at least 18 years old and provide accurate information about their vehicles and transport needs.

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 Nevada to Tennessee. The page explicitly states it provides "Door-to-door auto transport with real-time tracking and dedicated support," with an average route distance of 2024 miles and an estimated transit time of 4 days. Visitors are prompted 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.

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

Your page title for Nevada-to-Tennessee car shipping routes is too long at 79 characters and will be truncated in Google search results, reducing click-through rates when potential car shipping customers search for transport services.

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

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

likelyhigh

Your analytics endpoint at umami-autotransport.monotrkmain.com is failing to receive data from your Netlify deployment, preventing you from collecting insights about customer transport requests, provider matches, and user engagement on your referral platform.

CORS error detected

high

Your analytics service cannot send tracking data from your car shipping referral platform due to CORS policy mismatches between your Netlify domain and the Umami analytics server. This breaks your ability to monitor customer interactions, transport request submissions, and provider matching effectiveness.

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

medium

A missing resource is preventing proper loading of page elements on your car shipping referral platform, which could affect the user experience when customers try to submit transport requests or view shipping provider options.

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

medium

Your analytics tracking service (Umami) cannot communicate properly with your Netlify-hosted referral platform due to CORS configuration issues. This prevents you from tracking customer behavior as they submit car shipping requests and interact with transport provider matches.

Failed to load resource: net::ERR_FAILED

medium

A network request failure is occurring on your car shipping referral platform, which could disrupt the submission of transport requests or the retrieval of matched shipping providers.

HTTP 404 on https://shipcarfromnevadatotennessee.netlify.app/wp-includes

low

WordPress emoji script files are returning 404 errors on your Netlify-hosted platform. While this is a minor cosmetic issue, it indicates incomplete WordPress resource migration to your static 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 currently operating blind with broken analytics and failing resource loads—a dangerous combination for a service that depends on understanding customer behavior to improve provider matches. Start immediately by fixing the CORS configuration between your Netlify domain and the Umami analytics server. This is blocking all tracking of customer transport requests, provider matching interactions, and conversion funnels. Without this data, you cannot optimize which providers get matched to which requests or identify where customers drop off during the submission process.

Next, audit and fix all 404 resource failures preventing page elements from loading. These aren't just cosmetic issues—they're directly impacting the user experience when customers submit transport requests or browse matched providers. Identify exactly which resources are failing (the WordPress emoji scripts and other assets) and either migrate them fully to Netlify or remove the references entirely. Test the complete request submission flow end-to-end to ensure no customers are experiencing friction.

Once core functionality is restored, address the technical debt from your WordPress-to-Netlify migration. The presence of WordPress artifact errors suggests your site wasn't fully cleaned up. Conduct a thorough audit of your static hosting configuration to eliminate all lingering references to WordPress resources that don't exist in your current environment.

Finally, optimize your page titles for high-intent search keywords. Reduce your Nevada-to-Tennessee title to under 60 characters so it displays fully in Google results, and apply this discipline to other regional route pages. This is a quick win that will improve organic visibility for customers actively searching for car shipping between specific locations.

Suggested priority order:

  1. CORS error blocking analytics data collection
  2. Failed resource loads preventing request submission
  3. Network request failures on Umami endpoint
  4. WordPress artifact 404 errors and incomplete migration cleanup
  5. Page title truncation 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.