Website review, no card needed

ficpa.org logo

ficpa.org website review

Visit site (opens in a new tab)Reviewed 18 October 202645 issues · 88 checks

This review found 45 issues worth fixing on ficpa.org, 17 of them high impact, across 88 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
2.7 s1.2 sApr 25Oct 101.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.1 s
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20261.9 s
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.5 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20262.0 s
Aug 29, 20262.5 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.2 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
116 ms81 msApr 25Oct 10112 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202685 ms
May 2, 202687 ms
May 9, 202687 ms
May 16, 202688 ms
May 23, 202692 ms
May 30, 202693 ms
Jun 6, 202690 ms
Jun 13, 202693 ms
Jun 20, 202693 ms
Jun 27, 202689 ms
Jul 4, 202688 ms
Jul 11, 202688 ms
Jul 18, 202687 ms
Jul 25, 202693 ms
Aug 1, 202695 ms
Aug 8, 202691 ms
Aug 15, 202694 ms
Aug 22, 202687 ms
Aug 29, 202688 ms
Sep 5, 202695 ms
Sep 12, 202696 ms
Sep 19, 202697 ms
Sep 26, 2026100 ms
Oct 3, 2026105 ms
Oct 10, 2026112 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 ficpa.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ficpa.org at 0.4 s0.4 s
  2. ficpa.org at 0.8 s0.8 s
  3. ficpa.org at 1.2 s1.2 s
  4. ficpa.org at 1.6 s1.6 s
  5. ficpa.org at 2.0 s2.0 s
  6. ficpa.org at 2.3 s2.3 s
  7. ficpa.org at 2.7 s2.7 s
  8. ficpa.org at 3.1 s3.1 s

Speed

10 to fix47
  • Use efficient cache lifetimes

    18.4 s · 6.0 MB

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

  • Render-blocking requests

    7.7 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.7 s.

  • Improve image delivery

    4.6 s · 2.3 MB

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

  • Reduce unused JavaScript

    4.0 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

  • Reduce unused CSS

    1.2 s · 246 KiB

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

  • Mobile performance score: 47

    47/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, hsappstatic.net and Facebook and others), adding 1.7 MB and 1.3 s of main-thread time.

  • Google Tag Manager adds 437 ms

    437 ms

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

  • hsappstatic.net adds 332 ms

    332 ms

    hsappstatic.net costs a phone 332 ms of main-thread work and 694 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.9 s

    A phone's processor spends 2.9 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 16 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    48 KiB

    Polyfills for old browsers add 48 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: 19 ms

    19 ms

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

Core Web Vitals

9 to fix100
  • 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: 13.7 s

    13.7 s

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

  • Largest Contentful Paint: 20.3 s

    20.3 s

    Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Legislative Update: FICPA secures Isaias relief For the las…”.

  • Time to Interactive: 27.0 s

    27.0 s

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

  • Speed Index: 13.7 s

    13.7 s

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

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

    +26%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Total Blocking Time: 339 ms

    339 ms

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

  • 16 images without width and height

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

6 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

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

    -19%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 7.4 MB in 94 requests

    7.4 MB

    Your homepage downloads 7.4 MB in 94 requests on a phone: images 3.2 MB (27), scripts 2.5 MB (35) and fonts 1.3 MB (5). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (534 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.

  • 4 images below the first screen load straight away

    4 images further down the page (516 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.10 g

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

6 to fixGoogle 8191
  • 7 buttons without a name

    7 buttons have no accessible name, so screen readers announce just “button”.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • 4 images without alt text

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

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

    All page content should be contained by landmarks: 30 elements on the page fail 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.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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

10 to fixGoogle 6458
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (25 characters)

    Your title is only 25 characters: “Florida Institute of CPAs”. 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.

  • 6 H1 headlines

    There are 6 <h1> headlines (“Legislative Update: FICPA secures Isaias relief”, “Peer to Peer AI & Automation Guidance” and “Registration Open: CPA Day at the Capitol”). 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.

  • No XML sitemap

    No XML sitemap at https://www.ficpa.org/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at ficpa.org/robots.txt, the first file search crawlers ask for.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 117 internal links, 29 external

    The homepage links to 117 pages on ficpa.org and 29 external pages.

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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (834 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.ficpa.org/be-professional-affiliate-member, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 6 pages without a meta description

    https://www.ficpa.org/membership/benefits, https://www.ficpa.org/member_savings_and_insurance_programs, https://www.ficpa.org/membership/types, https://www.ficpa.org/newly-certified-cpas, https://www.ficpa.org/membership and https://www.ficpa.org/membership/ficpa-100 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.

5 checks passed
  • 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.

  • 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=2137396351.1792347376&gtm=45be6ae1v9247301082za20ozb831544…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    93 of 101 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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: 6 customer or partner logos. 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 830 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 9 calls to action

    The homepage has 9 calls to action, for example “Join”, “Why Join?” and “Call for Presenters”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (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.

  • 13 cookies set on arrival

    13

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 ficpa.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

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 45 issues on ficpa.org, including 19 speed issues, 10 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

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