Website review, no card needed

milwaukeepbs.org logo

milwaukeepbs.org website review

Visit site (opens in a new tab)Reviewed 23 October 202646 issues · 88 checks

This review found 46 issues worth fixing on milwaukeepbs.org, 19 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.6 s2.1 sMay 2Oct 172.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.6 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
142 ms114 msMay 2Oct 17134 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026130 ms
May 9, 2026128 ms
May 16, 2026125 ms
May 23, 2026120 ms
May 30, 2026117 ms
Jun 6, 2026118 ms
Jun 13, 2026124 ms
Jun 20, 2026127 ms
Jun 27, 2026128 ms
Jul 4, 2026128 ms
Jul 11, 2026132 ms
Jul 18, 2026127 ms
Jul 25, 2026128 ms
Aug 1, 2026129 ms
Aug 8, 2026128 ms
Aug 15, 2026134 ms
Aug 22, 2026128 ms
Aug 29, 2026127 ms
Sep 5, 2026130 ms
Sep 12, 2026136 ms
Sep 19, 2026137 ms
Sep 26, 2026139 ms
Oct 3, 2026136 ms
Oct 10, 2026129 ms
Oct 17, 2026134 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of milwaukeepbs.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. milwaukeepbs.org at 1.0 s1.0 s
  2. milwaukeepbs.org at 1.9 s1.9 s
  3. milwaukeepbs.org at 2.9 s2.9 s
  4. milwaukeepbs.org at 3.9 s3.9 s
  5. milwaukeepbs.org at 4.8 s4.8 s
  6. milwaukeepbs.org at 5.8 s5.8 s
  7. milwaukeepbs.org at 6.8 s6.8 s
  8. milwaukeepbs.org at 7.7 s7.7 s

Speed

12 to fix18
  • Use efficient cache lifetimes

    12.6 s · 3.5 MB

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

  • Improve image delivery

    9.3 s · 2.2 MB

    5 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.3 s faster on a phone.

  • Reduce unused JavaScript

    1.6 s · 2.9 MB

    About 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • YouTube adds 1.3 s

    1.3 s

    YouTube costs a phone 1.3 s of main-thread work and 2.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 18

    18/100

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

  • Main-thread work: 5.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and pbs.org and others), adding 6.4 MB and 2.7 s of main-thread time.

  • Render-blocking requests

    850 ms

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

  • Reduce unused CSS

    470 ms · 235 KiB

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

  • Google Tag Manager adds 512 ms

    512 ms

    Google Tag Manager costs a phone 512 ms of main-thread work and 796 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.

  • pbs.org adds 263 ms

    263 ms

    pbs.org costs a phone 263 ms of main-thread work and 1.5 MB 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.

  • 20 long tasks on the main thread

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

  • Minify CSS

    31 KiB

    31 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    23 KiB

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

  • Chained critical requests

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 32 ms

    32 ms

    Your server sent the HTML in 32 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 0.48

    0.48

    For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 19.6 s

    19.6 s

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

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 45.5 s

    45.5 s

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

  • Cumulative Layout Shift: 0.447

    0.447

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user TTFB: 946 ms

    946 ms

    Real visitors wait 946 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 130 ms to 134 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +7%

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

3 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 135 ms

    135 ms

    Real visitors wait 135 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

Images and page weight

5 to fix25
  • Page weight: 8.7 MB in 147 requests

    8.7 MB

    Your homepage downloads 8.7 MB in 147 requests on a phone: scripts 5.0 MB (62), images 2.7 MB (28) and HTML 377 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    86298b4a0e_Cartober26_Every-Car-Can-Drive-Change.gif weighs 2.0 MB. On a phone connection a single image that size takes seconds.

  • 5 images in older formats

    5 images (2.1 MB) 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.

  • An image on the first screen is lazy-loaded

    76a6744d8e_Newsletter Sign Up (400 x 400 px).png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images far larger than shown

    319 KiB

    2 images are downloaded at several times the size a phone draws them, for example 86298b4a0e_Cartober26_Every-Car-Can-Drive-Change.gif at 1,200 px wide, shown at 370 px. Resized copies would save about 319 KiB.

  • About 2.5 g of CO₂ per visit

    2.47 g

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

Accessibility

3 to fixGoogle 9293
  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 text element with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9075
  • Title is short (24 characters)

    Your title is only 24 characters: “What is on Milwaukee PBS”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (13 characters)

    Your meta description is only 13 characters: “milwaukee_pbs”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • No robots.txt

    There is no robots.txt at milwaukeepbs.org/robots.txt, the first file search crawlers ask for.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 74 internal links, 56 external

    The homepage links to 74 pages on milwaukeepbs.org and 56 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “WATCH LIVE - CHANNEL 10.1”.

  • Structured data in place

    Structured data found: WebSite.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.milwaukeepbs.org/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.milwaukeepbs.org/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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (621 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 1 linked page hidden from search

    https://www.milwaukeepbs.org/full-page-schedule is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages share a meta description

    https://www.milwaukeepbs.org/stream, https://www.milwaukeepbs.org/full-page-schedule, https://www.milwaukeepbs.org/adelante, https://www.milwaukeepbs.org/blacknouveau, https://www.milwaukeepbs.org/movers and https://www.milwaukeepbs.org/jesus-salas and 2 others use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://www.milwaukeepbs.org/stream, https://www.milwaukeepbs.org/schedule/channel-information, https://www.milwaukeepbs.org/full-page-schedule, https://www.milwaukeepbs.org/movers, https://www.milwaukeepbs.org/my-wisconsin-backyard and https://www.milwaukeepbs.org/rhythm-cafe-mke and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • 51 small tap targets

    51 of 101 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 553 words of copy

    The homepage carries about 553 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Full Page Schedule” and “PBS KIDS Summer Activity Book”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Full Page Schedule”, “PBS KIDS Summer Activity Book” and “Join or Renew”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 30 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at milwaukeepbs.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
Analytics
Google Analytics | Google Tag Manager

Company

Headquarters
Milwaukee

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on milwaukeepbs.org, including 22 speed issues, 6 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25