Website review, no card needed
amaiowa.com website review
Visit site (opens in a new tab)Reviewed 3 November 202648 issues · 85 checks
This review found 48 issues worth fixing on amaiowa.com, 15 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
75CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.5 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
Use efficient cache lifetimes
1.9 s · 16.6 MB64 files are served with short cache lifetimes, so returning visitors download them again (16.6 MB).
Render-blocking requests
2.9 s39 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Reduce unused JavaScript
910 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 910 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, mcjobboard.net and Google Tag Manager and others), adding 2.3 MB and 888 ms of main-thread time.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Minify JavaScript
460 ms · 94 KiB94 KiB could be saved by minifying JavaScript.
YouTube adds 360 ms
360 msYouTube costs a phone 360 ms of main-thread work and 982 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.
mcjobboard.net adds 298 ms
298 msmcjobboard.net costs a phone 298 ms of main-thread work and 690 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 157 ms
157 msGoogle Tag Manager costs a phone 157 ms of main-thread work and 331 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 CSS
140 ms · 135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
Legacy JavaScript
150 ms · 17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
140 ms · 6 KiB6 KiB could be saved by minifying CSS.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 140 ms. During a long task the page ignores taps.
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: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 23.0 s
23.0 sThe page becomes fully interactive after 23.0 s. Good is under 3.8 s.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The American Marketing Association (AMA), one of the larges…”. Most of its time is element render delay (1.8 s).
Total Blocking Time: 239 ms
239 msScripts block taps and scrolling for 239 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
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.016
0.016The layout barely moves while loading (CLS 0.016, good is under 0.1).
Images and page weight
Page weight: 18.9 MB in 103 requests
18.9 MBYour homepage downloads 18.9 MB in 103 requests on a phone: images 16.3 MB (22), scripts 2.3 MB (35) and stylesheets 128 KiB (29). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.
3 images in older formats
3 images (1.8 MB) 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 5.4 g of CO₂ per visit
5.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.35 g of CO₂e: 642.2 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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
26 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (4 characters)
Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“About AMA Iowa” and “Our Platinum Sponsors”). One clear main headline is easier for people and search engines.
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 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.
41 internal links, 18 external
The homepage links to 41 pages on amaiowa.com and 18 external pages.
2 checks passed
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.amaiowa.com/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://www.amaiowa.com/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 (425 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.amaiowa.com/masterminds, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://www.amaiowa.com/news has no <title>, so Google invents the link text in results.
2 linked pages hidden from search
https://www.amaiowa.com/events and https://www.amaiowa.com/all-events are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.amaiowa.com/ama-iowa-board-mentorship-program and https://www.amaiowa.com/speaking-opportunities all use the title “American Marketing Association Iowa”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://www.amaiowa.com/ama-iowa-board-mentorship-program, https://www.amaiowa.com/events, https://www.amaiowa.com/all-events, https://www.amaiowa.com/speaking-opportunities and https://www.amaiowa.com/news have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.amaiowa.com/ama-iowa-board-mentorship-program, https://www.amaiowa.com/events, https://www.amaiowa.com/all-events, https://www.amaiowa.com/speaking-opportunities and https://www.amaiowa.com/news have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.amaiowa.com/ama-iowa-board-mentorship-program took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
1 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Best practices
1 broken image
1 image failed to load on a phone, for example https://amai.memberclicks.net/assets/featured-slider-images/2024-NOVAs-1531x524.png.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
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.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 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 365 words of copy
The homepage carries about 365 words of visible text.
4 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Join Today (ama.org)”, “Contact” and “Subscribe”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 trust badge and “over 38,000 members”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before 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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 1 of them by other companies (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.
17 other companies contacted
Loading the homepage contacts 17 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 amaiowa.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2022.
Stack
- CMS
- Joomla
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Hiring
- Hiring
- 1 open role
- Teams
- Account Service & Brand Strategy (1)
- Job board
- bamboohr
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on amaiowa.com, including 16 speed issues, 7 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.