Website review, no card needed

The Ad Council logo

adcouncil.org website review

Visit site (opens in a new tab)Reviewed 2 November 202626 issues · 66 checks

This review found 26 issues worth fixing on adcouncil.org, 7 of them high impact, across 66 checks. The most urgent: page weight: 5.6 MB in 53 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for The Ad Council

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

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

Full-page screenshot of adcouncil.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adcouncil.org at 0.5 s0.5 s
  2. adcouncil.org at 0.9 s0.9 s
  3. adcouncil.org at 1.4 s1.4 s
  4. adcouncil.org at 1.9 s1.9 s
  5. adcouncil.org at 2.4 s2.4 s
  6. adcouncil.org at 2.8 s2.8 s
  7. adcouncil.org at 3.3 s3.3 s
  8. adcouncil.org at 3.8 s3.8 s

Speed

8 to fix77
  • Improve image delivery

    3.7 MB

    3 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, brightspotcdn.com and Optanon and others), adding 5.3 MB and 731 ms of main-thread time.

  • Mobile performance score: 77

    77/100

    Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    800 ms

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

  • brightspotcdn.com adds 270 ms

    270 ms

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

  • Use efficient cache lifetimes

    411 KiB

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

  • Google Tag Manager adds 306 ms

    306 ms

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

  • Reduce unused JavaScript

    337 KiB

    About 337 KiB of JavaScript is downloaded but never used on this page.

  • 6 long tasks on the main thread

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Reduce unused CSS

    80 KiB

    About 80 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 24 ms

    24 ms

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

Core Web Vitals

5 to fix86
  • Time to Interactive: 9.3 s

    9.3 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 3.1 s

    3.1 s

    Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We believe in fostering a society where everyone can thrive…”. Most of its time is element render delay (2.4 s).

  • Total Blocking Time: 281 ms

    281 ms

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.6 MB in 53 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 53 requests on a phone: images 4.6 MB (11), scripts 729 KiB (15) and fonts 182 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

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

  • About 1.6 g of CO₂ per visit

    1.60 g

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

2 checks passed
  • 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

3 to fix87
  • [role] values are not valid

    [role] values are not valid (1 element).

  • 21 tap targets too small

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

  • 2 text elements with low contrast

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

  • Headings skip levels

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

  • SVG elements with an img role do not have an accessible text alternative

    SVG elements with an img role do not have an accessible text alternative (18 elements).

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

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

1 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

SEO

2 to fixGoogle 10091
  • No structured data

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

  • Meta description is long (191 characters)

    Your meta description is 191 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 107 internal links, 4 external

    The homepage links to 107 pages on adcouncil.org and 4 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Our History/About”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Welcome to the Ad Council | The Ad Council”.

  • Canonical URL set

    The canonical URL is https://www.adcouncil.org/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://www.adcouncil.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://adcouncil.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

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://www.pages01.net/WTS/event.jpeg?accesskey=21baa39d-179f1c501f9-a7548a3fbbe3d9f8bac3b3472c6792ee&v=1.31&isNewSession=1&type=pageview&isNewVisitor=1&sessionGUID=c68e31ca-b113-d138-aa67-ca66b2202c.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

2 checks passed
  • Tap targets are thumb-sized

    10 of 12 tappable elements near the top are at least 24 px.

  • 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: 11 testimonial or review blocks. 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 671 words of copy

    The homepage carries about 671 words of visible text.

3 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “Sign Up For Our Newsletter”, “Join Our Team” and “Contact Us”.

  • 6 short forms

    6 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

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

  • 18 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 adcouncil.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
Hosting
AWS

Hiring

Hiring
2 open roles
Teams
Marketing & Communications (1)
Job board
greenhouse

Company

Employees
185
Founded
1941

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on adcouncil.org, including 13 speed issues, 2 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