cloud4y.com website review

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

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

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

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

8 third-party services load with your homepage (Jivochat, roistat.com and Yandex Metrica and others), adding 771 KiB and 628 ms of main-thread time.

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

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

Jivochat costs a phone 208 ms of main-thread work and 377 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 KiB could be saved by minifying CSS.

49 KiB could be saved by minifying JavaScript.

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

1 image could be 24 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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

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

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Virtual servers”. Most of its time is resource load delay (2.9 s).

Scripts block taps and scrolling for 268 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.

22 images are downloaded at several times the size a phone draws them, for example citrix.png at 1,700 px wide, shown at 147 px. Resized copies would save about 2.2 MB.

26 images (3.0 MB) 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.

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

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

All page content should be contained by landmarks: 25 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.

7 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Google's crawler is blocked from indexing this page.

Your title is 66 characters, so Google will cut it off around 60: “Cloud Infrastructure and Services for Business in Russia | Cloud4Y”.

Your canonical URL points to cloud4u.ru, not cloud4y.com, so Google may credit that host instead.

Structured data found (Organization) but with 1 problem, for example “Organization: url points at a different host (https://www.cloud4y.ru/)”.

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

The homepage links to 152 pages on cloud4y.com and 9 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

/contacts/feedback has no meta description, so Google writes the search snippet from whatever text it finds.

/contacts/feedback and /career have no <h1> headline, so visitors and search engines get no clear main topic.

/support, /4partners, /contacts/feedback, /blog, /clients and /contacts and 3 others took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://www.cloud4y.com/.

1 link from your homepage to your own site is broken, for example https://www.cloud4y.com/cloud-services/ssl-certificates/ (404).

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.

cloud4y.com is registered until Dec 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 335 words of visible text.

cloud4y.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

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 Yandex Metrica (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 20 cookies (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.