Tools & Wizards About Us
inloco.ai screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

inloco.ai

Incognia | Location Identity for Trust and Safety | Digital Trust

Page Load Speed

2.8 sec in total

First Response

158 ms

Resources Loaded

1.6 sec

Page Rendered

1.1 sec

inloco.ai screenshot

About Website

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

Spoof-proof location verification used by trust & safety teams to authenticate customers throughout their digital journey and increase digital trust.

Visit inloco.ai

Key Findings

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

inloco.ai performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value2,610 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

www.incognia.com

158 ms

header-incognia-v2.min.css

181 ms

module_42827447361_header-incognia-v2.min.css

201 ms

main-incognia.css

436 ms

LanguageSwitcher.css

67 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Inloco.ai, 6% (4 requests) were made to No-cache.hubspot.com and 5% (3 requests) were made to 5242234.fs1.hubspotusercontent-na1.net. The less responsive or slowest element that took the longest time to load (865 ms) relates to the external source Incognia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (30%)

Content Size

4.4 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 202.4 kB

  • Original 232.2 kB
  • After minification 212.1 kB
  • After compression 29.9 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 202.4 kB or 87% of the original size.

Image Optimization

-26%

Potential reduce by 1.1 MB

  • Original 4.1 MB
  • After minification 3.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. Obviously, Inloco needs image optimization as it can save up to 1.1 MB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-26%

Potential reduce by 9.3 kB

  • Original 35.7 kB
  • After minification 35.7 kB
  • After compression 26.5 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 9.3 kB or 26% of the original size.

CSS Optimization

-27%

Potential reduce by 8.5 kB

  • Original 31.2 kB
  • After minification 31.2 kB
  • After compression 22.7 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. Inloco.ai needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (65%)

Requests Now

63

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.incognia.com

www.incognia.com

158 ms

header-incognia-v2.min.css

header-incognia-v2.min.css

181 ms

module_42827447361_header-incognia-v2.min.css

module_42827447361_header-incognia-v2.min.css

201 ms

main-incognia.css

main-incognia.css

436 ms

LanguageSwitcher.css

LanguageSwitcher.css

67 ms

module_38534607605_hero-home.min.css

module_38534607605_hero-home.min.css

270 ms

module_29651564740_alert-box.min.css

module_29651564740_alert-box.min.css

198 ms

module_83074896963_benefits-summary.min.css

module_83074896963_benefits-summary.min.css

283 ms

module_85078875916_icon-title-list.min.css

module_85078875916_icon-title-list.min.css

320 ms

module_74615782787_industry-deck.min.css

module_74615782787_industry-deck.min.css

389 ms

module_74042690878_key-differentiators.min.css

module_74042690878_key-differentiators.min.css

338 ms

module_38535969085_results-display.min.css

module_38535969085_results-display.min.css

752 ms

module_47085125973_resources-with-cta.min.css

module_47085125973_resources-with-cta.min.css

318 ms

footer-incognia.min.css

footer-incognia.min.css

485 ms

uc.js

uc.js

103 ms

css2

css2

76 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

75 ms

layout.min.css

layout.min.css

103 ms

current.js

current.js

338 ms

project.js

project.js

357 ms

header-incognia-v2.min.js

header-incognia-v2.min.js

521 ms

module_38534607605_hero-home.min.js

module_38534607605_hero-home.min.js

534 ms

module_29651564740_alert-box.min.js

module_29651564740_alert-box.min.js

539 ms

module_38535969085_results-display.min.js

module_38535969085_results-display.min.js

865 ms

alpine.min.js

alpine.min.js

65 ms

module_47085125973_resources-with-cta.min.js

module_47085125973_resources-with-cta.min.js

646 ms

5242234.js

5242234.js

569 ms

index.js

index.js

548 ms

configuration.js

configuration.js

260 ms

cc.js

cc.js

136 ms

d50afaf3-3a86-46bb-9649-88e3490c24a9.png

d50afaf3-3a86-46bb-9649-88e3490c24a9.png

224 ms

logo-incognia-purple.svg

logo-incognia-purple.svg

61 ms

logo-incognia-symbol.svg

logo-incognia-symbol.svg

70 ms

icon-webinar-v2.svg

icon-webinar-v2.svg

66 ms

icon-ebook.svg

icon-ebook.svg

64 ms

icon-case-study.svg

icon-case-study.svg

68 ms

icon-infographic.svg

icon-infographic.svg

99 ms

icon-shield.svg

icon-shield.svg

95 ms

icon-bolt.svg

icon-bolt.svg

95 ms

icon-check.svg

icon-check.svg

246 ms

icon-food-delivery-purple.svg

icon-food-delivery-purple.svg

242 ms

icon-gaming-purple.svg

icon-gaming-purple.svg

217 ms

icon-social-purple.svg

icon-social-purple.svg

125 ms

icon-financial-purple.svg

icon-financial-purple.svg

242 ms

icon-food-delivery-white.svg

icon-food-delivery-white.svg

122 ms

icon-gaming-white.svg

icon-gaming-white.svg

219 ms

icon-social-white.svg

icon-social-white.svg

217 ms

icon-location.svg

icon-location.svg

239 ms

icon-background-check.svg

icon-background-check.svg

234 ms

icon-profile.svg

icon-profile.svg

236 ms

icon-fraudster.svg

icon-fraudster.svg

270 ms

1ba0330c-0fcc-4a2c-a598-52789d583878.png

1ba0330c-0fcc-4a2c-a598-52789d583878.png

241 ms

world_1.svg

world_1.svg

213 ms

arrow-white.png

arrow-white.png

296 ms

arrow-black.png

arrow-black.png

296 ms

incognia-home-03.jpg

incognia-home-03.jpg

302 ms

icon-check-black.svg

icon-check-black.svg

146 ms

case-gaming-app.png

case-gaming-app.png

150 ms

case-social-media-app.png

case-social-media-app.png

273 ms

case-willbank.png

case-willbank.png

362 ms

bc-v4.min.html

bc-v4.min.html

126 ms

,

,

100 ms

d50afaf3-3a86-46bb-9649-88e3490c24a9.png

d50afaf3-3a86-46bb-9649-88e3490c24a9.png

41 ms

1ba0330c-0fcc-4a2c-a598-52789d583878.png

1ba0330c-0fcc-4a2c-a598-52789d583878.png

57 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

5 ms

Accessibility Review

inloco.ai accessibility score

77

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

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

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

inloco.ai SEO score

79

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

High

robots.txt is not valid

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

inloco.ai

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