Tools & Wizards About Us
neoma.ai screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

neoma.ai

Neoma | AI Integration for Automated Workflows and Human-Centric Experiences

Page Load Speed

2.6 sec in total

First Response

92 ms

Resources Loaded

1.5 sec

Page Rendered

1 sec

neoma.ai screenshot

About Website

Click here to check amazing Neoma content. Otherwise, check out these important facts you probably never knew about neoma.ai

Neoma integrates systems, spaces & people to power automated workflows. Expertise in hospitality, connected devices, cybersecurity & data management. Delivering human-centric experiences.

Visit neoma.ai

Key Findings

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

Performance Metrics

neoma.ai performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value24.7 s

0/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value2,910 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.318

36/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

Network Requests Diagram

neoma.ai

92 ms

neoma.ai

24 ms

all.min.css

9 ms

swiper-bundle.min.css

11 ms

aos.css

27 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 80% of them (67 requests) were addressed to the original Neoma.ai, 4% (3 requests) were made to Placehold.co and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Neoma.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (20%)

Content Size

6.1 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Neoma.ai main page is 6.1 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 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 122.1 kB

  • Original 144.1 kB
  • After minification 123.8 kB
  • After compression 22.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 20.3 kB, which is 14% 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 122.1 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 587.7 kB

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

JavaScript Optimization

-65%

Potential reduce by 281.1 kB

  • Original 431.9 kB
  • After minification 431.9 kB
  • After compression 150.8 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 281.1 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 221.2 kB

  • Original 267.2 kB
  • After minification 260.3 kB
  • After compression 46.0 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. Neoma.ai needs all CSS files to be minified and compressed as it can save up to 221.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (37%)

Requests Now

78

After Optimization

49

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

neoma.ai

neoma.ai

92 ms

neoma.ai

neoma.ai

24 ms

all.min.css

all.min.css

9 ms

swiper-bundle.min.css

swiper-bundle.min.css

11 ms

aos.css

aos.css

27 ms

cookieconsent.css

cookieconsent.css

28 ms

main.css

main.css

40 ms

warmly.js

warmly.js

197 ms

weglot.min.js

weglot.min.js

152 ms

popper.min.js

popper.min.js

23 ms

headroom.min.js

headroom.min.js

23 ms

flowbite.min.js

flowbite.min.js

97 ms

on-screen.umd.min.js

on-screen.umd.min.js

89 ms

jarallax.min.js

jarallax.min.js

90 ms

anime.min.js

anime.min.js

89 ms

swiper-bundle.min.js

swiper-bundle.min.js

97 ms

cookieconsent.js

cookieconsent.js

97 ms

aos.js

aos.js

99 ms

lunr.min.js

lunr.min.js

100 ms

js

js

308 ms

js

js

389 ms

20218834.js

20218834.js

299 ms

v2.js

v2.js

147 ms

ebook.js

ebook.js

98 ms

popup-modal.js

popup-modal.js

101 ms

main.js

main.js

100 ms

reb2b.js.gz

reb2b.js.gz

416 ms

white

white

246 ms

article-cover.jpg

article-cover.jpg

22 ms

article-cover.png

article-cover.png

37 ms

article-cover.png

article-cover.png

25 ms

article-cover.jpg

article-cover.jpg

1175 ms

article-cover.png

article-cover.png

30 ms

peninsula-hotel.png

peninsula-hotel.png

22 ms

tec.png

tec.png

24 ms

wheelock-properties.png

wheelock-properties.png

26 ms

hongkong-land.png

hongkong-land.png

27 ms

regent.png

regent.png

27 ms

swire.png

swire.png

31 ms

pure-fitness.png

pure-fitness.png

30 ms

hellenic-republic.png

hellenic-republic.png

31 ms

grand-hyatt.png

grand-hyatt.png

31 ms

kpmg.png

kpmg.png

32 ms

capgemini.png

capgemini.png

32 ms

shkp.png

shkp.png

32 ms

fifa.png

fifa.png

32 ms

ki-space.png

ki-space.png

33 ms

rics.png

rics.png

33 ms

onthelist.svg

onthelist.svg

39 ms

liga-pro.png

liga-pro.png

37 ms

eagle-cement.png

eagle-cement.png

37 ms

jcd.png

jcd.png

36 ms

600x400

600x400

223 ms

200x300

200x300

250 ms

pmq.png

pmq.png

35 ms

fifa-representative.jpg

fifa-representative.jpg

58 ms

mathew-james-lawson.png

mathew-james-lawson.png

58 ms

chelsea-perino.png

chelsea-perino.png

60 ms

kathryn-yeung.png

kathryn-yeung.png

50 ms

mike-economakis.png

mike-economakis.png

50 ms

maximise-roi-operations.png

maximise-roi-operations.png

74 ms

Stadium_Bubbles-09.png

Stadium_Bubbles-09.png

49 ms

Stadium_Bubbles-02.png

Stadium_Bubbles-02.png

50 ms

Stadium_Bubbles-03.png

Stadium_Bubbles-03.png

69 ms

Stadium_Bubbles-04.png

Stadium_Bubbles-04.png

68 ms

Stadium_Bubbles-05.png

Stadium_Bubbles-05.png

68 ms

Stadium_Bubbles-06.png

Stadium_Bubbles-06.png

66 ms

Stadium_Bubbles-08.png

Stadium_Bubbles-08.png

90 ms

Stadium_Bubbles-07.png

Stadium_Bubbles-07.png

190 ms

ebook-personalisation-with-privacy.png

ebook-personalisation-with-privacy.png

191 ms

social-linkedin.png

social-linkedin.png

87 ms

new-twitter.png

new-twitter.png

86 ms

social-youtube.webp

social-youtube.webp

189 ms

privacy-first.png

privacy-first.png

187 ms

TTNorms-Regular.otf

TTNorms-Regular.otf

35 ms

TTNorms-Medium.otf

TTNorms-Medium.otf

35 ms

TTNorms-Bold.otf

TTNorms-Bold.otf

33 ms

collectedforms.js

collectedforms.js

161 ms

leadflows.js

leadflows.js

108 ms

banner.js

banner.js

140 ms

20218834.js

20218834.js

186 ms

fb.js

fb.js

101 ms

web-interactives-embed.js

web-interactives-embed.js

131 ms

conversations-embed.js

conversations-embed.js

100 ms

Accessibility Review

neoma.ai accessibility score

97

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

neoma.ai best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

neoma.ai SEO score

90

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

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

    EN

  • Encoding

    UTF-8

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

neoma.ai

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