Tools & Wizards About Us

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

oq.om

OQ Official website - global integrated energy company | OQ

Page Load Speed

27.2 sec in total

First Response

1.6 sec

Resources Loaded

24.6 sec

Page Rendered

894 ms

About Website

Welcome to oq.om homepage info - get ready to check OQ best content right away, or after learning these important things about oq.om

OQ is a global integrated energy company, with roots in Oman and operations in 17 countries globally. Visit OQ to learn more.

Visit oq.om

Key Findings

We analyzed Oq.om page load time and found that the first response time was 1.6 sec and then it took 25.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

oq.om performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value23.9 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

oq.com

1640 ms

en

522 ms

gtm.js

147 ms

main.min.css

7475 ms

jquery.min.js

9010 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Oq.om, 20% (8 requests) were made to Cdn.cookielaw.org and 7% (3 requests) were made to Oq.com. The less responsive or slowest element that took the longest time to load (12.4 sec) relates to the external source Assets.oq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 480.2 kB (9%)

Content Size

5.6 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oq.om main page is 5.6 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. 50% of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 220.2 kB

  • Original 252.1 kB
  • After minification 203.6 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. This page needs HTML code to be minified as it can gain 48.5 kB, which is 19% 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 220.2 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 195.3 kB

  • Original 5.0 MB
  • After minification 4.8 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. OQ images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 35.0 kB

  • Original 302.2 kB
  • After minification 302.2 kB
  • After compression 267.2 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 35.0 kB or 12% of the original size.

CSS Optimization

-31%

Potential reduce by 29.7 kB

  • Original 94.9 kB
  • After minification 94.8 kB
  • After compression 65.2 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. Oq.om needs all CSS files to be minified and compressed as it can save up to 29.7 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (30%)

Requests Now

33

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

oq.om accessibility score

76

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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.

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

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

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

oq.om best practices score

92

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

Page has valid source maps

SEO Factors

oq.om SEO score

86

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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