Tools & Wizards About Us
o2o.my screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

o2o.my

Web Design Malaysia | Ecommerce Website | O2O Digital

Page Load Speed

11.2 sec in total

First Response

741 ms

Resources Loaded

10.1 sec

Page Rendered

354 ms

o2o.my screenshot

About Website

Welcome to o2o.my homepage info - get ready to check O2O best content for Malaysia right away, or after learning these important things about o2o.my

O2O Digital Malaysia Web Design Company specialising in brand engaging responsive website, trendy ecommerce website, fast web hosting, SEO, & digital marketing

Visit o2o.my

Key Findings

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

Performance Metrics

o2o.my performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

o2o.my

741 ms

o2o.my

953 ms

www.o2o.my

953 ms

www.o2o.my

2741 ms

9a9e87227a277627eba4b24a5160dc33_0.js

245 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 68% of them (47 requests) were addressed to the original O2o.my, 19% (13 requests) were made to Embed.tawk.to and 4% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain O2o.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 152.8 kB (12%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of O2o.my main page is 1.3 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. 45% of websites need less resources to load. Images take 610.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 103.3 kB

  • Original 126.9 kB
  • After minification 126.9 kB
  • After compression 23.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 103.3 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 20.7 kB

  • Original 610.6 kB
  • After minification 589.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. O2O images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 26.5 kB

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

CSS Optimization

-2%

Potential reduce by 2.4 kB

  • Original 97.0 kB
  • After minification 97.0 kB
  • After compression 94.6 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. O2o.my has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (41%)

Requests Now

59

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

o2o.my

o2o.my

741 ms

o2o.my

o2o.my

953 ms

www.o2o.my

www.o2o.my

953 ms

www.o2o.my

www.o2o.my

2741 ms

9a9e87227a277627eba4b24a5160dc33_0.js

9a9e87227a277627eba4b24a5160dc33_0.js

245 ms

k2.js

k2.js

496 ms

9a9e87227a277627eba4b24a5160dc33_1.js

9a9e87227a277627eba4b24a5160dc33_1.js

1201 ms

jquery.easing.js

jquery.easing.js

700 ms

wow.js

wow.js

741 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

726 ms

quix.js

quix.js

752 ms

slick.min.js

slick.min.js

746 ms

9a9e87227a277627eba4b24a5160dc33_2.js

9a9e87227a277627eba4b24a5160dc33_2.js

1655 ms

gtm.js

gtm.js

57 ms

logo.svg

logo.svg

286 ms

logo-white.svg

logo-white.svg

240 ms

dummy.png

dummy.png

262 ms

home-webdesign-anessa.webp

home-webdesign-anessa.webp

732 ms

anessa-bg.webp

anessa-bg.webp

764 ms

home-ecommerce-cmichael.png

home-ecommerce-cmichael.png

766 ms

home-ecommerce-cmichael-bg.webp

home-ecommerce-cmichael-bg.webp

790 ms

home-creative-img1.png

home-creative-img1.png

557 ms

home-creative-img2.webp

home-creative-img2.webp

804 ms

home-creative-bg.webp

home-creative-bg.webp

1066 ms

home-seo.png

home-seo.png

996 ms

home-seo-bg.webp

home-seo-bg.webp

1068 ms

testimony-callie.png

testimony-callie.png

1012 ms

testimony-mandi-icon.png

testimony-mandi-icon.png

1035 ms

testimony-christyng-logo.png

testimony-christyng-logo.png

1066 ms

testimony-qii-logo.png

testimony-qii-logo.png

1251 ms

testimony-lwe-logo.png

testimony-lwe-logo.png

1273 ms

testimony-peridot-logo.png

testimony-peridot-logo.png

1414 ms

testimony-ezylease-icon.png

testimony-ezylease-icon.png

1429 ms

testimonial-flores-logo.png

testimonial-flores-logo.png

1307 ms

sph-logo-icon.png

sph-logo-icon.png

1329 ms

google-partner-logo.png

google-partner-logo.png

1525 ms

fb-partner.png

fb-partner.png

1536 ms

trustee.png

trustee.png

1574 ms

consumer-choice.png

consumer-choice.png

1608 ms

apaccio.jpg

apaccio.jpg

1691 ms

1cfec68c4cbf1e8144af0c0865c8d59b_0.css

1cfec68c4cbf1e8144af0c0865c8d59b_0.css

1991 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRSW3wRmYJp8I5.woff

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRSW3wRmYJp8I5.woff

16 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRR23wRmYJp8I5zzw.woff

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRR23wRmYJp8I5zzw.woff

45 ms

fa-solid-900.woff

fa-solid-900.woff

45 ms

fa-regular-400.woff

fa-regular-400.woff

64 ms

fa-brands-400.woff

fa-brands-400.woff

69 ms

hotjar-1376380.js

hotjar-1376380.js

185 ms

default

default

248 ms

popup.html

popup.html

1345 ms

tooltip.html

tooltip.html

1362 ms

home-slide-new-banner.png

home-slide-new-banner.png

1541 ms

modules.8da33a8f469c3b5ffcec.js

modules.8da33a8f469c3b5ffcec.js

18 ms

o2o-mobile.png

o2o-mobile.png

1258 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

76 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

75 ms

twk-event-polyfill.js

twk-event-polyfill.js

85 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

73 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

83 ms

twk-main.js

twk-main.js

73 ms

twk-vendor.js

twk-vendor.js

137 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

140 ms

twk-chunk-common.js

twk-chunk-common.js

140 ms

twk-runtime.js

twk-runtime.js

126 ms

twk-app.js

twk-app.js

141 ms

large_left.png

large_left.png

286 ms

large_right.png

large_right.png

283 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1323 ms

widget-settings

widget-settings

163 ms

en.js

en.js

15 ms

Accessibility Review

o2o.my accessibility score

60

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

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Heading elements are not in a sequentially-descending order

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

o2o.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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

o2o.my SEO score

93

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

Image elements do not have [alt] attributes

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 O2o.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 O2o.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

o2o.my

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