conning.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Optanon and others), adding 1.1 MB and 699 ms of main-thread time.

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

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

About 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

3 KiB could be saved by minifying JavaScript.

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 visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Investment Solutions Designed for Insurers Our deep investm…”.

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 101 requests on a phone: images 3.3 MB (25), scripts 1.1 MB (30) and other files 73 KiB (30). Under 2 MB keeps phones on slow connections fast.

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

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

57 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Some list items are not inside a list.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

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

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

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

There are 6 <h1> headlines (“Investment Solutions Designed for Insurers”, “The Conning Advantage” and “We Value Diverse Voices”). One clear main headline is easier for people and search engines.

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.

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

The homepage links to 81 pages on conning.com and 13 external pages.

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.

/investment-expertise/investment-strategy-development, /investment-expertise/investment-accounting-and-reporting, /software-and-services/economic-scenario-generator, /software-and-services/portfolio-analysis, /insurance-expertise and /insurance-expertise/insurance-solutions and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://qvdt3feo.com/events.js' violates the following Content Security Policy directive: "script-s…”.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

conning.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,416 words of visible text.

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.

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

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

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