Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

app.waiterio.com

Restaurant POS system | Waiterio Restaurant Point of Sale

Page Load Speed

141 ms in total

First Response

10 ms

Resources Loaded

131 ms

Page Rendered

0 ms

About Website

Click here to check amazing App Waiterio content for United States. Otherwise, check out these important facts you probably never knew about app.waiterio.com

The Restaurant POS system for restaurants in 70+ countries! Waiterio Point of Sale is the fastest way to handle restaurants' orders

Visit app.waiterio.com

Key Findings

We analyzed App.waiterio.com page load time and found that the first response time was 10 ms and then it took 131 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

app.waiterio.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value1,360 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

app.waiterio.com

10 ms

app.waiterio.com

23 ms

main.6a0d20c01365677a3e5f.js

13 ms

29 ms

gtm.js

56 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 43% of them (3 requests) were addressed to the original App.waiterio.com, 14% (1 request) were made to Js.stripe.com and 14% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (56 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.6 kB (1%)

Content Size

403.2 kB

After Optimization

398.6 kB

In fact, the total size of App.waiterio.com main page is 403.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Javascripts take 396.6 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 4.5 kB

  • Original 6.6 kB
  • After minification 6.6 kB
  • After compression 2.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 4.5 kB or 68% of the original size.

JavaScript Optimization

-0%

Potential reduce by 95 B

  • Original 396.6 kB
  • After minification 396.6 kB
  • After compression 396.5 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.

Requests Breakdown

Number of requests can be reduced by 4 (80%)

Requests Now

5

After Optimization

1

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

Accessibility Review

app.waiterio.com accessibility score

69

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

app.waiterio.com 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

Page has valid source maps

SEO Factors

app.waiterio.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise App.waiterio.com 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 App.waiterio.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 data is detected on the main page of App Waiterio. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: