cdsi.us.com website review

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

8 third-party services load with your homepage (Framer CDN, YouTube and Google Tag Manager and others), adding 3.4 MB and 1.3 s of main-thread time.

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

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

Framer CDN costs a phone 646 ms of main-thread work and 2.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.

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

YouTube costs a phone 521 ms of main-thread work and 993 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.

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

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

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

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

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.

Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.4 MB in 152 requests on a phone: images 1.5 MB (99), scripts 1.4 MB (29) and fonts 311 KiB (10). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example SX6H5DDtXNIU7zV6RMTyvqwrH0.png at 1,200 px wide, shown at 228 px. Resized copies would save about 57 KiB.

3 images further down the page (173 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.97 g of CO₂e: 116.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

Your title is only 28 characters: “Home - Cirrus Data Solutions”. 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.

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

Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 271 pages on cdsi.us.com and 41 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.

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.

/cirrus-data-cloud-private-edition and /cirrus-data-cloud all use the title “Cirrus Data Cloud - Cirrus Data Solutions”. Search engines can't tell which page to show for a search, so each competes with the others.

/cirrus-data-cloud-private-edition and /cirrus-data-cloud use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /cirrus-migrate-on-premises-breakthrough-innovation-for-business-success, whose canonical is /blog/cirrus-migrate-on-premises-breakthrough-innovation-for-business-success. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/cli has no <h1> headline, so visitors and search engines get no clear main topic.

/cirrus-migrate-on-premises-breakthrough-innovation-for-business-success took over 3 s to send its HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

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.

Opening https://cdsi.us.com goes through 2 redirects before the homepage loads.

1 link go through two or more redirects, for example https://www.cirrusdata.com/cirrus-migrate-on-premises-breakthrough-innovation-for-business-success/.

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.

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

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

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.

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

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

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

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

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 1,969 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 and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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