Website review, no card needed
pancan.org website review
Visit site (opens in a new tab)Reviewed 26 October 202647 issues · 98 checks
This review found 47 issues worth fixing on pancan.org, 23 of them high impact, across 98 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.0 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.2 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.2 s |
| Oct 24, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 195 ms |
| May 16, 2026 | 194 ms |
| May 23, 2026 | 196 ms |
| May 30, 2026 | 196 ms |
| Jun 6, 2026 | 194 ms |
| Jun 13, 2026 | 194 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 193 ms |
| Jul 25, 2026 | 193 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 197 ms |
| Aug 15, 2026 | 202 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 204 ms |
| Sep 19, 2026 | 197 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 194 ms |
| Oct 10, 2026 | 196 ms |
| Oct 17, 2026 | 201 ms |
| Oct 24, 2026 | 203 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
Speed
Reduce unused JavaScript
3.4 s · 2.3 MBAbout 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.
Use efficient cache lifetimes
3.4 s · 1.4 MB106 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Render-blocking requests
1.9 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Google Tag Manager adds 1.3 s
1.3 sGoogle Tag Manager costs a phone 1.3 s of main-thread work and 1.2 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.
Google CDN adds 1.1 s
1.1 sGoogle CDN costs a phone 1.1 s of main-thread work and 1.5 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: 27
27/100Your mobile performance score is 27 (desktop: 45). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.2 s
A phone's processor spends 8.2 s on main-thread work while loading, 4.9 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 (Google Tag Manager, Google CDN and fundraiseup.com and others), adding 3.8 MB and 3.5 s of main-thread time.
Reduce unused CSS
530 ms · 95 KiBAbout 95 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 530 ms faster on a phone.
Improve image delivery
361 KiB13 images could be 361 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 295 ms. During a long task the page ignores taps.
cloudfront.net adds 188 ms
188 mscloudfront.net costs a phone 188 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.
Legacy JavaScript
250 ms · 53 KiBPolyfills for old browsers add 53 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Minify JavaScript
170 ms · 46 KiB46 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
150 ms · 62 KiB62 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 8.0 s
8.0 sThe first text or image appears after 8.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 18.1 s
18.1 sYour largest element takes 18.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “hero ps text”.
Time to Interactive: 40.6 s
40.6 sThe page becomes fully interactive after 40.6 s. Good is under 3.8 s.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
38 images without width and height
38 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 195 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 173 ms
173 msReal visitors wait 173 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user TTFB: 735 ms
735 msReal visitors wait 735 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
Images and page weight
Page weight: 7.1 MB in 284 requests
7.1 MBYour homepage downloads 7.1 MB in 284 requests on a phone: scripts 4.4 MB (83), other files 1.1 MB (75) and images 841 KiB (85). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
66 KiB1 image is downloaded at several times the size a phone draws it, for example Alyssa-Lile-Blog-Header.jpg at 733 px wide, shown at 100 px. Resized copies would save about 66 KiB.
7 images below the first screen load straight away
7 images further down the page (289 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.0 g of CO₂ per visit
2.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.01 g of CO₂e: 241.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “Pancreatic Cancer Action Network – Research, Patient Support, Resources”.
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://pancan.org/wp-content/uploads/2018/04/small-logo.png")”.
128 internal links, 34 external
The homepage links to 128 pages on pancan.org and 34 external pages.
5 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “We're the national organization providing support, resources, volunteer opportunities and hope for people fighting panc…”.
Canonical URL set
The canonical URL is https://pancan.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.pancan.org/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://pancan.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (691 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://pancan.org/stories has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://pancan.org/es and https://pancan.org/facing-pancreatic-cancer/patient-services/educational-events 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 62 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.
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 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=151003667&tm=gtm002&Ver=2&mid=b7270793-14a3-4fa1-912f-cf9c1d90f74e&bo=1&sid=99ee0430d11f11f1b5373d349ac50f02&vid=99ee41c0d11f11f18157f96bb9450090&vids=1&msclkid=N&pi=9.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “The pseudo class ":first-child" is potentially unsafe when doing server-side rendering. Try changing it to ":first-of-t…”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
87 of 92 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 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.
About 746 words of copy
The homepage carries about 746 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US” and “JOIN OUR COMMUNITY”.
8 calls to action
The homepage has 8 calls to action, for example “CONTACT US”, “Join Our Community” and “Contact Us”.
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 Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
12 trackers load before any consent
12Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 7 mores (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.
49 cookies set on arrival
49Opening the homepage sets 49 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.
63 other companies contacted
Loading the homepage contacts 63 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 pancan.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Analytics
- Google 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 47 issues on pancan.org, including 21 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.