Tools & Wizards About Us
oritex.be screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

oritex.be

Page Load Speed

1.4 sec in total

First Response

300 ms

Resources Loaded

971 ms

Page Rendered

176 ms

oritex.be screenshot

About Website

Welcome to oritex.be homepage info - get ready to check Oritex best content right away, or after learning these important things about oritex.be

Visit oritex.be

Key Findings

We analyzed Oritex.be page load time and found that the first response time was 300 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

oritex.be performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.12

84/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

oritex.be

300 ms

style.css

134 ms

acceuil-textile.jpg

668 ms

acceuil-tactic.jpg

607 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that all of those requests were addressed to Oritex.be and no external sources were called. The less responsive or slowest element that took the longest time to load (668 ms) belongs to the original domain Oritex.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 550 B (0%)

Content Size

287.6 kB

After Optimization

287.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Oritex.be main page is 287.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 286.6 kB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 383 B

  • Original 671 B
  • After minification 649 B
  • After compression 288 B

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 383 B or 57% of the original size.

Image Optimization

-0%

Potential reduce by 38 B

  • Original 286.6 kB
  • After minification 286.6 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. Oritex images are well optimized though.

CSS Optimization

-53%

Potential reduce by 129 B

  • Original 245 B
  • After minification 185 B
  • After compression 116 B

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. Oritex.be needs all CSS files to be minified and compressed as it can save up to 129 B or 53% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • Images
  • CSS

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oritex. According to our analytics all requests are already optimized.

Network Requests Diagram

oritex.be

oritex.be

300 ms

style.css

style.css

134 ms

acceuil-textile.jpg

acceuil-textile.jpg

668 ms

acceuil-tactic.jpg

acceuil-tactic.jpg

607 ms

Accessibility Review

oritex.be accessibility score

70

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-*] attributes do not have valid values

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

Best Practices

oritex.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

oritex.be SEO score

92

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oritex.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Oritex.be main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

oritex.be

Open Graph description is not detected on the main page of Oritex. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: