AbdulTSD logo
AbdulTSD Growth, SEO and Security Audit
Prepared for ProRideLimo.com | May 17, 2026 | Confidential client review
Revenue Leakage Audit

Pro Ride Limo is losing premium bookings before the sales conversation even starts.

This report is designed to show the commercial reality behind the crawl data. The current website is not just under-optimized. It is sending paid and organic traffic into a slower, weaker, less trusted experience than a premium chauffeur brand should present.

If you only read one part, read this first

In simple terms, this report found that the website is likely losing business because important visitors are landing on a slow mobile experience, Google is still seeing broken and outdated URLs, and the website is not as secure or trustworthy as a premium service brand should be.

  • Your mobile homepage experience is too slow for high-intent traffic.
  • Broken and redirected URLs are still weakening SEO and user trust.
  • Some low-value pages are getting attention instead of your real money pages.
  • Security hardening is weaker than it should be for a lead-generation website.
  • Fixing these issues can create a visible difference in trust, lead quality, and conversions.
High risk: mobile acquisition leakage
Visible trust gap: weak security posture
Commercial issue: the wrong pages are absorbing attention
31.5s Mobile LCP

Far too slow for ad traffic and mobile booking intent.

23 Bad sitemap URLs

301 and 404 URLs are still polluting crawl signals.

11 HTML 404s

Broken destinations are still part of the site ecosystem.

54 Best Practices

Security and trust hardening are below the standard expected.

Why Business Is Being Lost

The website is leaking demand at every stage of the acquisition funnel.

This is the core commercial message for the client. The problem is not only rankings. It is the combination of wasted paid traffic, diluted organic focus, conversion friction, and security trust gaps that causes premium prospects to leave or hesitate.

Paid clicks are arriving into a slow mobile experience

Mobile lab performance is severe: FCP 10.8s, LCP 31.5s, TBT 1,130 ms, and a page payload above 9 MB. Visitors can abandon before the booking flow feels ready.

  • Google Ads and Meta clicks become more expensive to convert.
  • Quote intent drops before trust signals or CTAs are fully visible.

Organic visibility is diluted by crawl waste

The crawl found 12 HTML 301s, 11 HTML 404s, and 23 non-200 sitemap URLs. Google is still being invited to crawl outdated paths instead of focusing on canonical revenue pages.

  • Broken and redirected URLs waste crawl budget and internal equity.
  • Legacy paths weaken confidence in the site architecture.

The wrong pages are being indexed and shown importance

Author archives, category archives, blog pagination, login, create-account, and other low-value URLs are indexable. That spreads search intent away from pages that should win bookings.

  • 12 utility or archive URLs should be reviewed for noindex or consolidation.
  • Thin pages like login, create-account, and gallery weaken the funnel.

Trust is lower than a premium chauffeur brand should allow

Accessibility issues, weak best-practice signals, browser warnings, and inconsistent template quality make the site feel less refined than the service promise.

  • Best Practices score of 54 is too low for a business site collecting leads.
  • Weak hardening raises both perceived and actual risk at conversion time.
Revenue Leakage Path

What the user experience likely feels like today

This is how traffic is most likely being lost in real terms. Even when the service itself is strong, the website experience can quietly push prospects toward inaction or a competitor.

1 Click

A prospect clicks a Google Ads, Meta Ads, or organic listing with high intent.

2 Wait

Mobile rendering is slow, assets are heavy, and the first impression takes too long to settle.

3 Doubt

The experience feels less premium than expected because of friction, clutter, or weak trust signals.

4 Exit

The user leaves before completing a quote request, call, or reservation step.

5 Loss

The booking goes to a faster competitor, while ad spend and ranking equity are wasted.

Critical Findings

The four issues with the biggest sales impact

These are the issues most likely to create visible business lift once fixed. They affect speed, discoverability, conversion confidence, and long-term trust.

Performance overload

71 HTML pages exceed 150 KB raw size. The homepage alone is 405.6 KB raw HTML. Lighthouse also flagged large amounts of unused JavaScript and CSS.

  • Primary landing templates are too heavy for fast mobile acquisition.
  • Render-blocking requests and large payloads slow down the moment of trust.

Sitemap and crawl contamination

23 non-200 URLs were found in the sitemap export, including broken and redirected pages such as old service pages, no-slash variants, and orphaned legacy paths.

  • Google receives mixed signals about which pages matter.
  • Search equity is leaking into outdated destinations.

Thin and low-intent pages are still visible

Login, create-account, online reservation, archives, and pagination pages are indexable. Several of these pages also have very low word counts and weak sales value.

  • Commercial search intent is spread across pages that should not be central.
  • The ranking footprint looks broader but sells less effectively.

Security posture is below expectation

Live headers show a minimal CSP, exposed X-Powered-By, and no observed HSTS, X-Frame-Options, or COOP. Lighthouse also reported trust-and-safety gaps.

  • Potential exposure is higher than it should be for a lead-generation brand.
  • Even without an active compromise, the site looks less enterprise-ready.
Independent Verification

How the client can verify these findings without taking our word for it

No honest audit should ask for blind trust. The correct position is this: the core technical findings in this report are independently testable using public tools, browser diagnostics, and a free crawl. What public tools cannot prove alone is exact revenue loss without access to GA4, Google Search Console, call tracking, and booking conversion data.

Best client-facing line: if the same issues appear in multiple outside tools, then the pattern is real and not just a sales claim.
Speed and UX

Google PageSpeed Insights

Use this to verify mobile and desktop performance, Core Web Vitals context, accessibility, best practices, and SEO signals on the homepage or any landing page.

