cy5.io website review

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

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

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

About 218 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.

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

Google Tag Manager costs a phone 294 ms of main-thread work and 309 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 2.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

6 third-party services load with your homepage (Google Tag Manager, Clarity and apollo.io and others), adding 348 KiB and 392 ms of main-thread time.

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

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

Polyfills for old browsers add 10 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.

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

2 KiB could be saved by minifying JavaScript.

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Actionable Security Signals, at Cloud Speed”. Most of its time is element render delay (6.1 s).

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

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

18 images have no width and height attributes, so the layout jumps as each one loads.

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

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

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 7.6 MB in 97 requests on a phone: media 6.5 MB (2), scripts 619 KiB (30) and fonts 206 KiB (3). Under 2 MB keeps phones on slow connections fast.

2 images (62 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

There are 2 <h1> headlines (“Arrived.” and “Actionable Security Signals, at Cloud Speed”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://www.cy5.io/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 31 pages on cy5.io and 3 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /platform, whose canonical is /ion-cloud-security-platform. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/platform, /cloud-native-siem-by-cy5, /dspm, /enterprise-security-data-lake-india, /about and /partners and 1 other took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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 426 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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 6 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.