Tools & Wizards About Us
oo.sg screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

oo.sg

OO.sg - Compare Book Prices, Buy Books Online from Singapore Bookstores

Page Load Speed

5.7 sec in total

First Response

1.2 sec

Resources Loaded

4.3 sec

Page Rendered

231 ms

oo.sg screenshot

About Website

Click here to check amazing OO content for Singapore. Otherwise, check out these important facts you probably never knew about oo.sg

Compare book prices and promotions from major Singapore and international online bookstores including Amazon, Kinokuniya and The Book Depository. Buy books for the best prices all from one page.

Visit oo.sg

Key Findings

We analyzed Oo.sg page load time and found that the first response time was 1.2 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

oo.sg performance score

0

Network Requests Diagram

oo.sg

1203 ms

bootstrap.css

510 ms

skin.css

491 ms

style.css

762 ms

tgn0.0.1.css

495 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 80% of them (43 requests) were addressed to the original Oo.sg, 6% (3 requests) were made to S7.addthis.com and 4% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Oo.sg.

Page Optimization Overview & Recommendations

Page size can be reduced by 741.1 kB (59%)

Content Size

1.3 MB

After Optimization

521.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oo.sg 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. 40% of websites need less resources to load. Javascripts take 691.8 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 46.6 kB

  • Original 66.1 kB
  • After minification 63.2 kB
  • After compression 19.5 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.6 kB or 71% of the original size.

Image Optimization

-11%

Potential reduce by 27.7 kB

  • Original 261.6 kB
  • After minification 233.9 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. Obviously, OO needs image optimization as it can save up to 27.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 461.7 kB

  • Original 691.8 kB
  • After minification 645.9 kB
  • After compression 230.1 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 461.7 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 205.0 kB

  • Original 242.9 kB
  • After minification 200.8 kB
  • After compression 37.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. Oo.sg needs all CSS files to be minified and compressed as it can save up to 205.0 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

52

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oo.sg

oo.sg

1203 ms

bootstrap.css

bootstrap.css

510 ms

skin.css

skin.css

491 ms

style.css

style.css

762 ms

tgn0.0.1.css

tgn0.0.1.css

495 ms

BackToTop.jquery.css

BackToTop.jquery.css

518 ms

jquery.js

jquery.js

797 ms

jquery-ui.js

jquery-ui.js

737 ms

jquery.validate.js

jquery.validate.js

739 ms

bootstrap.js

bootstrap.js

774 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

774 ms

script.js

script.js

981 ms

common.js

common.js

987 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

1006 ms

nivo-slider.css

nivo-slider.css

1008 ms

default.css

default.css

1020 ms

addthis_widget.js

addthis_widget.js

18 ms

BackToTop.jquery.js

BackToTop.jquery.js

1118 ms

atrk.js

atrk.js

24 ms

css

css

25 ms

dc.js

dc.js

31 ms

inpage_linkid.js

inpage_linkid.js

7 ms

__utm.gif

__utm.gif

20 ms

header_bg.gif

header_bg.gif

252 ms

logo_shadow.png

logo_shadow.png

261 ms

logo_main.png

logo_main.png

250 ms

searchBarSprite.png

searchBarSprite.png

251 ms

middle%20banner.png

middle%20banner.png

1217 ms

thumb.php

thumb.php

422 ms

thumb.php

thumb.php

1150 ms

thumb.php

thumb.php

1050 ms

thumb.php

thumb.php

1036 ms

thumb.php

thumb.php

1051 ms

thumb.php

thumb.php

1217 ms

thumb.php

thumb.php

1571 ms

thumb.php

thumb.php

1566 ms

thumb.php

thumb.php

1584 ms

thumb.php

thumb.php

1604 ms

loading.gif

loading.gif

1459 ms

tw.png

tw.png

1470 ms

fb.png

fb.png

1699 ms

top_image1.png

top_image1.png

1724 ms

page_shadow.png

page_shadow.png

1805 ms

bottom_shadow.png

bottom_shadow.png

1810 ms

desktop_mobile_sprite.png

desktop_mobile_sprite.png

1818 ms

bottom_footer1.png

bottom_footer1.png

1828 ms

atrk.gif

atrk.gif

57 ms

300lo.json

300lo.json

54 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

67 ms

ie67-css.d5089428ac7f05efd372.js

ie67-css.d5089428ac7f05efd372.js

18 ms

test.png

test.png

211 ms

arrow-prev.png

arrow-prev.png

1804 ms

arrow-next.png

arrow-next.png

1840 ms

back_top.gif

back_top.gif

1910 ms

SEO Factors

oo.sg SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oo.sg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Oo.sg 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

oo.sg

Open Graph description is not detected on the main page of OO. 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: