Website review, no card needed

centivo.com logo

centivo.com website review

Visit site (opens in a new tab)Reviewed 4 November 202625 issues · 80 checks

This review found 25 issues worth fixing on centivo.com, 6 of them high impact, across 80 checks. The most urgent: render-blocking requests. 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.0 s1.5 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
164 ms84 msMay 16Oct 31101 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026129 ms
May 23, 2026114 ms
May 30, 2026110 ms
Jun 6, 2026131 ms
Jun 13, 2026146 ms
Jun 20, 2026155 ms
Jun 27, 2026155 ms
Jul 4, 2026138 ms
Jul 11, 2026113 ms
Jul 18, 2026102 ms
Jul 25, 202696 ms
Aug 1, 202693 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202695 ms
Aug 29, 202695 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 2026102 ms
Sep 26, 2026111 ms
Oct 3, 2026111 ms
Oct 10, 2026117 ms
Oct 17, 2026112 ms
Oct 24, 202699 ms
Oct 31, 2026101 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 centivo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. centivo.com at 0.4 s0.4 s
  2. centivo.com at 0.8 s0.8 s
  3. centivo.com at 1.2 s1.2 s
  4. centivo.com at 1.6 s1.6 s
  5. centivo.com at 2.0 s2.0 s
  6. centivo.com at 2.4 s2.4 s
  7. centivo.com at 2.8 s2.8 s
  8. centivo.com at 3.2 s3.2 s

Speed

10 to fix68
  • Render-blocking requests

    1.5 s

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

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 2.8 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 CDN, Google Tag Manager and Hubspot and others), adding 2.2 MB and 1.6 s of main-thread time.

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    859 KiB

    About 859 KiB of JavaScript is downloaded but never used on this page.

  • Google CDN adds 573 ms

    573 ms

    Google CDN costs a phone 573 ms of main-thread work and 1.1 MB 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.

  • Google Tag Manager adds 508 ms

    508 ms

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

  • Use efficient cache lifetimes

    497 KiB

    17 files are served with short cache lifetimes, so returning visitors download them again (497 KiB).

  • 20 long tasks on the main thread

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

  • Hubspot adds 209 ms

    209 ms

    Hubspot costs a phone 209 ms of main-thread work and 317 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.

  • Improve image delivery

    42 KiB

    2 images could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    20 KiB

    About 20 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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: 1 ms

    1 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 19.3 s

    19.3 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Speed Index: 4.7 s

    4.7 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

10 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.2 s

    2.2 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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.3 s

    1.3 s

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

  • Real-user TTFB: 482 ms

    482 ms

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

  • Tap response (INP) got 18% faster for real visitors

    -18%

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

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

    -13%

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

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “You wouldn’t trust a random stranger with your hair. Why sh…”.

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

1 to fix70
  • Page weight: 8.4 MB in 84 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 84 requests on a phone: media 5.5 MB (2), scripts 2.1 MB (22) and other files 378 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (35 KiB) is 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.

  • 2 images below the first screen load straight away

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

  • About 2.4 g of CO₂ per visit

    2.37 g

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

3 to fixGoogle 9797
  • Orphan list items

    Some list items are not inside a list.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 42 internal links, 14 external

    The homepage links to 42 pages on centivo.com and 14 external pages.

8 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Primary-care-centered self-funded health plans for employers of 50–3,000. Save ~15-30% vs. fully-insured. Serving WI, T…”.

  • One H1 headline

    Your main headline reads: “You wouldn’t trust a random stranger with your hair. Why should your healthcare be any different?”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Self-Funded Health Plans for Employers | Centivo”.

  • Canonical URL set

    The canonical URL is https://centivo.com/.

  • Structured data in place

    Structured data found: Article, Corporation, FAQPage, ImageObject and ItemList.

  • 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://centivo.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://centivo.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.

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 2 pages share a title

    https://centivo.com/privacy-policy and https://centivo.com/notice-of-privacy-practices all use the title “Privacy Policy | Centivo”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://centivo.com/privacy-policy, https://centivo.com/notice-of-privacy-practices, https://centivo.com/terms-and-conditions and https://centivo.com/accessibility 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 18 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.

  • Canonical URLs point to themselves

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

  • 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

2 to fixGoogle 9687
  • 3 small tap targets

    3 of 13 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 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • 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.

  • Thin social proof

    Social proof on the homepage: 7 testimonial or review blocks. 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 874 words of copy

    The homepage carries about 874 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: “Let's Get Started”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Let's Get Started” and “Contact us”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

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

Privacy and tracking

  • 7 trackers load before any consent

    7

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

  • 32 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Analytics
Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
10 open roles
Teams
Claims (2), Corporate (2), Application Support & Help Desk (1), Client Success (1)
Job board
ashby

Company

Headquarters
Buffalo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on centivo.com, including 14 speed issues and 3 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