Website review, no card needed
iaapa.org website review
Visit site (opens in a new tab)Reviewed 28 October 202636 issues · 86 checks
This review found 36 issues worth fixing on iaapa.org, 14 of them high impact, across 86 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.2 s |
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.7 s |
| Jun 6, 2026 | 5.2 s |
| Jun 13, 2026 | 5.6 s |
| Jun 20, 2026 | 5.9 s |
| Jun 27, 2026 | 6.0 s |
| Jul 4, 2026 | 6.2 s |
| Jul 11, 2026 | 6.2 s |
| Jul 18, 2026 | 6.1 s |
| Jul 25, 2026 | 5.8 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 179 ms |
| May 16, 2026 | 181 ms |
| May 23, 2026 | 189 ms |
| May 30, 2026 | 206 ms |
| Jun 6, 2026 | 222 ms |
| Jun 13, 2026 | 222 ms |
| Jun 20, 2026 | 227 ms |
| Jun 27, 2026 | 226 ms |
| Jul 4, 2026 | 227 ms |
| Jul 11, 2026 | 241 ms |
| Jul 18, 2026 | 251 ms |
| Jul 25, 2026 | 242 ms |
| Aug 1, 2026 | 218 ms |
| Aug 8, 2026 | 200 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 189 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 174 ms |
| Oct 3, 2026 | 172 ms |
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 172 ms |
| Oct 24, 2026 | 168 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.5 s · 998 KiBAbout 998 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 1.1 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: 29
29/100Your mobile performance score is 29 (desktop: 52). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
2.1 MB26 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Facebook and others), adding 2.3 MB and 1.7 s of main-thread time.
Render-blocking requests
750 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused CSS
600 ms · 111 KiBAbout 111 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
2,754 HTML elements
The page has 2,754 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google/Doubleclick Ads adds 143 ms
143 msGoogle/Doubleclick Ads costs a phone 143 ms of main-thread work and 307 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.
Optanon adds 81 ms
81 msOptanon costs a phone 81 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Improve image delivery
143 KiB6 images could be 143 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
66 KiBPolyfills for old browsers add 66 KiB JavaScript that modern phones do not need.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.6 s
16.6 sYour largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 24.4 s
24.4 sThe page becomes fully interactive after 24.4 s. Good is under 3.8 s.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 913 ms
913 msScripts block taps and scrolling for 913 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.194
0.194The layout shifts by 0.194 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 179 ms to 168 ms 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: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 162 ms
162 msReal visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 781 ms
781 msReal visitors wait 781 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.2 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.1 MB in 148 requests
5.1 MBYour homepage downloads 5.1 MB in 148 requests on a phone: scripts 2.4 MB (57), media 1.7 MB (1) and fonts 453 KiB (9). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 173.4 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 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
280 internal links, 17 external
The homepage links to 280 pages on iaapa.org and 17 external pages.
7 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “We are IAAPA. We connect the diverse and dynamic attractions industry. Through our community, we grow and improve our p…”.
One H1 headline
Your main headline reads: “Join the fun business”.
Title: 59 characters
Your title is a healthy 59 characters: “IAAPA | The Global Association for the Attractions Industry”.
Canonical URL set
The canonical URL is https://iaapa.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.
XML sitemap found
Your XML sitemap is reachable at https://iaapa.org/sitemap.xml.
AI search readiness
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://iaapa.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 (2,031 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://iaapa.org/node/1 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
10 pages share a title
/, https://iaapa.org/node/1, https://iaapa.org/ar/node/1, https://iaapa.org/zh-hans/node/1, https://iaapa.org/de/node/1 and https://iaapa.org/es/node/1 and 4 others all use the title “IAAPA | The Global Association for the Attractions Industry”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages share a meta description
https://iaapa.org/node/1, https://iaapa.org/ar/node/1, https://iaapa.org/zh-hans/node/1, https://iaapa.org/de/node/1, https://iaapa.org/es/node/1 and https://iaapa.org/fr/node/1 and 3 others use the same meta description. A description written for each page earns more clicks.
1 page slow to respond
https://iaapa.org/ja/node/1 took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 114 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
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
7 small tap targets
7 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
A 11-field form
Your longest form asks for 11 fields (0 required). Every extra field lowers completion.
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 1,053 words of copy
The homepage carries about 1,053 words of visible text.
2 checks passed
16 calls to action
The homepage has 16 calls to action, for example “Contact Us”, “Book a Meeting or Event” and “Request Support”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
33 other companies contacted
Loading the homepage contacts 33 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 iaapa.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
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Founded
- 1918
- Headquarters
- Orlando
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 iaapa.org, including 17 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.