Website review, no card needed

asco.org logo

asco.org website review

Visit site (opens in a new tab)Reviewed 26 October 202634 issues · 73 checks

This review found 34 issues worth fixing on asco.org, 10 of them high impact, across 73 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
5.8 s3.7 sMay 9Oct 245.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.2 s
May 16, 20264.3 s
May 23, 20264.3 s
May 30, 20264.1 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20264.0 s
Jun 27, 20264.3 s
Jul 4, 20264.9 s
Jul 11, 20265.1 s
Jul 18, 20265.1 s
Jul 25, 20265.2 s
Aug 1, 20265.3 s
Aug 8, 20265.3 s
Aug 15, 20265.2 s
Aug 22, 20265.2 s
Aug 29, 20265.1 s
Sep 5, 20265.0 s
Sep 12, 20265.1 s
Sep 19, 20265.2 s
Sep 26, 20265.2 s
Oct 3, 20265.3 s
Oct 10, 20265.3 s
Oct 17, 20265.4 s
Oct 24, 20265.6 s
Real-visitor tap response (INP)75th percentile, phones
214 ms126 msMay 9Oct 24191 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026147 ms
May 16, 2026149 ms
May 23, 2026155 ms
May 30, 2026145 ms
Jun 6, 2026138 ms
Jun 13, 2026139 ms
Jun 20, 2026136 ms
Jun 27, 2026138 ms
Jul 4, 2026150 ms
Jul 11, 2026154 ms
Jul 18, 2026157 ms
Jul 25, 2026166 ms
Aug 1, 2026176 ms
Aug 8, 2026180 ms
Aug 15, 2026194 ms
Aug 22, 2026197 ms
Aug 29, 2026194 ms
Sep 5, 2026194 ms
Sep 12, 2026194 ms
Sep 19, 2026196 ms
Sep 26, 2026204 ms
Oct 3, 2026203 ms
Oct 10, 2026196 ms
Oct 17, 2026194 ms
Oct 24, 2026191 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 asco.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix
  • Main-thread work: 3.0 s

    A phone's processor spends 3.0 s on main-thread work while loading, 1.8 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 (FullStory, Adobe Tag Manager and Optanon and others), adding 807 KiB and 433 ms of main-thread time.

  • Document request latency

    133 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

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

  • First Contentful Paint: 6.9 s

    6.9 s

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

  • Speed Index: 10.0 s

    10.0 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Tap response (INP) got 30% slower for real visitors

    +30%

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

  • Largest content (LCP) got 28% slower for real visitors

    +28%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 958 ms

    958 ms

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

  • 6 images without width and height

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

3 checks passed
  • Real-user INP: 169 ms

    169 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix78
  • Page weight: 3.8 MB in 121 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 121 requests on a phone: scripts 1.5 MB (48), images 1.2 MB (27) and other files 594 KiB (38). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (300 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.07 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 fixGoogle 9195
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Headings skip levels

    Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 42 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: 42 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8378
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

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

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 12 internal links, 1 external

    The homepage links to 12 pages on asco.org and 1 external page.

4 checks passed
  • One H1 headline

    Your main headline reads: “Important Dates”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “American Society of Clinical Oncology - ASCO”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    23%

    A phone browser shows 421 words, but the HTML your server sends has only 96. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

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

Other pages

3 to fix83
  • 6 pages share a title

    https://www.asco.org/guidelines, https://www.asco.org/get-involved/membership/dues, https://www.asco.org/meetings-education/asco-sep, https://www.asco.org/gi/registration-hotels/registration-details, https://www.asco.org/gu/registration-hotels/registration-details and https://www.asco.org/annual-meeting/program/asco-voices all use the title “ASCO – American Society of Clinical Oncology”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://www.asco.org/abstracts, https://www.asco.org/guidelines, https://www.asco.org/journals, https://www.asco.org/posters, https://www.asco.org/slides and https://www.asco.org/videos and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.asco.org/abstracts, https://www.asco.org/guidelines, https://www.asco.org/get-involved/membership/dues, https://www.asco.org/meetings-education/asco-sep, https://www.asco.org/gi/registration-hotels/registration-details and https://www.asco.org/gu/registration-hotels/registration-details and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://www.asco.org/abstracts, https://www.asco.org/guidelines, https://www.asco.org/get-involved/membership/dues, https://www.asco.org/meetings-education/asco-sep, https://www.asco.org/gi/registration-hotels/registration-details and https://www.asco.org/gu/registration-hotels/registration-details and 1 other 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.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

5 to fixGoogle 4673
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=26243915&Ver=2&mid=45ff8166-6215-4ba1-afc0-9ffd0b45dff4&bo=1&sid=13cfcaf0d18311f18689cd55595bf2ca&vid=13cff6f0d18311f19e102ffe4977137c&vids=1&msclkid=N&pi=918639831&lg.

  • 3 third-party cookies

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

  • Deprecated browser APIs

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    22 of 25 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 421 words of visible text.

1 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Register”.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, Meta Pixel and Microsoft Ads and 1 more (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.

  • 19 cookies set on arrival

    19

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

  • 41 other companies contacted

    Loading the homepage contacts 41 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 asco.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
Angular
Hosting
CloudFront

Company

Employees
446
Founded
1964
Headquarters
Alexandria

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on asco.org, including 10 speed issues, 5 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