Open PageSpeed Insights
Headers and Hardening

SecurityHeaders.com

Use this to confirm whether headers like HSTS, X-Frame-Options, CSP quality, and other browser-side hardening signals are actually present.

Open SecurityHeaders.com
HTTPS and TLS

Qualys SSL Labs

Use this to inspect the HTTPS configuration and validate whether transport-layer security is modern and properly hardened.

Open SSL Labs
Redirects and Status Codes

HTTPStatus.io

Use this to verify 301s, 404s, redirect chains, and individual sitemap URLs. It is useful for checking the exact legacy URLs referenced in this report.

Open HTTPStatus.io
Full Site Crawl

Screaming Frog Free Version

This site crawled at 458 URLs, which fits inside Screaming Frog's free 500-URL limit. That means the client can independently verify the full crawl, 301s, 404s, metadata, H1s, canonicals, and sitemap issues.

Open Screaming Frog
Browser Audit

Chrome Lighthouse

Use Lighthouse in Chrome DevTools to reproduce performance, best-practice, accessibility, and SEO findings locally on important landing pages.

Open Lighthouse Docs
Important distinction: the presence of slow rendering, weak headers, 301s, 404s, or index bloat is publicly verifiable. Exact lost sales, wasted ad spend, and missed booking value require the client's analytics and booking data to quantify precisely.
Potential Cyber Security Threats

Security should become part of the sales conversation

For a booking-driven business, security is not only an IT topic. It affects lead trust, brand reputation, and operational continuity. These findings show a weaker defensive posture than expected. They do not prove an existing breach, but they do show avoidable exposure.

Weaker protection against script injection and abuse

The observed Content-Security-Policy only upgrades insecure requests. It does not provide strong browser-side restrictions against injected scripts or tighter resource control.

  • Potential outcome: weaker XSS resistance and looser script governance.
  • Business risk: reduced trust if forms or booking pages behave unexpectedly.

Clickjacking exposure remains open

No X-Frame-Options header was observed and no frame-ancestors policy was present in the CSP. That means browser-side protection against framing is weaker than it should be.

  • Potential outcome: brand pages can be embedded in hostile contexts more easily.
  • Business risk: trust and form safety perception decline.

HTTPS hardening is incomplete

No Strict-Transport-Security header was observed. That means the site is not enforcing long-term HTTPS behavior as strongly as modern best practice recommends.

  • Potential outcome: weaker transport hardening and downgrade resilience.
  • Business risk: lower confidence for users sharing contact and booking details.

Server fingerprinting is unnecessarily exposed

The live headers expose PHP and hosting details through X-Powered-By, Server, platform, and panel values. That makes technical reconnaissance easier than necessary.

  • Potential outcome: easier stack profiling by automated scanners.
  • Business risk: elevated attack surface perception and weaker operational posture.
Client-facing message: the site may not be visibly hacked today, but it is not hardened to the level a revenue-generating service brand should expect. Ignoring that creates both reputational and operational risk.
AbdulTSD Fix Roadmap

What should be fixed first to create a visible difference

The fastest path to stronger sales performance is not more traffic. It is fixing the leak in the current funnel, then measuring the before-and-after difference with proper tracking.

Phase 1 | First 7 to 14 days

Stop the immediate leakage

  • Remove sitemap pollution and clean all 301/404 internal references.
  • Reduce unused CSS and JavaScript on core landing templates.
  • Fix broken images, missing H1s, and overlong metadata.
  • Noindex or consolidate low-value archive and utility pages.
  • Add HSTS, stronger CSP, clickjacking protection, COOP, and hide X-Powered-By.
Phase 2 | Next 30 days

Rebuild focus and trust

  • Strengthen internal links into real booking and service pages.
  • Upgrade thin high-intent pages like get-quote, gallery, and reservation flows.
  • Fix mobile usability, contrast, heading order, and link-label issues.
  • Normalize old path variants so legacy URLs stop competing in the crawl.
Phase 3 | 30 to 90 days

Prove commercial lift

  • Connect GA4, GSC, call tracking, and booking events correctly.
  • Track clicks, CTR, leads, calls, and booked rides by landing page.
  • Monitor speed, crawl health, and index quality monthly.
  • Expand high-intent service clusters after the foundation is clean.
Expected Visible Difference

What the client should expect after cleanup

AbdulTSD should position the work around visible commercial improvement, not only technical repair. The goal is a cleaner, faster, more trusted growth asset that can support stronger lead generation.

Faster mobile first impression

Landing pages should feel ready sooner, reduce bounce risk, and improve the efficiency of ad spend.

Cleaner search focus

Search equity should be concentrated on service, airport, event, and booking pages instead of archives and utility URLs.

Higher trust at the booking moment

Security hardening, cleaner UX, and more polished templates should reduce hesitation around inquiry and reservation actions.

Trackable before and after results

Once GA4, GSC, and booking events are connected correctly, the client can see visible progress in speed, lead flow, and conversion efficiency.

Decision Point

The fastest route to more bookings is fixing the current leak before buying more traffic.

Pro Ride Limo already has enough service depth to compete. The site now needs disciplined execution: performance cleanup, technical SEO repair, security hardening, and measurement setup. That is where AbdulTSD can step in and create a visible difference in speed, trust, lead quality, and sales-related KPIs.

Performance cleanup Technical SEO repair Security hardening Tracking and attribution Before and after reporting
Recommended positioning for the client: we are not offering generic maintenance. We are offering to recover lost demand, protect the site, and turn the website into a stronger revenue asset.