9.8 sec in total
1.4 sec
5.9 sec
2.5 sec
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.myWe analyzed Aom.my page load time and found that the first response time was 1.4 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
aom.my performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value19.0 s
0/100
25%
Value16.2 s
0/100
10%
Value450 ms
63/100
30%
Value0.416
23/100
15%
Value14.2 s
9/100
10%
1364 ms
295 ms
403 ms
511 ms
541 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 87% of them (59 requests) were addressed to the original Aom.my, 6% (4 requests) were made to Google-analytics.com and 3% (2 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Aom.my.
Page size can be reduced by 221.2 kB (5%)
4.7 MB
4.5 MB
In fact, the total size of Aom.my main page is 4.7 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. 65% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 46.4 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.4 kB or 77% of the original size.
Potential reduce by 120.3 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. Aom images are well optimized though.
Potential reduce by 52.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 52.2 kB or 23% of the original size.
Potential reduce by 2.4 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.
Number of requests can be reduced by 26 (41%)
63
37
The browser has sent 63 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.
aom.my
1364 ms
gtm.js
295 ms
wp-emoji-release.min.js
403 ms
2h6hz.css
511 ms
cax2g.css
541 ms
cax2g.css
563 ms
cax2g.css
763 ms
bxeef.js
760 ms
2h6hz.js
1060 ms
cbay9.css
748 ms
scripts.js
749 ms
lazy-load.min.js
915 ms
jquery.blockUI.min.js
946 ms
add-to-cart.min.js
946 ms
js.cookie.min.js
964 ms
woocommerce.min.js
966 ms
cart-fragments.min.js
988 ms
skip-link-focus-fix.js
1263 ms
bootstrap.min.js
1263 ms
skrollr.min.js
1263 ms
core.js
1264 ms
js
52 ms
ubermenu.min.js
1264 ms
wp-embed.min.js
1329 ms
jquery.sliderPro.js
1766 ms
conversion_async.js
50 ms
analytics.js
31 ms
collect
51 ms
collect
89 ms
aom_logo.png
328 ms
blank.gif
306 ms
capitaland-01.png
304 ms
dhl-01.png
382 ms
farest-01.png
614 ms
ifly-01.png
665 ms
isetan-02.png
664 ms
ISS-02.png
664 ms
lambo-01.png
1272 ms
mbs-01.png
1242 ms
mediacorp-02.png
1268 ms
microsoft-02.png
1269 ms
ntuc-01.png
1270 ms
ocbc-01.png
1270 ms
pepper-lunch-01.png
1270 ms
shimizu-02.png
1263 ms
singhealth-03.png
1256 ms
SLA-01.png
1252 ms
southbeach-01.png
1252 ms
tunglok-01.png
1283 ms
divider.png
1138 ms
icon-air.png
1137 ms
icon-odor.png
1136 ms
icon-mold.png
1148 ms
icon-scent.png
1148 ms
icon-vent.png
1150 ms
filler1.jpg
2487 ms
pattern3.jpg
1244 ms
fontawesome-webfont.woff
1718 ms
fontawesome-webfont.woff
1312 ms
gen_204
114 ms
analytics.js
580 ms
collect
627 ms
aom.my
950 ms
openhand.cur
270 ms
TRIAL-BENNER-MY.png
1495 ms
TRIAL-BANNER-5.png
1548 ms
TRIAL-BANNER-10.png
1878 ms
cax2g.css
243 ms
aom.my accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
aom.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
aom.my SEO score
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
Document uses legible font sizes
EN
EN
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.
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: