Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

odeum.io

Odeum - Launch your own video subscription service, completely free.

Page Load Speed

7.4 sec in total

First Response

992 ms

Resources Loaded

4.2 sec

Page Rendered

2.3 sec

odeum.io screenshot

About Website

Welcome to odeum.io homepage info - get ready to check Odeum best content for United States right away, or after learning these important things about odeum.io

Announcing the first of its kind: A completely branded subscription video service with apps on every major platform at absolutely zero up-front cost.

Visit odeum.io

Key Findings

We analyzed Odeum.io page load time and found that the first response time was 992 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

odeum.io performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value24.8 s

0/100

10%

TBT (Total Blocking Time)

Value5,430 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value52.6 s

0/100

10%

Network Requests Diagram

odeum.io

992 ms

style.min.css

161 ms

theme.min.css

167 ms

header-footer.min.css

141 ms

elementor-icons.min.css

145 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 84% of them (104 requests) were addressed to the original Odeum.io, 4% (5 requests) were made to Player.vimeo.com and 3% (4 requests) were made to I.vimeocdn.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Odeum.io.

Page Optimization Overview & Recommendations

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

Content Size

12.9 MB

After Optimization

11.6 MB

In fact, the total size of Odeum.io main page is 12.9 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 12.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 196.6 kB

  • Original 228.5 kB
  • After minification 228.4 kB
  • After compression 31.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 196.6 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 1.1 MB

  • Original 12.2 MB
  • After minification 11.2 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. Odeum images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 870 B

  • Original 221.4 kB
  • After minification 221.4 kB
  • After compression 220.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.

CSS Optimization

-0%

Potential reduce by 284 B

  • Original 205.3 kB
  • After minification 205.3 kB
  • After compression 205.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. Odeum.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 72 (64%)

Requests Now

113

After Optimization

41

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

Accessibility Review

odeum.io accessibility score

87

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

odeum.io 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

odeum.io SEO score

89

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

Image elements do not have [alt] attributes

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