affinityplan.org website review

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

About 844 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

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

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

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

3 images could be 268 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

The page goes through 2 redirects before it starts loading, costing about 761 ms. Link and advertise the final URL directly.

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

The HTML itself could arrive about 400 ms sooner: redirects, a slow server response or missing compression delay everything after it.

59 KiB could be saved by minifying JavaScript.

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

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

4 third-party services load with your homepage (gbqofs.com, cloudfront.net and glassboxdigital.io and others), adding 337 KiB and 35 ms of main-thread time.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Simple hero 384x214 13”.

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

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

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

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

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

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

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

Your homepage downloads 2.1 MB in 46 requests on a phone: scripts 1.3 MB (22), images 286 KiB (4) and stylesheets 224 KiB (3). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 72.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 image has no alt text, which hurts accessibility and image search.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 10 characters: “Error Page”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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 at https://www.molinahealthcare.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

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

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.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

No character set is declared, so some characters can render as gibberish.

1 error was logged to the browser console during Google's test (“Uncaught TypeError: Cannot read properties of undefined (reading 'web_flow_target')”).

2 images are served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

molinahealthcare.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 47 words of visible text; thin pages give Google and first-time buyers little to go on.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.