Tools & Wizards About Us
nb.ai screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

nb.ai

Advanced Routing & Navigation APIs - NextBillion.ai

Page Load Speed

16.4 sec in total

First Response

531 ms

Resources Loaded

14.3 sec

Page Rendered

1.5 sec

nb.ai screenshot

About Website

Visit nb.ai now to see the best up-to-date Nb content and also check out these interesting facts you probably never knew about nb.ai

Nextbillion.ai provides industry’s most powerful APIs and SDKs to solve routing and optimization problems. Seamlessly integrate our products with your existing infrastructure.

Visit nb.ai

Key Findings

We analyzed Nb.ai page load time and found that the first response time was 531 ms and then it took 15.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

nb.ai performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

48/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value4.3 s

85/100

10%

Network Requests Diagram

nb.ai

531 ms

nextbillion.ai

1647 ms

main.min.css

1013 ms

astra-local-fonts.css

735 ms

menu-animation.min.css

738 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Nb.ai, 99% (82 requests) were made to Nextbillion.ai. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source Nextbillion.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 556.4 kB (66%)

Content Size

837.9 kB

After Optimization

281.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Nb.ai main page is 837.9 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. 40% of websites need less resources to load. HTML takes 629.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 515.0 kB

  • Original 629.9 kB
  • After minification 560.9 kB
  • After compression 115.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 69.0 kB, which is 11% 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 515.0 kB or 82% of the original size.

Image Optimization

-20%

Potential reduce by 41.3 kB

  • Original 207.3 kB
  • After minification 166.0 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, Nb needs image optimization as it can save up to 41.3 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

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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 9 (11%)

Requests Now

81

After Optimization

72

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nb.ai

nb.ai

531 ms

nextbillion.ai

nextbillion.ai

1647 ms

main.min.css

main.min.css

1013 ms

astra-local-fonts.css

astra-local-fonts.css

735 ms

menu-animation.min.css

menu-animation.min.css

738 ms

blocks.style.build.css

blocks.style.build.css

735 ms

style.css

style.css

774 ms

bootstrap.min.css

bootstrap.min.css

1410 ms

slick.min.css

slick.min.css

1418 ms

custom.css

custom.css

1416 ms

addtoany.min.css

addtoany.min.css

1446 ms

product-new.css

product-new.css

1510 ms

email-decode.min.js

email-decode.min.js

531 ms

lazyload.min.js

lazyload.min.js

1073 ms

nb-logo-colored-80x73.png

nb-logo-colored-80x73.png

700 ms

down-arrow.svg

down-arrow.svg

744 ms

3.svg

3.svg

1219 ms

2.svg

2.svg

733 ms

doordash.svg

doordash.svg

744 ms

db.svg

db.svg

990 ms

5.svg

5.svg

2127 ms

xgs.png

xgs.png

992 ms

magna.png

magna.png

1699 ms

xplor.png

xplor.png

1724 ms

geotab.png

geotab.png

1944 ms

8.svg

8.svg

1985 ms

7.svg

7.svg

2588 ms

zepto.png

zepto.png

2701 ms

4.svg

4.svg

2451 ms

meesho.png

meesho.png

2904 ms

mapfusion-zoom.webp

mapfusion-zoom.webp

2908 ms

gradient-cta.png

gradient-cta.png

2968 ms

tick.svg

tick.svg

2878 ms

case-study-1-new.webp

case-study-1-new.webp

3275 ms

case-study-2-new.webp

case-study-2-new.webp

3378 ms

xgs-banner-small.webp

xgs-banner-small.webp

3329 ms

mapfusion-nav-img.webp

mapfusion-nav-img.webp

3738 ms

nb-vs-google-1-new.jpg

nb-vs-google-1-new.jpg

3713 ms

bryan.png

bryan.png

3808 ms

arrow-right.svg

arrow-right.svg

3848 ms

home-ro-banner.webp

home-ro-banner.webp

4348 ms

banner-new-mobile-new.webp

banner-new-mobile-new.webp

4239 ms

mapfusion-logo.webp

mapfusion-logo.webp

4426 ms

pay-per-call-2.webp

pay-per-call-2.webp

4715 ms

pay-per-call-1.webp

pay-per-call-1.webp

4980 ms

pay-per-call-3-2x.webp

pay-per-call-3-2x.webp

4835 ms

james-new-opt-new.webp

james-new-opt-new.webp

4978 ms

james-new-opt.webp

james-new-opt.webp

5299 ms

yantisa-akhadi-new-opt.webp

yantisa-akhadi-new-opt.webp

5143 ms

key-benefits-1-opt.webp

key-benefits-1-opt.webp

5685 ms

key-benefits-1-2-opt.webp

key-benefits-1-2-opt.webp

5491 ms

key-benefits-1-3-opt.webp

key-benefits-1-3-opt.webp

5620 ms

distance-matrix-api-2x.webp

distance-matrix-api-2x.webp

5655 ms

navigation-sdk-2x.webp

navigation-sdk-2x.webp

6031 ms

truckit.svg

truckit.svg

5437 ms

hawx-2.svg

hawx-2.svg

6066 ms

easyhealth-2.svg

easyhealth-2.svg

6152 ms

fieldcorp.svg

fieldcorp.svg

5594 ms

goin.svg

goin.svg

5667 ms

use-cases-1.webp

use-cases-1.webp

5909 ms

use-cases-2.webp

use-cases-2.webp

6162 ms

use-cases-4.webp

use-cases-4.webp

6384 ms

logistics-1.webp

logistics-1.webp

6242 ms

mnx.svg

mnx.svg

5474 ms

high-performer-1.svg

high-performer-1.svg

5395 ms

best-support-2.svg

best-support-2.svg

5657 ms

momentum-leader-3.svg

momentum-leader-3.svg

5614 ms

easiest-to-do-4.svg

easiest-to-do-4.svg

5645 ms

g2-badge-1.svg

g2-badge-1.svg

5582 ms

g2-badge-2.png

g2-badge-2.png

5862 ms

g2-badge-3.png

g2-badge-3.png

5179 ms

g2-badge-4.svg

g2-badge-4.svg

6009 ms

set-up-1-new-opt.webp

set-up-1-new-opt.webp

5373 ms

set-up-2-new-opt.webp

set-up-2-new-opt.webp

5388 ms

step-3-opt.webp

step-3-opt.webp

5619 ms

integration-new.webp

integration-new.webp

5829 ms

logo-white.svg

logo-white.svg

5528 ms

aws.png

aws.png

5502 ms

google-cloud.png

google-cloud.png

5429 ms

azure.png

azure.png

5291 ms

aicpa.png

aicpa.png

5529 ms

gdpr.png

gdpr.png

5619 ms

iso.png

iso.png

5751 ms

Accessibility Review

nb.ai accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Best Practices

nb.ai best practices score

92

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

SEO Factors

nb.ai 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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nb.ai 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 Nb.ai 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

nb.ai

Open Graph data is detected on the main page of Nb. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: