Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 36

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 50

    SEO

    Google-friendlier than
    19% of websites

oapil.com

Oman Aluminium Processing Industries SPC (OAPIL) is Oman’s premier manufacturer of Aluminium / Alloy Rods and Overhead Line Conductors.

Page Load Speed

1.7 sec in total

First Response

447 ms

Resources Loaded

1.2 sec

Page Rendered

97 ms

About Website

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

Oman Aluminium Processing Industries SPC (OAPIL) is Oman's leading manufacturer of Aluminium and Alloy Rods, as well as Overhead Line Conductors, serving global power transmission markets since 2010.

Visit oapil.com

Key Findings

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

Performance Metrics

oapil.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

oapil.com

447 ms

bootstrap.css

74 ms

basic.css

34 ms

responsive.css

50 ms

style.css

81 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 85% of them (46 requests) were addressed to the original Oapil.com, 9% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Weloveiconfonts.com. The less responsive or slowest element that took the longest time to load (447 ms) belongs to the original domain Oapil.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 697.6 kB (35%)

Content Size

2.0 MB

After Optimization

1.3 MB

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

HTML Optimization

-79%

Potential reduce by 15.4 kB

  • Original 19.5 kB
  • After minification 16.9 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 2.6 kB, which is 13% 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 15.4 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 142.0 kB

  • Original 1.3 MB
  • After minification 1.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. Obviously, OAPIL needs image optimization as it can save up to 142.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 223.7 kB

  • Original 306.5 kB
  • After minification 263.4 kB
  • After compression 82.8 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 223.7 kB or 73% of the original size.

CSS Optimization

-88%

Potential reduce by 316.5 kB

  • Original 361.0 kB
  • After minification 263.7 kB
  • After compression 44.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. Oapil.com needs all CSS files to be minified and compressed as it can save up to 316.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (43%)

Requests Now

46

After Optimization

26

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

Accessibility Review

oapil.com accessibility score

36

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

[id] attributes on active, focusable elements are not unique

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

oapil.com best practices score

58

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

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

SEO Factors

oapil.com SEO score

50

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Oapil.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 Oapil.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 OAPIL. 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: