Tools & Wizards About Us
interos.ai screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

interos.ai

Supply Chain Resilience & Risk Management Software - Interos

Page Load Speed

2.5 sec in total

First Response

219 ms

Resources Loaded

1.2 sec

Page Rendered

1.1 sec

interos.ai screenshot

About Website

Click here to check amazing Interos content for United States. Otherwise, check out these important facts you probably never knew about interos.ai

AI powered supply chain risk management. The Interos Platform discovers, visualizes and assesses your supply chain.

Visit interos.ai

Key Findings

We analyzed Interos.ai page load time and found that the first response time was 219 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

interos.ai performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value4,310 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.256

48/100

15%

TTI (Time to Interactive)

Value24.9 s

0/100

10%

Network Requests Diagram

interos.ai

219 ms

www.interos.ai

193 ms

gtm.js

342 ms

v2.js

72 ms

style.min.css

35 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 81% of them (48 requests) were addressed to the original Interos.ai, 5% (3 requests) were made to Static.addtoany.com and 5% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (342 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.0 kB (10%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-79%

Potential reduce by 110.1 kB

  • Original 139.2 kB
  • After minification 139.1 kB
  • After compression 29.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 110.1 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 9.9 kB

  • Original 1.0 MB
  • After minification 1.0 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. Interos images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 105 B

  • Original 41.7 kB
  • After minification 41.7 kB
  • After compression 41.6 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.

Requests Breakdown

Number of requests can be reduced by 25 (48%)

Requests Now

52

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

interos.ai

interos.ai

219 ms

www.interos.ai

www.interos.ai

193 ms

gtm.js

gtm.js

342 ms

v2.js

v2.js

72 ms

style.min.css

style.min.css

35 ms

style.build.css

style.build.css

36 ms

style.css

style.css

42 ms

dashicons.min.css

dashicons.min.css

44 ms

style.css

style.css

44 ms

styles.css

styles.css

56 ms

addtoany.min.css

addtoany.min.css

46 ms

page.js

page.js

66 ms

jquery.min.js

jquery.min.js

47 ms

jquery-migrate.min.js

jquery-migrate.min.js

64 ms

addtoany.min.js

addtoany.min.js

59 ms

style.basic-ho-is-po-no-da-au-co-au-se-is.css

style.basic-ho-is-po-no-da-au-co-au-se-is.css

57 ms

navigation.js

navigation.js

53 ms

vendors.min.js

vendors.min.js

60 ms

main.min.js

main.min.js

62 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

319 ms

custom.js

custom.js

312 ms

hoverIntent.min.js

hoverIntent.min.js

320 ms

maxmegamenu.js

maxmegamenu.js

323 ms

OtAutoBlock.js

OtAutoBlock.js

61 ms

otSDKStub.js

otSDKStub.js

322 ms

5812029.js

5812029.js

322 ms

asp-c91bfc2d.js

asp-c91bfc2d.js

331 ms

interos-logo.svg

interos-logo.svg

86 ms

interos-logo-alt.svg

interos-logo-alt.svg

86 ms

search-icon-header.svg

search-icon-header.svg

88 ms

close-button-icon.svg

close-button-icon.svg

90 ms

icon-revenue.svg

icon-revenue.svg

88 ms

icon-visibility.svg

icon-visibility.svg

84 ms

icon-tool.svg

icon-tool.svg

91 ms

dot-pattern-dark-big.svg

dot-pattern-dark-big.svg

94 ms

global-image.png

global-image.png

311 ms

nasa-logo-150.png

nasa-logo-150.png

91 ms

050323-website-testimonial-slider-NASA2.png

050323-website-testimonial-slider-NASA2.png

116 ms

play-logo.svg

play-logo.svg

92 ms

L3Harris_Technologies_logo.svg

L3Harris_Technologies_logo.svg

120 ms

L3Harris-thumbnail-website-600.png

L3Harris-thumbnail-website-600.png

123 ms

Freddie_logo.svg

Freddie_logo.svg

124 ms

Freddie-mac-thumbnail-web-600.png

Freddie-mac-thumbnail-web-600.png

125 ms

accenture-logo.svg

accenture-logo.svg

122 ms

Accenture-thumbnail-web-600.png

Accenture-thumbnail-web-600.png

141 ms

dot-pattern-dark-medium.svg

dot-pattern-dark-medium.svg

127 ms

dot-pattern-light.svg

dot-pattern-light.svg

142 ms

solution-resilience-light.svg

solution-resilience-light.svg

189 ms

solution-compliance-light.svg

solution-compliance-light.svg

188 ms

solution-sourcing-light.svg

solution-sourcing-light.svg

190 ms

interos-footer-logo.svg

interos-footer-logo.svg

192 ms

sm.25.html

sm.25.html

124 ms

eso.Ep5bSEmr.js

eso.Ep5bSEmr.js

115 ms

NHaasGroteskDSPro-55Rg.woff

NHaasGroteskDSPro-55Rg.woff

325 ms

NHaasGroteskDSPro-65Md.woff

NHaasGroteskDSPro-65Md.woff

339 ms

interos.ttf

interos.ttf

190 ms

wARDj0u

wARDj0u

18 ms

fa01e10a-8f5a-42af-9380-63b0123bf529.json

fa01e10a-8f5a-42af-9380-63b0123bf529.json

100 ms

location

location

182 ms

Accessibility Review

interos.ai accessibility score

78

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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.

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

High

Page has valid source maps

SEO Factors

interos.ai SEO score

84

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

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

interos.ai

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