Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

orell.com

Oréll: Global Leader in Language Lab, Campus ERP, LMS & eLibrary

Page Load Speed

1.1 sec in total

First Response

153 ms

Resources Loaded

936 ms

Page Rendered

54 ms

orell.com screenshot

About Website

Welcome to orell.com homepage info - get ready to check Orell best content right away, or after learning these important things about orell.com

Oréll, the global leader in educational software industry provides futuristic learning solutions including Digital Language lab , School/College Management Software, LMS and Digital Library to help le...

Visit orell.com

Key Findings

We analyzed Orell.com page load time and found that the first response time was 153 ms and then it took 990 ms 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

orell.com performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

orell.com

153 ms

orell.com

273 ms

bootstrap.min.css

338 ms

custom.css

491 ms

media.css

338 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 62% of them (8 requests) were addressed to the original Orell.com, 38% (5 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (508 ms) belongs to the original domain Orell.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.5 kB (79%)

Content Size

441.6 kB

After Optimization

92.0 kB

In fact, the total size of Orell.com main page is 441.6 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. 15% of websites need less resources to load. CSS take 244.5 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 1.5 kB

  • Original 2.4 kB
  • After minification 2.0 kB
  • After compression 830 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. This page needs HTML code to be minified as it can gain 323 B, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.5 kB or 65% of the original size.

JavaScript Optimization

-71%

Potential reduce by 138.0 kB

  • Original 194.7 kB
  • After minification 194.7 kB
  • After compression 56.7 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 138.0 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 210.0 kB

  • Original 244.5 kB
  • After minification 217.8 kB
  • After compression 34.5 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. Orell.com needs all CSS files to be minified and compressed as it can save up to 210.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (82%)

Requests Now

11

After Optimization

2

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

Accessibility Review

orell.com accessibility score

66

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

orell.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

orell.com SEO score

83

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

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

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

Open Graph description is not detected on the main page of Orell. 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: