Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

vossle.co

Vossle: No-Code Artificial Intelligence for Immersive WebAR

Page Load Speed

5.7 sec in total

First Response

12 ms

Resources Loaded

1.8 sec

Page Rendered

3.9 sec

vossle.co screenshot

About Website

Click here to check amazing Vossle content. Otherwise, check out these important facts you probably never knew about vossle.co

Vossle is an AI-driven AR platform that helps businesses deploy AI's power to create Web-based Augmented reality experiences.

Visit vossle.co

Key Findings

We analyzed Vossle.co page load time and found that the first response time was 12 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

vossle.co performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value3,040 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.279

43/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

vossle.co

12 ms

vossle.ai

413 ms

a5ff7.css

27 ms

5d9aa.css

23 ms

css

66 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vossle.co, 58% (48 requests) were made to Dsjz0v6ta56lv.cloudfront.net and 19% (16 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (705 ms) relates to the external source Dsjz0v6ta56lv.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (9%)

Content Size

38.4 MB

After Optimization

35.1 MB

In fact, the total size of Vossle.co main page is 38.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. 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 37.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 410.3 kB

  • Original 482.0 kB
  • After minification 481.5 kB
  • After compression 71.7 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 410.3 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 2.9 MB

  • Original 37.4 MB
  • After minification 34.5 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. Vossle images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.8 kB

  • Original 348.0 kB
  • After minification 348.0 kB
  • After compression 340.2 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

-1%

Potential reduce by 1.4 kB

  • Original 174.8 kB
  • After minification 174.8 kB
  • After compression 173.4 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. Vossle.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (43%)

Requests Now

65

After Optimization

37

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

Accessibility Review

vossle.co accessibility score

83

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 IDs are not unique

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

Best Practices

vossle.co best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

vossle.co SEO score

91

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

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 Vossle.co 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 Vossle.co 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 data is detected on the main page of Vossle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: