cic.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and openai.com and others), adding 612 KiB and 595 ms of main-thread time.

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

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

The page has 1,746 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

About 73 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 30 ms faster on a phone.

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

9 KiB could be saved by minifying JavaScript.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 2.0 MB in 147 requests on a phone: images 1.1 MB (42), scripts 614 KiB (33) and fonts 134 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

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

The homepage links to 159 pages on cic.com and 38 external pages.

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.

/blog/cha-bio-group-and-cic-announce-intent-to-establish-a-cell-gene-biobank-based-open-innovation-center-in-south-korea has no meta description, so Google writes the search snippet from whatever text it finds.

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

Chrome logged issues while loading the page (“Content security policy”).

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.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://cic.com/landlords/.

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.

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

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

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

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.

The homepage carries about 852 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, HubSpot and LinkedIn Insight (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.

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

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