yellowcheckercab.com website review

80 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

Your mobile performance score is 38 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 images could be 232 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

About 1.0 MB of JavaScript is downloaded but never used on this page.

8 third-party services load with your homepage (Google CDN, Google Maps and Google Tag Manager and others), adding 1.8 MB and 826 ms of main-thread time.

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

Google CDN costs a phone 341 ms of main-thread work and 767 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 79 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

A phone's processor spends 3.4 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google Maps costs a phone 147 ms of main-thread work and 453 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

15 long tasks block the main thread while loading, the longest for 156 ms. During a long task the page ignores taps.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The page becomes fully interactive after 24.5 s. Good is under 3.8 s.

Visually, the page fills in at 13.1 s (Speed Index). Good is under 3.4 s.

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The first text or image appears after 4.1 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 446 ms in total while the page loads. Good is under 200 ms.

The layout shifts by 0.188 while loading, so content jumps under the reader's thumb. Good is under 0.1.

16 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.8 MB in 255 requests on a phone: scripts 2.9 MB (147), images 1.1 MB (40) and other files 368 KiB (24). Under 2 MB keeps phones on slow connections fast.

7 images (608 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

3 images are downloaded at several times the size a phone draws them, for example slide01a.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 251 KiB.

2 images further down the page (86 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 163.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 elements have a tabindex above 0, which scrambles the keyboard order.

2 links inside paragraphs rely on colour alone to stand out.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

22 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

18 form fields have no label, so screen readers announce an empty box and autofill guesses.

4 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h3, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.

34 links have no real href, so search engines can't follow them.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 16 pages on yellowcheckercab.com and 6 external pages.

Your Organization JSON-LD is missing url, logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://yellowcheckercab.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://yellowcheckercab.com/drivers-application, https://yellowcheckercab.com/corporate-accounts, https://yellowcheckercab.com/areas-served, https://yellowcheckercab.com/rates, https://yellowcheckercab.com/blog and https://yellowcheckercab.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

https://yellowcheckercab.com/areas-served, https://yellowcheckercab.com/rates and https://yellowcheckercab.com/contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'appconfig') at https://yellowcheckercab.com/wp-content/cache/a…”.

2 images are served at too low a resolution for sharp phone screens.

Requests the geolocation permission on page load.

Large scripts ship without source maps.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 947 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 3 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.