Website review, no card needed

imanet.org logo

imanet.org website review

Visit site (opens in a new tab)Reviewed 4 November 202643 issues · 83 checks

This review found 43 issues worth fixing on imanet.org, 21 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
6.8 s4.1 sMay 16Oct 315.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20266.5 s
May 23, 20266.0 s
May 30, 20265.7 s
Jun 6, 20265.3 s
Jun 13, 20265.2 s
Jun 20, 20265.2 s
Jun 27, 20265.2 s
Jul 4, 20265.3 s
Jul 11, 20265.3 s
Jul 18, 20265.3 s
Jul 25, 20265.2 s
Aug 1, 20265.0 s
Aug 8, 20265.0 s
Aug 15, 20264.6 s
Aug 22, 20264.4 s
Aug 29, 20264.5 s
Sep 5, 20264.5 s
Sep 12, 20264.7 s
Sep 19, 20264.8 s
Sep 26, 20265.0 s
Oct 3, 20265.1 s
Oct 10, 20265.1 s
Oct 17, 20265.2 s
Oct 24, 20265.2 s
Oct 31, 20265.2 s
Real-visitor tap response (INP)75th percentile, phones
492 ms302 msMay 16Oct 31464 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026378 ms
May 23, 2026368 ms
May 30, 2026351 ms
Jun 6, 2026334 ms
Jun 13, 2026326 ms
Jun 20, 2026324 ms
Jun 27, 2026327 ms
Jul 4, 2026333 ms
Jul 11, 2026337 ms
Jul 18, 2026343 ms
Jul 25, 2026354 ms
Aug 1, 2026358 ms
Aug 8, 2026394 ms
Aug 15, 2026431 ms
Aug 22, 2026437 ms
Aug 29, 2026443 ms
Sep 5, 2026444 ms
Sep 12, 2026446 ms
Sep 19, 2026452 ms
Sep 26, 2026455 ms
Oct 3, 2026461 ms
Oct 10, 2026466 ms
Oct 17, 2026469 ms
Oct 24, 2026470 ms
Oct 31, 2026464 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 imanet.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix29
  • Use efficient cache lifetimes

    5.7 s · 2.0 MB

    54 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

  • Improve image delivery

    3.6 s · 1.0 MB

    3 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.

  • Reduce unused CSS

    1.5 s · 335 KiB

    About 335 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Render-blocking requests

    1.6 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.1 s

    A phone's processor spends 5.1 s on main-thread work while loading, 2.6 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, Facebook and Hubspot and others), adding 1.9 MB and 1.8 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 837 KiB

    About 837 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 869 ms

    869 ms

    Google Tag Manager costs a phone 869 ms of main-thread work and 900 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.

  • Facebook adds 319 ms

    319 ms

    Facebook costs a phone 319 ms of main-thread work and 323 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 210 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need.

  • 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: 70 ms

    70 ms

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

Core Web Vitals

13 to fix33
  • 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.

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 25.6 s

    25.6 s

    The page becomes fully interactive after 25.6 s. Good is under 3.8 s.

  • Total Blocking Time: 896 ms

    896 ms

    Scripts block taps and scrolling for 896 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Cumulative Layout Shift: 0.296

    0.296

    The layout shifts by 0.296 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user INP: 402 ms

    402 ms

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

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

    +25%

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

  • Speed Index: 4.9 s

    4.9 s

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

  • 2 images without width and height

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

Images and page weight

2 to fix60
  • Page weight: 4.4 MB in 159 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 159 requests on a phone: scripts 2.4 MB (56), images 1.3 MB (33) and stylesheets 340 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (905 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.

  • About 1.2 g of CO₂ per visit

    1.25 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.25 g of CO₂e: 149.6 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

7 to fixGoogle 8289
  • 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.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h2 → h5 and h2 → h6), 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9285
  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “The Institute of Management Accountants and Financial Professionals | IMA”.

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

  • 26 internal links, 12 external

    The homepage links to 26 pages on imanet.org and 12 external pages.

5 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “IMA is the worldwide association for accounting and finance professionals. Explore certifications, CPE, networking, and…”.

  • One H1 headline

    Your main headline reads: “We set the standard for accounting and finance professionals worldwide”.

  • 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.imaglobal.org/sitemap.xml.

AI search readiness

1 to fix88
  • 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.imaglobal.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 (494 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix62
  • 1 linked page is broken

    Your homepage links to https://www.imaglobal.org/learn, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 5 pages share a title

    https://www.imaglobal.org/catalog, https://www.imaglobal.org/pages/grow-your-skills, https://www.imaglobal.org/pages/news, https://www.imaglobal.org/pages/statement-of-ethics and https://www.imaglobal.org/pages/donate all use the title “Institute of Management Accountants”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://www.imaglobal.org/catalog, https://www.imaglobal.org/pages/grow-your-skills, https://www.imaglobal.org/pages/news, https://www.imaglobal.org/pages/statement-of-ethics and https://www.imaglobal.org/pages/donate use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://www.imaglobal.org/catalog, https://www.imaglobal.org/pages/grow-your-skills, https://www.imaglobal.org/pages/news, https://www.imaglobal.org/pages/statement-of-ethics and https://www.imaglobal.org/pages/donate 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 16 found) and read each the way a search engine does.

4 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187241175&Ver=2&mid=bdd9dee4-636f-4e52-9969-83a9db298326&bo=1&sid=37e70930d87d11f1a383c34a7733536b&vid=37e73210d87d11f19ea0dd53abbbd2be&vids=1&msclkid=N&pi=918639831&l.

  • 5 small tap targets

    5 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

    Social proof on the homepage: “120k+ members”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 493 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join IMA”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Join IMA”, “Learn more about corporate memberships” and “Get your certification”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 20 cookies set on arrival

    20

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

  • 44 other companies contacted

    Loading the homepage contacts 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 imanet.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
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Enflow B.V.

Hiring

Hiring
21 open roles
Job board
careers page

Company

Founded
1919
Headquarters
Montvale

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on imanet.org, including 23 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

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