Compliance Audit of jwspeaker.com

Risk 01 · Tracking & Consent

The cookie banner does not do anything

jwspeaker.com

Watch the little red lights. Decline gets clicked, the banner politely leaves, and every tracker keeps right on rolling. All 18 cookies stay for the whole visit, and one of the tools records the screen: every scroll, every click.

Why it matters: recording visitors after they say no is exactly what the current wave of California privacy lawsuits goes after, and the banner is making a promise the site does not keep.

Potential risk

Who comes after you: Privacy class-action firms that scan the web for session-recording tools, plus California's privacy regulator.
How the lawsuit happens: A class action under California's wiretapping law (CIPA), which treats recording a visitor's screen without consent as illegal eavesdropping, at up to $5,000 per visitor.
Why you are liable: The site keeps recording after Decline is clicked, so consent cannot be argued, and the "we won't track" banner is a documented false statement on top of it.

See it live

Open jwspeaker.com and click Decline
Reload the page
DevTools › Application › Cookies: everything is still there

Risk 02 · Privacy Policy

The policy does not match what the site does

jwspeaker.com/privacy

⌕California0 results

Privacy Policy Last updated: (no date)

Collecting data but never mentioned: MS Clarity HubSpot CrazyEgg Bing

The policy is the company's public promise about data, and it is a little out of date. It has no date at all, never mentions California, and four of the eight tools collecting data are not in it.

Why it matters: California privacy law requires any site sharing visitor data with ad platforms, which this one does, to spell out California residents' rights in its policy. There is no way to write that section without the word appearing at least once, so a zero-result search is ten-second proof the required section does not exist. Gaps like that, between what the policy says and what the site does, are where most privacy enforcement starts.

Potential risk

Who comes after you: State attorneys general and California's privacy agency, whose enforcement sweeps compare exactly this: what the policy says versus what the site does.
How the penalty happens: Fines run per violation, up to $2,500 each and $7,500 if intentional, and every undisclosed tracker on every California visit can count separately.
Why you are liable: Four data-collecting tools are never disclosed, and the California rights section and "Do Not Sell or Share" opt-out the law requires do not exist anywhere on the site.

See it live

Open jwspeaker.com/terms-of-use/privacy/
Search the page for "California"
Zero results

Risk 03 · ADA Accessibility

The site fails standard accessibility checks

Press Tab twice and the highlight simply vanishes. The keyboard focus outline is switched off in the code, so anyone browsing by keyboard is lost. Google's audit tool counts 16 issues like this on the home page: low-contrast text, unlabeled images, links with no name.

Why it matters: these are the exact checks drive-by ADA demand letters start with, and mid-size manufacturers are a favorite target.

Potential risk

Who comes after you: Serial ADA plaintiffs and the law firms behind them, which file thousands of website suits a year and favor mid-size manufacturers.
How the lawsuit happens: A demand letter arrives citing the same automated checks this site fails; most companies settle in the five figures because defending costs more than fixing.
Why you are liable: The federal ADA applies to business websites, state laws like California's Unruh Act add $4,000 minimum per violation, and 16 documented failures make the letter easy to write.

See it live

Open jwspeaker.com
Press Tab a few times
Watch the keyboard focus disappear

The Math · Risks 01 + 02 + 03 combined

What 90 days of this could cost

$5,000wiretap penalty per recorded visitor (CIPA)

+

$2,500privacy fine per visitor (CCPA)

=

$7,500of exposure, every single visitor

At 30 visitors a month, one a day $700K 90 visitors × $7,500 + one ADA letter statutory ceiling, last 90 days

At 60 visitors a month, two a day $1.4M 180 visitors × $7,500 + one ADA letter statutory ceiling, last 90 days

Both scenarios are absurdly conservative on purpose. jwspeaker.com actually gets roughly 30,000 visits a month, about a thousand a day. Run the same 90-day math on just the California share of that traffic and the ceiling lands around $60M.

Ceiling math, not a damages prediction: CIPA and CCPA count California visitors only (the $60M figure already counts only them: ~91,000 visits per 90 days, 74% US, ~12% of that Californian, × $7,500), real settlements land below the statutory maximums, and the ADA line is booked as a single $25,000 demand-letter settlement. Traffic per SimilarWeb estimates. An engineering estimate, not legal advice.

Risk 04 · Search & Site Health

The site hands Google 879 URLs it should not

This one is not a lawsuit. It is search visibility and server cost, and it is invisible from the front end, so nobody has had a reason to look.

Three separate problems, all in the file the site uses to tell Google what to index. One whole sitemap is 100% dead links. Thirty-one records marked unpublished are serving full spec sheets to anyone. And every one of the 710 spec sheets is a PDF built from scratch on request, so the buyer waits about a second for something a web page would have shown instantly.

Why it matters: the buyer checking whether your light fits their truck waits on a PDF the server builds from scratch, and Google pays the same toll, spending its crawl on dead links instead of the 163 product pages that sell.

What it costs you

138 dead links. Every URL in standard-sitemap.xml returns 404. Not most. All 138.
31 drafts, public. Records marked unpublished still hand their full spec sheet to anyone. Today it is a power cord and a pole mount. That is luck, not a setting.
0.9 seconds per spec sheet. Every PDF is built from scratch on request. 280KB to 910KB, cached ten minutes, never at the CDN.
7× slower than a web page. 0.9s against 0.13s, at 4× the weight, and it opens in a PDF viewer instead of your site. HTML would be instant, searchable, linkable.

See it live

Open standard-sitemap.xml
Click any URL in the list. Every one is a 404
Then open a Model 93 spec sheet and count the wait

The good news: all four are already handled in the rebuild you are looking at. This demo scores 100 on the same accessibility audit, and a rebuilt site publishes a clean sitemap with cached spec sheets by default. Today is just about seeing where the current site stands.

Back to the demo

Reviewed 2026-07-22 · Google Lighthouse + manual checks · an engineering review, not legal advice

What we found on the current site

The cookie banner does not do anything

The policy does not match what the site does

The site fails standard accessibility checks

What 90 days of this could cost

The site hands Google 879 URLs it should not