Access oosto.com. Real-time Facial Recognition Technology

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,070 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.092

91/100

15%

TTI (Time to Interactive)

Value57.9 s

0/100

10%

oosto.com

63 ms

oosto.com

367 ms

uc.js

63 ms

js

83 ms

all.min.css

130 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 79% of them (69 requests) were addressed to the original Oosto.com, 10% (9 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Oosto.com.

Content Size

10.5 MB

After Optimization

10.2 MB

In fact, the total size of Oosto.com main page is 10.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 9.9 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 163.1 kB

Original 190.7 kB
After minification 164.1 kB
After compression 27.6 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 26.6 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 163.1 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 1.7 kB

Original 9.9 MB
After minification 9.9 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. Oosto images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 88.0 kB

Original 257.5 kB
After minification 257.5 kB
After compression 169.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 88.0 kB or 34% of the original size.

CSS Optimization

-0%

Potential reduce by 367 B

Original 122.3 kB
After minification 122.3 kB
After compression 122.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. Oosto.com has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

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

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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.

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

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 Oosto.com 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 Oosto.com 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

oosto.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Real-time Facial Recognition Technology | Oosto

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

oosto.com

oosto.com

uc.js

js

all.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

oosto.com

oosto.com

uc.js

js

all.min.css

v4-shims.min.css

cnss.css

style.min.css

css2

child-theme.min.css

shiftnav.min.css

dark-yellow.css

jquery.min.js

jquery-migrate.min.js

cnss.js

frontend-gtag.min.js

child-theme.min.js

frontend.min.css

core.min.js

mouse.min.js

sortable.min.js

addthis_widget.js

imagesloaded.min.js

masonry.min.js

js.cookie.min.js

shiftnav.min.js

brave.js

gtm.js

930473119

930473403

Oosto-Logo-Formerly-AnyVision-1.svg

oosto.com

static-hero.jpg

nvidia-logo.png

macys-logo.png

ford-logo.png

fgf-logo.png

okada-logo.png

santa-fe-logo.png

saints-logo.png

intellicene-logo.png

honeywell-logo.png

lprc-logo.png