Tools & Wizards About Us

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

wtf.menu

WTF Digital Waiter | Contactless dining | POS | Digital menu for any restaurant

Page Load Speed

1.8 sec in total

First Response

11 ms

Resources Loaded

1.7 sec

Page Rendered

58 ms

About Website

Visit wtf.menu now to see the best up-to-date WTF content and also check out these interesting facts you probably never knew about wtf.menu

WTF Digital Waiter improves restaurant margins by 25%. The digital waiter is a combination of POS, Contactless dining, digital menu. WTF is a one-stop dashboard for all your dine-in, delivery and orde...

Visit wtf.menu

Key Findings

We analyzed Wtf.menu page load time and found that the first response time was 11 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

wtf.menu performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

8/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value800 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

wtf.menu

11 ms

wtf.menu

815 ms

ac43htd6kv

51 ms

13.1fea979d.chunk.css

800 ms

main.7599fc24.chunk.css

22 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 67% of them (6 requests) were addressed to the original Wtf.menu, 22% (2 requests) were made to Clarity.ms and 11% (1 request) were made to C.clarity.ms. The less responsive or slowest element that took the longest time to load (815 ms) belongs to the original domain Wtf.menu.

Page Optimization Overview & Recommendations

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

Content Size

412.0 kB

After Optimization

406.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Wtf.menu main page is 412.0 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 5% of websites need less resources to load. Javascripts take 395.8 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 4.7 kB

  • Original 7.8 kB
  • After minification 7.8 kB
  • After compression 3.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.7 kB or 61% of the original size.

JavaScript Optimization

-0%

Potential reduce by 230 B

  • Original 395.8 kB
  • After minification 395.8 kB
  • After compression 395.6 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

-1%

Potential reduce by 102 B

  • Original 8.4 kB
  • After minification 8.4 kB
  • After compression 8.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. Wtf.menu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (43%)

Requests Now

7

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

wtf.menu accessibility score

100

Accessibility Issues

Best Practices

wtf.menu 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

Missing source maps for large first-party JavaScript

SEO Factors

wtf.menu SEO score

100

Search Engine Optimization Advices

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 Wtf.menu 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 Wtf.menu 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 WTF. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: