Tools & Wizards About Us

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

codengo.com

CodeNgo - Appstores Self-publishing service for Android Developers

Page Load Speed

3.6 sec in total

First Response

215 ms

Resources Loaded

3 sec

Page Rendered

382 ms

About Website

Visit codengo.com now to see the best up-to-date Code Ngo content for Canada and also check out these interesting facts you probably never knew about codengo.com

Your App, Everywhere Users Shop. Self-Publish to over 30 stores like Amazon, Opera, Samsung & more. Submit to and manage all your updates from one place. Alternate app stores drive 200% more downloads...

Visit codengo.com

Key Findings

We analyzed Codengo.com page load time and found that the first response time was 215 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

codengo.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

www.codengo.com

215 ms

none

361 ms

codengo.com

285 ms

cg-main.css

79 ms

jPicker-1.1.5.css

71 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 25% of them (30 requests) were addressed to the original Codengo.com, 32% (38 requests) were made to D36dtie4qa4iub.cloudfront.net and 7% (8 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (734 ms) relates to the external source Blog.codengo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (66%)

Content Size

2.7 MB

After Optimization

900.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Codengo.com main page is 2.7 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 44.4 kB

  • Original 56.1 kB
  • After minification 49.4 kB
  • After compression 11.8 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 6.7 kB, which is 12% 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 44.4 kB or 79% of the original size.

Image Optimization

-79%

Potential reduce by 1.0 MB

  • Original 1.3 MB
  • After minification 274.9 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, Code Ngo needs image optimization as it can save up to 1.0 MB or 79% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-46%

Potential reduce by 416.6 kB

  • Original 900.4 kB
  • After minification 866.2 kB
  • After compression 483.7 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 416.6 kB or 46% of the original size.

CSS Optimization

-70%

Potential reduce by 303.2 kB

  • Original 433.6 kB
  • After minification 342.9 kB
  • After compression 130.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. Codengo.com needs all CSS files to be minified and compressed as it can save up to 303.2 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (60%)

Requests Now

93

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

codengo.com accessibility score

62

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

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

Image elements do not have [alt] attributes

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

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

codengo.com best practices score

50

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

codengo.com SEO score

82

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Codengo.com 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 Codengo.com 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 data is detected on the main page of Code Ngo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: