Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 0

    Best Practices

  • 71

    SEO

    Google-friendlier than
    30% of websites

order.place

Restaurant POS and CRM Solution Provider in Singapore

Page Load Speed

1.1 sec in total

First Response

56 ms

Resources Loaded

983 ms

Page Rendered

49 ms

order.place screenshot

About Website

Welcome to order.place homepage info - get ready to check Order best content for Hong Kong right away, or after learning these important things about order.place

Visit order.place

Key Findings

We analyzed Order.place page load time and found that the first response time was 56 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

order.place performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.319

36/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

order.place

56 ms

www.aigens.com

926 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Order.place, 50% (1 request) were made to Aigens.com. The less responsive or slowest element that took the longest time to load (926 ms) relates to the external source Aigens.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 22 B (12%)

Content Size

177 B

After Optimization

155 B

In fact, the total size of Order.place main page is 177 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 177 B which makes up the majority of the site volume.

HTML Optimization

-12%

Potential reduce by 22 B

  • Original 177 B
  • After minification 177 B
  • After compression 155 B

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 22 B or 12% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

order.place accessibility score

75

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

[role] values are not valid

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.

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

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.

SEO Factors

order.place SEO score

71

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Order.place 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 Order.place main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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