Tools & Wizards About Us
orium.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

orium.com

Orium | Composable Commerce Specialists | Orium

Page Load Speed

1.9 sec in total

First Response

98 ms

Resources Loaded

909 ms

Page Rendered

885 ms

orium.com screenshot

About Website

Visit orium.com now to see the best up-to-date Orium content and also check out these interesting facts you probably never knew about orium.com

Orium is the leader in composable commerce, offering strategy, technology, design, and AI services to help brands evolve, scale, and adapt quickly.

Visit orium.com

Key Findings

We analyzed Orium.com page load time and found that the first response time was 98 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

orium.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value5,830 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.925

3/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

orium.com

98 ms

orium.com

182 ms

fb7e4e17c6d1b4ce.css

67 ms

239de20513d5ca96.css

102 ms

8749cf6c7a0998a7.css

110 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 89% of them (47 requests) were addressed to the original Orium.com, 11% (6 requests) were made to Images.ctfassets.net. The less responsive or slowest element that took the longest time to load (629 ms) belongs to the original domain Orium.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 184.7 kB (6%)

Content Size

3.1 MB

After Optimization

2.9 MB

  • HTML
  • Images

In fact, the total size of Orium.com main page is 3.1 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. 30% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 103.8 kB

  • Original 119.9 kB
  • After minification 119.8 kB
  • After compression 16.0 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 103.8 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 80.9 kB

  • Original 3.0 MB
  • After minification 2.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. Orium images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 16 (39%)

Requests Now

41

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

orium.com

orium.com

98 ms

orium.com

orium.com

182 ms

fb7e4e17c6d1b4ce.css

fb7e4e17c6d1b4ce.css

67 ms

239de20513d5ca96.css

239de20513d5ca96.css

102 ms

8749cf6c7a0998a7.css

8749cf6c7a0998a7.css

110 ms

bc548470525abf69.css

bc548470525abf69.css

111 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

169 ms

webpack-c3c3ebf24feb1fdc.js

webpack-c3c3ebf24feb1fdc.js

142 ms

framework-18c8ecbde440b2ac.js

framework-18c8ecbde440b2ac.js

210 ms

main-289541b6d624222f.js

main-289541b6d624222f.js

187 ms

_app-5aeaf0ffa7aa9882.js

_app-5aeaf0ffa7aa9882.js

216 ms

8037-82b8e67ec322cfd0.js

8037-82b8e67ec322cfd0.js

186 ms

8388-feb9a4b6feda3146.js

8388-feb9a4b6feda3146.js

186 ms

9755-1c565599fb4e1250.js

9755-1c565599fb4e1250.js

204 ms

4784-954050b90924fbf1.js

4784-954050b90924fbf1.js

215 ms

7650-e40545689dceb58d.js

7650-e40545689dceb58d.js

215 ms

1361-bab662ba4641b546.js

1361-bab662ba4641b546.js

218 ms

index-eedd04c89a250c87.js

index-eedd04c89a250c87.js

238 ms

_buildManifest.js

_buildManifest.js

243 ms

_ssgManifest.js

_ssgManifest.js

245 ms

commercetools-logo-website.svg

commercetools-logo-website.svg

19 ms

Elastic_Path_RGB_full_color_lockup__4_.png

Elastic_Path_RGB_full_color_lockup__4_.png

24 ms

Partner_Logo_-_BigCommerce.png

Partner_Logo_-_BigCommerce.png

24 ms

Partner_Logo_-_Google_Cloud.png

Partner_Logo_-_Google_Cloud.png

30 ms

partner-fluent-commerce.png

partner-fluent-commerce.png

31 ms

partner-newstore.png

partner-newstore.png

31 ms

orium-logo-white.svg

orium-logo-white.svg

278 ms

menu-dark.svg

menu-dark.svg

279 ms

logo-composable-new.7770e0f3.png

logo-composable-new.7770e0f3.png

284 ms

image

image

255 ms

image

image

255 ms

image

image

255 ms

image

image

256 ms

image

image

258 ms

image

image

282 ms

image

image

283 ms

instagram.svg

instagram.svg

629 ms

medium-logo.png

medium-logo.png

285 ms

facebook.svg

facebook.svg

287 ms

wordmark-dark-2.svg

wordmark-dark-2.svg

286 ms

image

image

313 ms

image

image

317 ms

image

image

319 ms

%2Fimages%2Farticles%2F1-ct-award.png

%2Fimages%2Farticles%2F1-ct-award.png

69 ms

%2Fimages%2Farticles%2F2-rename.png

%2Fimages%2Farticles%2F2-rename.png

70 ms

%2Fimages%2Farticles%2F3-mach-alliance.png

%2Fimages%2Farticles%2F3-mach-alliance.png

95 ms

%2Fimages%2Farticles%2F4-myplanet-x-tercera.png

%2Fimages%2Farticles%2F4-myplanet-x-tercera.png

97 ms

%2Fimages%2Farticles%2F5-shopping.png

%2Fimages%2Farticles%2F5-shopping.png

272 ms

%2Fimages%2Farticles%2F6-platform-solutions.png

%2Fimages%2Farticles%2F6-platform-solutions.png

147 ms

%2Fimages%2Fphoto-partnership.png

%2Fimages%2Fphoto-partnership.png

214 ms

%2Fimages%2Ffooter%2Flogo-nrf.png

%2Fimages%2Ffooter%2Flogo-nrf.png

70 ms

%2Fimages%2Ffooter%2Flogo-rcc.png

%2Fimages%2Ffooter%2Flogo-rcc.png

69 ms

%2Fimages%2Ffooter%2Flogo-mach.png

%2Fimages%2Ffooter%2Flogo-mach.png

99 ms

Accessibility Review

orium.com accessibility score

93

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

High

Page has valid source maps

SEO Factors

orium.com SEO score

93

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orium.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Orium.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

orium.com

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