Tools & Wizards About Us

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

crio.do

Crio.Do: Project-based learning platform for developers

Page Load Speed

5.2 sec in total

First Response

499 ms

Resources Loaded

4.6 sec

Page Rendered

90 ms

About Website

Visit crio.do now to see the best up-to-date Crio content for India and also check out these interesting facts you probably never knew about crio.do

Build professional work-like projects and accelerate your full stack developer or backend developer career with a job-ready project portfolio. Enroll and start for free.

Visit crio.do

Key Findings

We analyzed Crio.do page load time and found that the first response time was 499 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

crio.do performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value5,560 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

Network Requests Diagram

crio.do

499 ms

www.crio.do

423 ms

css2

66 ms

css2

83 ms

css2

93 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 43% of them (22 requests) were addressed to the original Crio.do, 41% (21 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source In.fw-cdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 862.7 kB (49%)

Content Size

1.8 MB

After Optimization

907.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Crio.do main page is 1.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 861.7 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 227.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 861.7 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 10 B

  • Original 5.2 kB
  • After minification 5.2 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. Crio images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 675.4 kB
  • After minification 675.4 kB
  • After compression 674.4 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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

24

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

crio.do accessibility score

95

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

crio.do best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

crio.do SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crio.do can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Crio.do 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 Crio. 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: