Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

cloudify.co

Cloudify Documentation Center | Cloudify Documentation Center

Page Load Speed

3.3 sec in total

First Response

232 ms

Resources Loaded

3 sec

Page Rendered

91 ms

cloudify.co screenshot

About Website

Visit cloudify.co now to see the best up-to-date Cloudify content for United States and also check out these interesting facts you probably never knew about cloudify.co

Where the Cloudify documentation LIVES!

Visit cloudify.co

Key Findings

We analyzed Cloudify.co page load time and found that the first response time was 232 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

cloudify.co performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

16/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value10,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value32.0 s

0/100

10%

Network Requests Diagram

cloudify.co

232 ms

cloudify.co

74 ms

docs.cloudify.co

69 ms

font-awesome.min.css

39 ms

nucleus.css

46 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Cloudify.co, 72% (18 requests) were made to Docs.cloudify.co and 8% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Docs.cloudify.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 312.6 kB (77%)

Content Size

404.0 kB

After Optimization

91.5 kB

In fact, the total size of Cloudify.co main page is 404.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 140.8 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 126.3 kB

  • Original 137.3 kB
  • After minification 112.9 kB
  • After compression 11.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 24.5 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 126.3 kB or 92% of the original size.

Image Optimization

-20%

Potential reduce by 3.9 kB

  • Original 19.4 kB
  • After minification 15.5 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Cloudify needs image optimization as it can save up to 3.9 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 95.4 kB

  • Original 140.8 kB
  • After minification 131.4 kB
  • After compression 45.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 95.4 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 87.0 kB

  • Original 106.4 kB
  • After minification 92.9 kB
  • After compression 19.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Cloudify.co needs all CSS files to be minified and compressed as it can save up to 87.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (67%)

Requests Now

21

After Optimization

7

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cloudify. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

cloudify.co accessibility score

67

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

cloudify.co best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

cloudify.co SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cloudify.co can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cloudify.co main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Cloudify. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: