Website review, no card needed

alaskapublic.org logo

alaskapublic.org website review

Visit site (opens in a new tab)Reviewed 18 October 202638 issues · 81 checks

This review found 38 issues worth fixing on alaskapublic.org, 13 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
1.7 s1.5 sApr 25Oct 101.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.6 s
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
96 ms85 msApr 25Oct 1094 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202695 ms
May 2, 202691 ms
May 9, 202689 ms
May 16, 202690 ms
May 23, 202688 ms
May 30, 202689 ms
Jun 6, 202689 ms
Jun 13, 202687 ms
Jun 20, 202689 ms
Jun 27, 202687 ms
Jul 4, 202686 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202688 ms
Aug 8, 202688 ms
Aug 15, 202688 ms
Aug 22, 202693 ms
Aug 29, 202692 ms
Sep 5, 202693 ms
Sep 12, 202693 ms
Sep 19, 202687 ms
Sep 26, 202694 ms
Oct 3, 202692 ms
Oct 10, 202694 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 alaskapublic.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

13 to fix44
  • Render-blocking requests

    3.5 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.

  • Reduce unused JavaScript

    2.9 s · 620 KiB

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

  • Improve image delivery

    2.5 s · 543 KiB

    6 images could be 543 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

  • Mobile performance score: 44

    44/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, brightspotcdn.com and Google/Doubleclick Ads and others), adding 4.2 MB and 1.2 s of main-thread time.

  • Google Tag Manager adds 772 ms

    772 ms

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

  • brightspotcdn.com adds 215 ms

    215 ms

    brightspotcdn.com costs a phone 215 ms of main-thread work and 3.2 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 CSS

    300 ms · 62 KiB

    About 62 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.

  • Legacy JavaScript

    300 ms · 33 KiB

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

  • 9 long tasks on the main thread

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

  • Main-thread work: 2.4 s

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

  • Google/Doubleclick Ads adds 160 ms

    160 ms

    Google/Doubleclick Ads costs a phone 160 ms of main-thread work and 306 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.

  • 1,796 HTML elements

    The page has 1,796 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    11 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (11 KiB).

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

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 18.6 s

    18.6 s

    Your largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Democrat Mary Peltola (left) and Republican Sen. Dan Sulliv…”.

  • First Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 19.0 s

    19.0 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Total Blocking Time: 632 ms

    632 ms

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 82 ms

    82 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 737 ms

    737 ms

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

  • Cumulative Layout Shift: 0.006

    0.006

    The layout barely moves while loading (CLS 0.006, good is under 0.1).

Images and page weight

4 to fix42
  • Page weight: 4.3 MB in 52 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 52 requests on a phone: images 2.3 MB (16), scripts 1.2 MB (11) and fonts 550 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    90 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 in older formats

    2 images (718 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.

  • 2 images far larger than shown

    168 KiB

    2 images are downloaded at several times the size a phone draws them, for example copy-of-debate-for-the-state-2026-email-web-9-26-1200-x-600- at 1,200 px wide, shown at 350 px. Resized copies would save about 168 KiB.

  • About 1.2 g of CO₂ per visit

    1.21 g

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

Accessibility

3 to fixGoogle 9696
  • 31 text elements with low contrast

    31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (5 elements)

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

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 9278
  • No H1 headline

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

  • Title is short (19 characters)

    Your title is only 19 characters: “Alaska Public Media”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

  • 353 internal links, 42 external

    The homepage links to 353 pages on alaskapublic.org and 42 external pages.

5 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Alaska Public Media harnesses the power of multiple media platforms to make a more informed and connected life possible…”.

  • Canonical URL set

    The canonical URL is https://alaskapublic.org/.

  • Structured data in place

    Structured data found: WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://alaskapublic.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://alaskapublic.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix93
  • 2 pages share a meta description

    https://alaskapublic.org/watch and https://alaskapublic.org/listen use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://alaskapublic.org/programs/alaska-insight, https://alaskapublic.org/debate-for-the-state, https://alaskapublic.org/programs/every-little-bit, https://alaskapublic.org/programs/indie-alaska, https://alaskapublic.org/programs/hope and https://alaskapublic.org/programs/in-my-family 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 104 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Identifier 'promoEnabled' has already been declared”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 837 words of copy

    The homepage carries about 837 words of visible text.

3 checks passed
  • 20 calls to action

    The homepage has 20 calls to action, for example “Schedule”, “KSKA Schedule” and “Subscribe: Daily Digest”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 alaskapublic.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on alaskapublic.org, including 18 speed issues, 4 SEO issues and 3 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