Tools & Wizards About Us
aom.my screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

aom.my

Air | Odor | Scent | Mold | Vent - Air & Odor Management (MY)

Page Load Speed

9 sec in total

First Response

840 ms

Resources Loaded

7.8 sec

Page Rendered

425 ms

aom.my screenshot

About Website

Visit aom.my now to see the best up-to-date Aom content and also check out these interesting facts you probably never knew about aom.my

Air & Odor Management (Singapore), a one stop provider, from consultancy to equipment/product solutions, for all your air and odor problems.

Visit aom.my

Key Findings

We analyzed Aom.my page load time and found that the first response time was 840 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

aom.my performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.6 s

0/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.662

8/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

aom.my

840 ms

gtm.js

71 ms

wp-emoji-release.min.js

280 ms

2h6hz.css

482 ms

cax2g.css

519 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 91% of them (60 requests) were addressed to the original Aom.my, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Aom.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.9 kB (4%)

Content Size

4.8 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aom.my main page is 4.8 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. 55% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 46.1 kB

  • Original 59.8 kB
  • After minification 54.1 kB
  • After compression 13.7 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. 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 46.1 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 120.3 kB

  • Original 4.3 MB
  • After minification 4.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. Aom images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 20.2 kB

  • Original 294.5 kB
  • After minification 294.5 kB
  • After compression 274.3 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

-3%

Potential reduce by 2.4 kB

  • Original 73.8 kB
  • After minification 73.8 kB
  • After compression 71.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. Aom.my has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (42%)

Requests Now

62

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aom.my

aom.my

840 ms

gtm.js

gtm.js

71 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

280 ms

2h6hz.css

2h6hz.css

482 ms

cax2g.css

cax2g.css

519 ms

cax2g.css

cax2g.css

522 ms

cax2g.css

cax2g.css

786 ms

bxeef.js

bxeef.js

1086 ms

2h6hz.js

2h6hz.js

862 ms

cbay9.css

cbay9.css

723 ms

scripts.js

scripts.js

779 ms

lazy-load.min.js

lazy-load.min.js

783 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

964 ms

add-to-cart.min.js

add-to-cart.min.js

1040 ms

js.cookie.min.js

js.cookie.min.js

1047 ms

woocommerce.min.js

woocommerce.min.js

1049 ms

cart-fragments.min.js

cart-fragments.min.js

1132 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

1206 ms

bootstrap.min.js

bootstrap.min.js

1303 ms

skrollr.min.js

skrollr.min.js

1308 ms

core.js

core.js

1312 ms

js

js

68 ms

ubermenu.min.js

ubermenu.min.js

1362 ms

wp-embed.min.js

wp-embed.min.js

1394 ms

jquery.sliderPro.js

jquery.sliderPro.js

1688 ms

conversion_async.js

conversion_async.js

77 ms

aom_logo.png

aom_logo.png

452 ms

blank.gif

blank.gif

458 ms

capitaland-01.png

capitaland-01.png

463 ms

dhl-01.png

dhl-01.png

527 ms

farest-01.png

farest-01.png

563 ms

ifly-01.png

ifly-01.png

712 ms

isetan-02.png

isetan-02.png

969 ms

ISS-02.png

ISS-02.png

725 ms

lambo-01.png

lambo-01.png

799 ms

mbs-01.png

mbs-01.png

821 ms

mediacorp-02.png

mediacorp-02.png

816 ms

microsoft-02.png

microsoft-02.png

971 ms

ntuc-01.png

ntuc-01.png

982 ms

ocbc-01.png

ocbc-01.png

1072 ms

pepper-lunch-01.png

pepper-lunch-01.png

1057 ms

shimizu-02.png

shimizu-02.png

1079 ms

singhealth-03.png

singhealth-03.png

1229 ms

SLA-01.png

SLA-01.png

1229 ms

southbeach-01.png

southbeach-01.png

1244 ms

tunglok-01.png

tunglok-01.png

1296 ms

divider.png

divider.png

1332 ms

icon-air.png

icon-air.png

1336 ms

icon-odor.png

icon-odor.png

1477 ms

icon-mold.png

icon-mold.png

1475 ms

icon-scent.png

icon-scent.png

1494 ms

icon-vent.png

icon-vent.png

1523 ms

filler1.jpg

filler1.jpg

2676 ms

pattern3.jpg

pattern3.jpg

1602 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2235 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1918 ms

analytics.js

analytics.js

94 ms

aom.my

aom.my

2388 ms

openhand.cur

openhand.cur

1101 ms

TRIAL-BENNER-MY.png

TRIAL-BENNER-MY.png

2262 ms

TRIAL-BANNER-5.png

TRIAL-BANNER-5.png

3858 ms

TRIAL-BANNER-10.png

TRIAL-BANNER-10.png

2631 ms

collect

collect

26 ms

js

js

46 ms

cax2g.css

cax2g.css

264 ms

TRIAL-BANNER-11.png

TRIAL-BANNER-11.png

1168 ms

Accessibility Review

aom.my accessibility score

79

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.

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

aom.my best practices score

67

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

aom.my SEO score

100

Search Engine Optimization Advices

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 Aom.my 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 Aom.my 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

aom.my

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