Tools & Wizards About Us

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

voyage.audio

Voyage Audio | Higher Order Ambisonics Microphone VR Audio Recording

Page Load Speed

2.5 sec in total

First Response

253 ms

Resources Loaded

2 sec

Page Rendered

267 ms

About Website

Click here to check amazing Voyage content. Otherwise, check out these important facts you probably never knew about voyage.audio

Home to Spatial Mic by Voyage Audio — 2nd Order Ambisonics VR microphone capable of single wire digital connectivity to a computer or mobile device.

Visit voyage.audio

Key Findings

We analyzed Voyage.audio page load time and found that the first response time was 253 ms and then it took 2.2 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

voyage.audio performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value2,630 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.126

83/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

voyage.audio

253 ms

voyage.audio

155 ms

js

163 ms

quicklatex-format.css

49 ms

style.css

207 ms

Our browser made a total of 148 requests to load all elements on the main page. We found that 61% of them (91 requests) were addressed to the original Voyage.audio, 16% (23 requests) were made to C0.wp.com and 12% (18 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (993 ms) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.9 kB (22%)

Content Size

887.2 kB

After Optimization

695.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Voyage.audio main page is 887.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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 463.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 181.9 kB

  • Original 228.5 kB
  • After minification 220.4 kB
  • After compression 46.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. 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 181.9 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 8.0 kB

  • Original 463.7 kB
  • After minification 455.7 kB

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. Voyage images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

  • Original 130.4 kB
  • After minification 130.4 kB
  • After compression 129.3 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 810 B

  • Original 64.6 kB
  • After minification 64.6 kB
  • After compression 63.8 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. Voyage.audio has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 118 (87%)

Requests Now

135

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

voyage.audio accessibility score

68

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

voyage.audio best practices score

83

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

Page has valid source maps

SEO Factors

voyage.audio SEO score

98

Search Engine Optimization Advices

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 Voyage.audio 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 Voyage.audio 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 Voyage. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: