Website review, no card needed

aptonline.org logo

aptonline.org website review

Visit site (opens in a new tab)Reviewed 23 October 202636 issues · 81 checks

This review found 36 issues worth fixing on aptonline.org, 13 of them high impact, across 81 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.5 s1.5 sMay 2Oct 171.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20261.9 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.4 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
155 ms74 msMay 2Oct 1783 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026110 ms
May 9, 2026112 ms
May 16, 2026118 ms
May 23, 2026140 ms
May 30, 2026146 ms
Jun 6, 2026129 ms
Jun 13, 2026123 ms
Jun 20, 2026103 ms
Jun 27, 202696 ms
Jul 4, 202691 ms
Jul 11, 202691 ms
Jul 18, 202694 ms
Jul 25, 202696 ms
Aug 1, 2026108 ms
Aug 8, 2026112 ms
Aug 15, 2026112 ms
Aug 22, 2026111 ms
Aug 29, 2026123 ms
Sep 5, 2026121 ms
Sep 12, 2026106 ms
Sep 19, 2026109 ms
Sep 26, 2026106 ms
Oct 3, 202693 ms
Oct 10, 202692 ms
Oct 17, 202683 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 aptonline.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aptonline.org at 0.4 s0.4 s
  2. aptonline.org at 0.8 s0.8 s
  3. aptonline.org at 1.1 s1.1 s
  4. aptonline.org at 1.5 s1.5 s
  5. aptonline.org at 1.9 s1.9 s
  6. aptonline.org at 2.3 s2.3 s
  7. aptonline.org at 2.6 s2.6 s
  8. aptonline.org at 3.0 s3.0 s

Speed

8 to fix42
  • Use efficient cache lifetimes

    44.6 s · 18.1 MB

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

  • Improve image delivery

    17.7 s · 10.3 MB

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

  • Mobile performance score: 42

    42/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Amazon Web Services and Google Analytics and others), adding 18.4 MB and 130 ms of main-thread time.

  • backblazeb2.com adds 0 ms

    0 ms

    backblazeb2.com costs a phone 0 ms of main-thread work and 17.8 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.

  • Reduce unused JavaScript

    450 ms · 131 KiB

    About 131 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 4 long tasks on the main thread

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

  • Amazon Web Services adds 0 ms

    0 ms

    Amazon Web Services costs a phone 0 ms of main-thread work and 425 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.

  • Legacy JavaScript

    150 ms · 13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • 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.

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 234 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

7 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.47

    0.47

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

  • Largest Contentful Paint: 75.2 s

    75.2 s

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

  • Time to Interactive: 77.4 s

    77.4 s

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

  • Cumulative Layout Shift: 0.821

    0.821

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

  • Total Blocking Time: 379 ms

    379 ms

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

  • 1 image without width and height

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

8 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 78 ms

    78 ms

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 446 ms

    446 ms

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

  • Tap response (INP) got 21% faster for real visitors

    -21%

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

  • Speed Index: 1.8 s

    1.8 s

    Visually, the page fills in at 1.8 s (Speed Index), inside the 3.4 s “good” threshold.

Images and page weight

1 to fix70
  • Page weight: 18.9 MB in 39 requests

    18.9 MB

    Your homepage downloads 18.9 MB in 39 requests on a phone: images 18.1 MB (10), other files 451 KiB (16) and scripts 393 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 5.4 g of CO₂ per visit

    5.36 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9697
  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

8 to fixGoogle 9163
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (26 characters)

    Your title is only 26 characters: “American Public Television”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://aptonline.org/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • 1 link with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 19 internal links, 6 external

    The homepage links to 19 pages on aptonline.org and 6 external pages.

1 checks passed
  • Meta description: 111 characters

    Your meta description is 111 characters: “APT is a leading distributor of high-quality, top-rated programming to the nation's public television stations.”.

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://aptonline.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 (135 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 12 pages share a title

    /, https://aptonline.org/programs/viewers/alpha, https://aptonline.org/programs/viewers/genre, https://aptonline.org/pages/stations/index-Closed+Captioning+Certification, https://aptonline.org/pages/about/about-apt and https://aptonline.org/about/Our-Mission and 6 others all use the title “American Public Television”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://aptonline.org/stations, https://aptonline.org/producers, https://aptonline.org/viewers, https://aptonline.org/programs/viewers/alpha, https://aptonline.org/programs/viewers/genre and https://aptonline.org/pages/stations/index-Closed+Captioning+Certification and 9 others use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://aptonline.org/pages/stations/index-Closed+Captioning+Certification, https://aptonline.org/pages/about/about-apt, https://aptonline.org/about/Our-Mission, https://aptonline.org/about/Leadership, https://aptonline.org/about/Careers and https://aptonline.org/about/Directions and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://aptonline.org/producers, https://aptonline.org/viewers, https://aptonline.org/programs/viewers/alpha, https://aptonline.org/programs/viewers/genre, https://aptonline.org/pages/stations/index-Closed+Captioning+Certification and https://aptonline.org/pages/about/about-apt and 8 others 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 18 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 5 small tap targets

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

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

4 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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.

  • Only about 213 words

    The homepage has only about 213 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • 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.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Learn more about APT” and “Newsletter Signup”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 aptonline.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
Next.js
Analytics
Google Analytics
Hosting
AWS

Company

Headquarters
Boston

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on aptonline.org, including 15 speed issues, 8 SEO issues and 4 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