Tools & Wizards About Us
ior.com.au screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

ior.com.au

IOR | Australian-owned and Operated

Page Load Speed

1.9 sec in total

First Response

52 ms

Resources Loaded

1.4 sec

Page Rendered

509 ms

ior.com.au screenshot

About Website

Click here to check amazing IOR content. Otherwise, check out these important facts you probably never knew about ior.com.au

IOR operates a network of diesel stops designed for heavy vehicles and delivers bulk fuel, storage and monitoring solutions throughout Australia.

Visit ior.com.au

Key Findings

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

Performance Metrics

ior.com.au performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value5,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value24.4 s

0/100

10%

Network Requests Diagram

ior.com.au

52 ms

www.ior.com.au

165 ms

css

113 ms

style.min.css

73 ms

frontend.css

89 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 81% of them (79 requests) were addressed to the original Ior.com.au, 9% (9 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (461 ms) belongs to the original domain Ior.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 216.0 kB (11%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ior.com.au 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. Only a small number of websites need less resources to load. Images take 887.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 191.2 kB

  • Original 222.2 kB
  • After minification 191.7 kB
  • After compression 31.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 30.5 kB, 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 191.2 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 1.8 kB

  • Original 887.5 kB
  • After minification 885.8 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. IOR images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 10.6 kB

  • Original 683.2 kB
  • After minification 682.8 kB
  • After compression 672.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 12.4 kB

  • Original 159.3 kB
  • After minification 159.3 kB
  • After compression 146.9 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. Ior.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 63 (74%)

Requests Now

85

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ior.com.au

ior.com.au

52 ms

www.ior.com.au

www.ior.com.au

165 ms

css

css

113 ms

style.min.css

style.min.css

73 ms

frontend.css

frontend.css

89 ms

all.min.css

all.min.css

79 ms

style.css

style.css

53 ms

style.css

style.css

46 ms

style.css

style.css

45 ms

grid.css

grid.css

44 ms

icons.css

icons.css

107 ms

js_composer.min.css

js_composer.min.css

89 ms

animations.css

animations.css

86 ms

grid_responsive.css

grid_responsive.css

73 ms

css

css

102 ms

public.min.css

public.min.css

73 ms

formreset.min.css

formreset.min.css

103 ms

formsmain.min.css

formsmain.min.css

105 ms

readyclass.min.css

readyclass.min.css

97 ms

browsers.min.css

browsers.min.css

103 ms

pum-site-styles.css

pum-site-styles.css

95 ms

wpgmza_data.js

wpgmza_data.js

99 ms

jquery.min.js

jquery.min.js

110 ms

jquery-migrate.min.js

jquery-migrate.min.js

111 ms

libs.min.js

libs.min.js

114 ms

common.js

common.js

112 ms

jquery.json.min.js

jquery.json.min.js

113 ms

gravityforms.min.js

gravityforms.min.js

115 ms

api.js

api.js

101 ms

js

js

375 ms

background-style.css

background-style.css

110 ms

animate.css

animate.css

111 ms

style.css

style.css

373 ms

animate.min.css

animate.min.css

372 ms

frontend.min.js

frontend.min.js

375 ms

script-min.js

script-min.js

377 ms

site.js

site.js

372 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

373 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

375 ms

wp-polyfill.min.js

wp-polyfill.min.js

373 ms

hooks.min.js

hooks.min.js

376 ms

react.min.js

react.min.js

377 ms

react-dom.min.js

react-dom.min.js

377 ms

escape-html.min.js

escape-html.min.js

359 ms

element.min.js

element.min.js

358 ms

i18n.min.js

i18n.min.js

355 ms

runtime.7bf3c869.js

runtime.7bf3c869.js

328 ms

vendors-public.7bf3c869.js

vendors-public.7bf3c869.js

332 ms

public.7bf3c869.js

public.7bf3c869.js

321 ms

dom-ready.min.js

dom-ready.min.js

319 ms

a11y.min.js

a11y.min.js

316 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

301 ms

core.min.js

core.min.js

300 ms

pum-site-scripts.js

pum-site-scripts.js

300 ms

css

css

25 ms

mobile-detect.min.js

mobile-detect.min.js

297 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

294 ms

js_composer_front.min.js

js_composer_front.min.js

294 ms

ultimate_bg.js

ultimate_bg.js

293 ms

jparallax.js

jparallax.js

294 ms

jquery.vhparallax.js

jquery.vhparallax.js

286 ms

jquery.appear.js

jquery.appear.js

284 ms

custom.js

custom.js

284 ms

vc-waypoints.min.js

vc-waypoints.min.js

284 ms

fbevents.js

fbevents.js

208 ms

gtm.js

gtm.js

205 ms

Logo-for-website.png

Logo-for-website.png

196 ms

Petroleum.svg

Petroleum.svg

193 ms

aviation.svg

aviation.svg

185 ms

Rural.svg

Rural.svg

189 ms

Terminals.svg

Terminals.svg

187 ms

Infrastructure-1.svg

Infrastructure-1.svg

63 ms

logo-caltex-only-300x122.png

logo-caltex-only-300x122.png

120 ms

Offer-Images_Back-to-Base.webp

Offer-Images_Back-to-Base.webp

121 ms

Offer-Images_On-Farm-Bulk-Fuel.webp

Offer-Images_On-Farm-Bulk-Fuel.webp

121 ms

Offer-Images_Aviation.webp

Offer-Images_Aviation.webp

118 ms

Offer-Images_Fuel-Tanks.webp

Offer-Images_Fuel-Tanks.webp

116 ms

Proserpine-Airport-Opening-2-02-280x150.jpg

Proserpine-Airport-Opening-2-02-280x150.jpg

119 ms

icon_plus.png

icon_plus.png

461 ms

Bathurst-Now-Open-Thumbnail-JPG-280x150.jpg

Bathurst-Now-Open-Thumbnail-JPG-280x150.jpg

458 ms

DSC00144_resized-280x150.jpg

DSC00144_resized-280x150.jpg

459 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

99 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

441 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

443 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

446 ms

icomoon.svg

icomoon.svg

446 ms

icomoon.woff

icomoon.woff

446 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

446 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

446 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

442 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

445 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

444 ms

recaptcha__en.js

recaptcha__en.js

266 ms

Charlton-HERO-IOR.webp

Charlton-HERO-IOR.webp

114 ms

DJI_0169-scaled-IOR.webp

DJI_0169-scaled-IOR.webp

117 ms

Hero-Image_Oils-and-Lubricants.webp

Hero-Image_Oils-and-Lubricants.webp

116 ms

Offer-Images-Driver-scaled.jpg

Offer-Images-Driver-scaled.jpg

117 ms

Accessibility Review

ior.com.au accessibility score

81

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

ior.com.au 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ior.com.au SEO score

77

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

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

High

Tap targets are not sized appropriately

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 Ior.com.au 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 Ior.com.au 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

ior.com.au

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