Tools & Wizards About Us
whatmenu.com screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

whatmenu.com

Whatmenu: discover Coupons and Save near me

Page Load Speed

1.2 sec in total

First Response

62 ms

Resources Loaded

1.1 sec

Page Rendered

71 ms

whatmenu.com screenshot

About Website

Visit whatmenu.com now to see the best up-to-date Whatmenu content and also check out these interesting facts you probably never knew about whatmenu.com

Discover and save on coupons and menus, take outs, meals and more

Visit whatmenu.com

Key Findings

We analyzed Whatmenu.com page load time and found that the first response time was 62 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

whatmenu.com performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

whatmenu.com

62 ms

restaurant.whatmenu.com

475 ms

adsbygoogle.js

145 ms

leaflet.css

266 ms

leaflet.js

262 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Whatmenu.com, 71% (12 requests) were made to Restaurant.whatmenu.com and 12% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (475 ms) relates to the external source Restaurant.whatmenu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 147.5 kB (37%)

Content Size

398.2 kB

After Optimization

250.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Whatmenu.com main page is 398.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 361.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 18.1 kB

  • Original 24.9 kB
  • After minification 24.8 kB
  • After compression 6.8 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 18.1 kB or 73% of the original size.

Image Optimization

-15%

Potential reduce by 1.7 kB

  • Original 11.7 kB
  • After minification 10.0 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, Whatmenu needs image optimization as it can save up to 1.7 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-35%

Potential reduce by 127.7 kB

  • Original 361.7 kB
  • After minification 361.7 kB
  • After compression 233.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 127.7 kB or 35% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

  • AJAX
  • Images
  • JavaScript

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatmenu. According to our analytics all requests are already optimized.

Network Requests Diagram

whatmenu.com

whatmenu.com

62 ms

restaurant.whatmenu.com

restaurant.whatmenu.com

475 ms

adsbygoogle.js

adsbygoogle.js

145 ms

leaflet.css

leaflet.css

266 ms

leaflet.js

leaflet.js

262 ms

dashicons.min.css

dashicons.min.css

269 ms

admin-bar.min.css

admin-bar.min.css

272 ms

style.min.css

style.min.css

264 ms

theme.min.css

theme.min.css

276 ms

style.css

style.css

386 ms

style.css

style.css

388 ms

show_ads_impl.js

show_ads_impl.js

244 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

20 ms

whatmenu.png

whatmenu.png

151 ms

whale_navigate.png

whale_navigate.png

157 ms

ads

ads

29 ms

print.css

print.css

132 ms

Accessibility Review

whatmenu.com accessibility score

60

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

Image elements do not have [alt] attributes

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

whatmenu.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

whatmenu.com SEO score

87

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

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Whatmenu.com 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 Whatmenu.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

whatmenu.com

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