Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

o2o.com

O2O Events Convert Your Event To a Digital Marketing and Lead Generation Platform %

Page Load Speed

9.4 sec in total

First Response

82 ms

Resources Loaded

8.3 sec

Page Rendered

1.1 sec

About Website

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

Event industries leading online to offline marketing platform creates perfect engagement between exhibitors and visitors increasing event revenue at the same time offering high ROI to exhibitors

Visit o2o.com

Key Findings

We analyzed O2o.com page load time and found that the first response time was 82 ms and then it took 9.4 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.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value17.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.2 s

0/100

25%

SI (Speed Index)

Value26.8 s

0/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value35.6 s

0/100

10%

Network Requests Diagram

o2o.com

82 ms

www.o2oevents.com

1420 ms

jquery.selectBox.css

202 ms

font-awesome.css

401 ms

prettyPhoto.css

595 ms

Our browser made a total of 140 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original O2o.com, 87% (122 requests) were made to O2oevents.com and 11% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source O2oevents.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (36%)

Content Size

6.0 MB

After Optimization

3.8 MB

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

HTML Optimization

-88%

Potential reduce by 212.9 kB

  • Original 243.3 kB
  • After minification 238.3 kB
  • After compression 30.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 212.9 kB or 88% of the original size.

Image Optimization

-3%

Potential reduce by 115.6 kB

  • Original 3.5 MB
  • After minification 3.3 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. O2O images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 524.6 kB

  • Original 761.5 kB
  • After minification 758.5 kB
  • After compression 236.9 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 524.6 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 1.3 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 193.3 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.com needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 76 (68%)

Requests Now

112

After Optimization

36

The browser has sent 112 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 44 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

o2o.com accessibility score

86

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

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

o2o.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

o2o.com SEO score

79

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

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.com 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.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 O2O. 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: