Tools & Wizards About Us

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

nexxo.io

Blockchain Powered Financial Services Platform| Nexxo

Page Load Speed

8.8 sec in total

First Response

205 ms

Resources Loaded

5.9 sec

Page Rendered

2.7 sec

About Website

Click here to check amazing Nexxo content for Indonesia. Otherwise, check out these important facts you probably never knew about nexxo.io

Nexxo is the first blockchain-powered financial services platform for micro and small businesses. Nexxo offers small business owners a wide range of banking services such as payroll, POS machines, pre...

Visit nexxo.io

Key Findings

We analyzed Nexxo.io page load time and found that the first response time was 205 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

nexxo.io performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value14,070 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value28.1 s

0/100

10%

Network Requests Diagram

nexxo.io

205 ms

nexxo.io

442 ms

js

193 ms

bootstrap.min.css

380 ms

jquery.min.js

461 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 54% of them (43 requests) were addressed to the original Nexxo.io, 13% (10 requests) were made to Youtube.com and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Nexxo.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (19%)

Content Size

11.6 MB

After Optimization

9.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nexxo.io main page is 11.6 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. Only a small number of websites need less resources to load. Images take 10.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 93.1 kB

  • Original 116.4 kB
  • After minification 92.7 kB
  • After compression 23.3 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 23.7 kB, which is 20% 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 93.1 kB or 80% of the original size.

Image Optimization

-15%

Potential reduce by 1.6 MB

  • Original 10.8 MB
  • After minification 9.1 MB

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, Nexxo needs image optimization as it can save up to 1.6 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-48%

Potential reduce by 162.2 kB

  • Original 338.6 kB
  • After minification 338.6 kB
  • After compression 176.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 162.2 kB or 48% of the original size.

CSS Optimization

-85%

Potential reduce by 312.1 kB

  • Original 369.3 kB
  • After minification 369.1 kB
  • After compression 57.2 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. Nexxo.io needs all CSS files to be minified and compressed as it can save up to 312.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (26%)

Requests Now

72

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

nexxo.io accessibility score

68

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

nexxo.io best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

nexxo.io SEO score

67

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

High

Image elements do not have [alt] attributes

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

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 Nexxo.io 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 Nexxo.io 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 Nexxo. 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: