Tools & Wizards About Us
oddle.me screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

oddle.me

Oddle | Grow Your Restaurant with Online Orders, CRM & Loyalty Tools

Page Load Speed

11.5 sec in total

First Response

475 ms

Resources Loaded

9.7 sec

Page Rendered

1.3 sec

oddle.me screenshot

About Website

Visit oddle.me now to see the best up-to-date Oddle content for Singapore and also check out these interesting facts you probably never knew about oddle.me

Power your restaurant’s growth with Oddle. From online ordering to CRM and marketing automation — everything you need to grow, all in one place.

Visit oddle.me

Key Findings

We analyzed Oddle.me page load time and found that the first response time was 475 ms and then it took 11 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

oddle.me performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.7 s

0/100

25%

SI (Speed Index)

Value22.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,480 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

oddle.me

475 ms

oddle.me

1767 ms

all.css

426 ms

blocks.style.build.css

640 ms

main.min.css

647 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 96% of them (144 requests) were addressed to the original Oddle.me, 2% (3 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Oddle.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 796.9 kB (3%)

Content Size

22.9 MB

After Optimization

22.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oddle.me main page is 22.9 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 21.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 260.6 kB

  • Original 296.7 kB
  • After minification 280.5 kB
  • After compression 36.1 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 260.6 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 529.6 kB

  • Original 21.6 MB
  • After minification 21.0 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. Oddle images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 3.0 kB

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

CSS Optimization

-3%

Potential reduce by 3.7 kB

  • Original 128.5 kB
  • After minification 128.4 kB
  • After compression 124.8 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. Oddle.me has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 101 (69%)

Requests Now

147

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oddle.me

oddle.me

475 ms

oddle.me

oddle.me

1767 ms

all.css

all.css

426 ms

blocks.style.build.css

blocks.style.build.css

640 ms

main.min.css

main.min.css

647 ms

css

css

37 ms

menu-animation.min.css

menu-animation.min.css

441 ms

style.min.css

style.min.css

455 ms

simple-sitemap.css

simple-sitemap.css

640 ms

amazonpolly-public.css

amazonpolly-public.css

648 ms

different-menus-for-different-page-public.css

different-menus-for-different-page-public.css

648 ms

swiper.min.css

swiper.min.css

655 ms

gs-logo.min.css

gs-logo.min.css

656 ms

awpa-frontend-style.css

awpa-frontend-style.css

676 ms

styles.css

styles.css

850 ms

default.css

default.css

863 ms

slick.min.css

slick.min.css

862 ms

slick-theme.min.css

slick-theme.min.css

871 ms

exad-styles.min.css

exad-styles.min.css

1087 ms

htbbootstrap.css

htbbootstrap.css

897 ms

font-awesome.min.css

font-awesome.min.css

1063 ms

animation.css

animation.css

1077 ms

htmega-keyframes.css

htmega-keyframes.css

1081 ms

elementor-icons.min.css

elementor-icons.min.css

1094 ms

frontend-lite.min.css

frontend-lite.min.css

1120 ms

post-1472.css

post-1472.css

1276 ms

frontend-lite.min.css

frontend-lite.min.css

1291 ms

global.css

global.css

1293 ms

post-6.css

post-6.css

1302 ms

css

css

32 ms

fontawesome.min.css

fontawesome.min.css

1304 ms

solid.min.css

solid.min.css

1340 ms

jquery.min.js

jquery.min.js

1492 ms

jquery-migrate.min.js

jquery-migrate.min.js

1508 ms

amazonpolly-public.js

amazonpolly-public.js

1511 ms

different-menus-for-different-page-public.js

different-menus-for-different-page-public.js

1517 ms

awpa-frontend-scripts.js

awpa-frontend-scripts.js

1519 ms

lodash.min.js

lodash.min.js

1565 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1705 ms

post-4176.css

post-4176.css

1715 ms

scroll-to-top.min.css

scroll-to-top.min.css

1515 ms

animations.min.css

animations.min.css

1311 ms

wp-polyfill.min.js

wp-polyfill.min.js

1307 ms

autop.min.js

autop.min.js

1354 ms

blob.min.js

blob.min.js

1465 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

1301 ms

react.min.js

react.min.js

1299 ms

hooks.min.js

hooks.min.js

1305 ms

deprecated.min.js

deprecated.min.js

1304 ms

dom.min.js

dom.min.js

1359 ms

react-dom.min.js

react-dom.min.js

1468 ms

escape-html.min.js

escape-html.min.js

1303 ms

element.min.js

element.min.js

1300 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

1306 ms

i18n.min.js

i18n.min.js

1306 ms

keycodes.min.js

keycodes.min.js

1336 ms

priority-queue.min.js

priority-queue.min.js

1291 ms

compose.min.js

compose.min.js

1289 ms

redux-routine.min.js

redux-routine.min.js

1296 ms

data.min.js

data.min.js

1291 ms

html-entities.min.js

html-entities.min.js

1297 ms

shortcode.min.js

shortcode.min.js

1332 ms

blocks.min.js

blocks.min.js

1300 ms

dom-ready.min.js

dom-ready.min.js

1292 ms

a11y.min.js

a11y.min.js

1298 ms

moment.min.js

moment.min.js

1299 ms

date.min.js

date.min.js

1529 ms

primitives.min.js

primitives.min.js

1327 ms

rich-text.min.js

rich-text.min.js

1284 ms

warning.min.js

warning.min.js

1287 ms

components.min.js

components.min.js

2168 ms

url.min.js

url.min.js

1301 ms

api-fetch.min.js

api-fetch.min.js

1378 ms

keyboard-shortcuts.min.js

keyboard-shortcuts.min.js

1429 ms

notices.min.js

notices.min.js

1305 ms

style-engine.min.js

style-engine.min.js

1314 ms

token-list.min.js

token-list.min.js

1328 ms

wordcount.min.js

wordcount.min.js

1388 ms

block-editor.min.js

block-editor.min.js

1913 ms

core-data.min.js

core-data.min.js

1440 ms

media-utils.min.js

media-utils.min.js

1330 ms

preferences-persistence.min.js

preferences-persistence.min.js

1336 ms

preferences.min.js

preferences.min.js

1399 ms

reusable-blocks.min.js

reusable-blocks.min.js

1495 ms

server-side-render.min.js

server-side-render.min.js

1510 ms

editor.min.js

editor.min.js

1484 ms

frontend.build.js

frontend.build.js

1649 ms

frontend.min.js

frontend.min.js

1511 ms

jquery.sticky-sidebar.js

jquery.sticky-sidebar.js

1531 ms

swiper.min.js

swiper.min.js

1552 ms

gs-logo.min.js

gs-logo.min.js

1818 ms

exad-scripts.min.js

exad-scripts.min.js

1758 ms

popper.min.js

popper.min.js

1637 ms

htbbootstrap.js

htbbootstrap.js

1623 ms

waypoints.js

waypoints.js

1616 ms

scroll-to-top.min.js

scroll-to-top.min.js

1656 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1808 ms

webpack.runtime.min.js

webpack.runtime.min.js

1746 ms

frontend-modules.min.js

frontend-modules.min.js

1620 ms

frontend.min.js

frontend.min.js

1621 ms

waypoints.min.js

waypoints.min.js

1612 ms

core.min.js

core.min.js

1643 ms

frontend.min.js

frontend.min.js

1736 ms

elements-handlers.min.js

elements-handlers.min.js

1625 ms

gtm.js

gtm.js

236 ms

frame@1x-140x38.png

frame@1x-140x38.png

612 ms

home-kv7@2x-1-768x826.png

home-kv7@2x-1-768x826.png

985 ms

USP-1-1@2x.jpg

USP-1-1@2x.jpg

1638 ms

USP-BG2-1@2x.jpg

USP-BG2-1@2x.jpg

1267 ms

USP-3-1@2x.jpg

USP-3-1@2x.jpg

1391 ms

USP-4-1@2x.jpg

USP-4-1@2x.jpg

1617 ms

W-Hotel.png

W-Hotel.png

761 ms

US-Pizza.png

US-Pizza.png

978 ms

The-Westin-KL.png

The-Westin-KL.png

1195 ms

St-Regis.png

St-Regis.png

1199 ms

Oriental.png

Oriental.png

1411 ms

Mitasu-232x300.png

Mitasu-232x300.png

1424 ms

meridien_new.png

meridien_new.png

1488 ms

Grand-Hyatt-KL.png

Grand-Hyatt-KL.png

1604 ms

TPL.png

TPL.png

1626 ms

TGIF.png

TGIF.png

1639 ms

Sanbanto.png

Sanbanto.png

1709 ms

Mabbub.png

Mabbub.png

1816 ms

Komugi.png

Komugi.png

1830 ms

Fatcat.png

Fatcat.png

1842 ms

berkat-madinah-hijau-300x223.jpg

berkat-madinah-hijau-300x223.jpg

1852 ms

absolute-thai-black-red-300x64.jpg

absolute-thai-black-red-300x64.jpg

1744 ms

font

font

56 ms

font

font

56 ms

font

font

125 ms

Tommy.png

Tommy.png

1814 ms

Tiga-Budak.png

Tiga-Budak.png

1911 ms

Paul.png

Paul.png

1928 ms

Nasi-Lemak-Saleha.png

Nasi-Lemak-Saleha.png

1941 ms

La-Juice.png

La-Juice.png

1918 ms

Kayra.png

Kayra.png

1905 ms

Coco-Steamboat.png

Coco-Steamboat.png

1828 ms

Chateraise.png

Chateraise.png

1915 ms

Customer-Data-3-v4@2x.png

Customer-Data-3-v4@2x.png

3006 ms

OE-Hero7-v2@1x.png

OE-Hero7-v2@1x.png

3033 ms

oe-logo@1x-300x157.png

oe-logo@1x-300x157.png

1956 ms

png-transparent-google-play-4.png

png-transparent-google-play-4.png

1910 ms

png-transparent-google-play-3.png

png-transparent-google-play-3.png

1835 ms

extra-2b@2x.png

extra-2b@2x.png

2060 ms

extra-1c@2x.png

extra-1c@2x.png

2121 ms

prefooter-bg-b@2x-scaled.jpg

prefooter-bg-b@2x-scaled.jpg

1754 ms

home-kv7@2x-1-279x300.png

home-kv7@2x-1-279x300.png

1618 ms

oe-logo@1x.png

oe-logo@1x.png

1748 ms

oe-hero7@2x.png

oe-hero7@2x.png

2336 ms

frame@2x.png

frame@2x.png

1682 ms

Accessibility Review

oddle.me accessibility score

93

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

Links do not have a discernible name

Best Practices

oddle.me best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

oddle.me 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

Links do not have descriptive text

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 Oddle.me 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 Oddle.me 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

oddle.me

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