Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nymo.ai

Nymo | Video Analytics Solutions, specializes in Artificial Intelligence and Edge Computing

Page Load Speed

3.2 sec in total

First Response

263 ms

Resources Loaded

2.6 sec

Page Rendered

275 ms

About Website

Welcome to nymo.ai homepage info - get ready to check Nymo best content right away, or after learning these important things about nymo.ai

Nymo provides Video Analytics Solution to generate actionable business intelligence serving Construction, Retail, Manufacturing and Logistics industries.

Visit nymo.ai

Key Findings

We analyzed Nymo.ai page load time and found that the first response time was 263 ms and then it took 2.9 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

nymo.ai performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.205

60/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

nymo.ai

263 ms

nymo.ai

266 ms

www.nymo.ai

347 ms

master.css

132 ms

responsive.css

193 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 64% of them (45 requests) were addressed to the original Nymo.ai, 14% (10 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (956 ms) relates to the external source Designsupply-web.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 787.1 kB (34%)

Content Size

2.3 MB

After Optimization

1.6 MB

In fact, the total size of Nymo.ai main page is 2.3 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. 55% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 38.5 kB

  • Original 46.5 kB
  • After minification 31.1 kB
  • After compression 8.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 15.4 kB, which is 33% 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 38.5 kB or 83% of the original size.

Image Optimization

-38%

Potential reduce by 692.8 kB

  • Original 1.8 MB
  • After minification 1.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, Nymo needs image optimization as it can save up to 692.8 kB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 23.1 kB

  • Original 361.4 kB
  • After minification 361.4 kB
  • After compression 338.3 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.

CSS Optimization

-28%

Potential reduce by 32.7 kB

  • Original 118.1 kB
  • After minification 118.1 kB
  • After compression 85.5 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. Nymo.ai needs all CSS files to be minified and compressed as it can save up to 32.7 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (42%)

Requests Now

53

After Optimization

31

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nymo. 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 JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

nymo.ai accessibility score

80

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 input fields do not have accessible names

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

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

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

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

Open Graph description is not detected on the main page of Nymo. 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: