candf.com website review

Your mobile performance score is 100. That is in Google's “good” band (90 and up).

A phone's processor spends 0.5 s on main-thread work while loading, 26 ms of it running JavaScript. That is comfortably low.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 134 ms to 100 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 2.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

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

The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

Visually, the page fills in at 1.4 s (Speed Index), inside the 3.4 s “good” threshold.

Scripts block the page for only 0 ms while loading. Good is under 200 ms.

The page is fully interactive after 1.8 s.

Your homepage downloads 506 KiB in 22 requests on a phone: images 410 KiB (16), stylesheets 67 KiB (4) and HTML 28 KiB (1). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

Images below the first screen wait until the visitor scrolls to them.

No image is downloaded at more than three times the size it is drawn on a phone.

All 46 images in the HTML carry an alt attribute.

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

Your meta description is 129 characters: “Transform your business with C&F's data-driven solutions. Enhance efficiency, drive growth, and stay competitive. Learn…”.

Your main headline reads: “Advanced data solutions for business excellence”.

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

Structured data found: Organization, WebPage and WebSite.

robots.txt is in place and points crawlers to your sitemap.

Your XML sitemap is reachable at https://candf.com/sitemap_index.xml.

Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

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

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

The site publishes /llms.txt (103 KiB, 316 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

All 15 pages we checked loaded without an error.

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

All 15 pages that loaded have a meta description.

Every page we checked has its own title.

Each page we checked has a main headline.

All 15 pages that loaded have a <title>.

The page declares a mobile viewport.

The homepage is served over HTTPS (candf.com).

The certificate from Let's Encrypt · YR2 verifies for candf.com and is valid for another 76 days.

X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

Strict-Transport-Security is set, so browsers always use https.

http://candf.com redirects to the secure version.

The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

All 44 links checked from your homepage (40 internal, 4 external) answered without errors.

candf.com was registered in May 1995 through Key-Systems GmbH. An established domain carries more trust with email providers and search engines.

candf.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

candf.com is registered until May 2027.

On a phone, the first screen shows a clear next step: “Download the guide”.

The homepage has 6 calls to action, for example “Join Us”, “Contact us” and “Download the guide”.

2 short forms (1 field at most) are right on the homepage.

Analytics detected: Google Tag Manager.

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

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

DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com a:cloudserver3222233-3222264.home.pl a mx -all”.

A DKIM key is published (selector “selector1”, “selector2” and “k2”), so receivers can verify mail really came from you.

A consent management tool (Cookiebot) loads with the page.