Website review, no card needed
mma.org website review
Visit site (opens in a new tab)Reviewed 23 October 202639 issues · 95 checks
This review found 39 issues worth fixing on mma.org, 15 of them high impact, across 95 checks. The most urgent: render-blocking requests. 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
80B- #46,165 of 117,227 reviewed websitesbeats 55%
- #30,843 of 66,877 online storesbeats 47%
- #616 of 2,691 WooCommerce storesbeats 73%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 934 ms |
| May 9, 2026 | 931 ms |
| May 16, 2026 | 929 ms |
| May 23, 2026 | 926 ms |
| May 30, 2026 | 933 ms |
| Jun 6, 2026 | 919 ms |
| Jun 13, 2026 | 911 ms |
| Jun 20, 2026 | 907 ms |
| Jun 27, 2026 | 898 ms |
| Jul 4, 2026 | 902 ms |
| Jul 11, 2026 | 899 ms |
| Jul 18, 2026 | 907 ms |
| Jul 25, 2026 | 921 ms |
| Aug 1, 2026 | 915 ms |
| Aug 8, 2026 | 911 ms |
| Aug 15, 2026 | 884 ms |
| Aug 22, 2026 | 862 ms |
| Aug 29, 2026 | 863 ms |
| Sep 5, 2026 | 880 ms |
| Sep 12, 2026 | 889 ms |
| Sep 19, 2026 | 895 ms |
| Sep 26, 2026 | 899 ms |
| Oct 3, 2026 | 880 ms |
| Oct 10, 2026 | 882 ms |
| Oct 17, 2026 | 879 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 76 ms |
| May 9, 2026 | 75 ms |
| May 16, 2026 | 76 ms |
| May 23, 2026 | 76 ms |
| May 30, 2026 | 76 ms |
| Jun 6, 2026 | 75 ms |
| Jun 13, 2026 | 73 ms |
| Jun 20, 2026 | 72 ms |
| Jun 27, 2026 | 71 ms |
| Jul 4, 2026 | 72 ms |
| Jul 11, 2026 | 73 ms |
| Jul 18, 2026 | 75 ms |
| Jul 25, 2026 | 76 ms |
| Aug 1, 2026 | 74 ms |
| Aug 8, 2026 | 73 ms |
| Aug 15, 2026 | 71 ms |
| Aug 22, 2026 | 71 ms |
| Aug 29, 2026 | 71 ms |
| Sep 5, 2026 | 72 ms |
| Sep 12, 2026 | 72 ms |
| Sep 19, 2026 | 73 ms |
| Sep 26, 2026 | 73 ms |
| Oct 3, 2026 | 71 ms |
| Oct 10, 2026 | 71 ms |
| Oct 17, 2026 | 71 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
Render-blocking requests
4.2 s40 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Reduce unused JavaScript
2.7 s · 608 KiBAbout 608 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 57). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,665 HTML elements
The page has 4,665 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
700 ms · 256 KiB10 images could be 256 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Reduce unused CSS
750 ms · 150 KiBAbout 150 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
400 ms · 72 KiB7 files are served with short cache lifetimes, so returning visitors download them again (72 KiB).
Google Tag Manager adds 245 ms
245 msGoogle Tag Manager costs a phone 245 ms of main-thread work and 318 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 271 ms. During a long task the page ignores taps.
Vimeo adds 57 ms
57 msVimeo costs a phone 57 ms of main-thread work and 538 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Vimeo and Google Analytics and others), adding 1,005 KiB and 323 ms of main-thread time.
Legacy JavaScript
100 ms · 8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
15 KiB15 KiB could be saved by minifying JavaScript.
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
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: 111 ms
111 msYour server sent the HTML in 111 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 10.5 s
10.5 sThe first text or image appears after 10.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 18.7 s
18.7 sYour largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MMA to hold Legislative Breakfast Meetings Oct. 16, 23, 30”.
Time to Interactive: 20.3 s
20.3 sThe page becomes fully interactive after 20.3 s. Good is under 3.8 s.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 516 ms
516 msScripts block taps and scrolling for 516 ms in total while the page loads. Good is under 200 ms.
29 images without width and height
29 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 76 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s 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: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 84 ms
84 msReal visitors wait 84 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 723 ms
723 msReal visitors wait 723 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 204 requests
3.5 MBYour homepage downloads 3.5 MB in 204 requests on a phone: scripts 1.7 MB (69), images 1.0 MB (70) and fonts 375 KiB (12). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (319 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.
7 images below the first screen load straight away
7 images further down the page (283 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 119.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
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.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
25 images without alt text
25 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (99 elements)
All page content should be contained by landmarks: 99 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.
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.
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, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 9 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.
45 links with vague text
45 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
48 H1 headlines
There are 48 <h1> headlines (“We are the voice of cities & towns in Massachuset…”, “We are the voice of cities & towns in Massachuset…” and “MMA to hold Legislative Breakfast Meetings Oct. 1…”). One clear main headline is easier for people and search engines.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
328 internal links, 708 external
The homepage links to 328 pages on mma.org and 708 external pages.
5 checks passed
Title: 41 characters
Your title is a healthy 41 characters: “Massachusetts Municipal Association (MMA)”.
Canonical URL set
The canonical URL is https://www.mma.org/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
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.mma.org/sitemap_index.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.mma.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 (11,950 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://www.mma.org/municipal-marketplace/job-ads, https://www.mma.org/municipal-marketplace, https://www.mma.org/about-mma/contact-us, https://www.mma.org/members, https://www.mma.org/members/member-communities and https://www.mma.org/members/mayors and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mma.org/massachusetts-selectmens-association, whose canonical is https://www.mma.org/members/msa. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://www.mma.org/municipal-marketplace/job-ads, https://www.mma.org/municipal-marketplace, https://www.mma.org/about-mma/contact-us, https://www.mma.org/members, https://www.mma.org/members/member-communities and https://www.mma.org/members/massachusetts-municipal-communicators and 3 others 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 133 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 third-party cookies
2 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.”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
18 of 22 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.
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 11,050 words of copy
The homepage carries about 11,050 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “LEARN MORE”.
51 calls to action
The homepage has 51 calls to action, for example “Contact Us”, “Newsletter Sign up” and “Learn more”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 1 customer or partner logo, a star rating and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link 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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 2 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.
14 other companies contacted
Loading the homepage contacts 14 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 mma.org, 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 © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- 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 39 issues on mma.org, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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.