Tools & Wizards About Us
mealsy.ca screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

mealsy.ca

Mealsy: Restaurant Online Ordering System, POS, Self-Ordering Kiosk.

Page Load Speed

20 sec in total

First Response

27 ms

Resources Loaded

19.6 sec

Page Rendered

456 ms

mealsy.ca screenshot

About Website

Visit mealsy.ca now to see the best up-to-date Mealsy content for Canada and also check out these interesting facts you probably never knew about mealsy.ca

Get Website, App, POS, Online Ordering Software, Self-ordering kiosk, Digital signage & More. Start today!

Visit mealsy.ca

Key Findings

We analyzed Mealsy.ca page load time and found that the first response time was 27 ms and then it took 20 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

mealsy.ca performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

mealsy.ca

27 ms

mealsy.ca

185 ms

style.min.css

7 ms

theme.min.css

11 ms

header-footer.min.css

11 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 76% of them (48 requests) were addressed to the original Mealsy.ca, 17% (11 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Web.archive.org. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Web.archive.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 713.8 kB (51%)

Content Size

1.4 MB

After Optimization

677.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mealsy.ca main page is 1.4 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 495.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 93.8 kB

  • Original 111.8 kB
  • After minification 109.2 kB
  • After compression 18.0 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 93.8 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 44 B

  • Original 495.5 kB
  • After minification 495.4 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. Mealsy images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 261.1 kB

  • Original 376.8 kB
  • After minification 376.8 kB
  • After compression 115.7 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 261.1 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 358.9 kB

  • Original 406.9 kB
  • After minification 403.2 kB
  • After compression 48.0 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. Mealsy.ca needs all CSS files to be minified and compressed as it can save up to 358.9 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (61%)

Requests Now

49

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mealsy.ca

mealsy.ca

27 ms

mealsy.ca

mealsy.ca

185 ms

style.min.css

style.min.css

7 ms

theme.min.css

theme.min.css

11 ms

header-footer.min.css

header-footer.min.css

11 ms

frontend-lite.min.css

frontend-lite.min.css

16 ms

post-6.css

post-6.css

11 ms

swiper.min.css

swiper.min.css

12 ms

frontend-lite.min.css

frontend-lite.min.css

12 ms

global.css

global.css

20 ms

post-10.css

post-10.css

13 ms

post-97.css

post-97.css

14 ms

post-100.css

post-100.css

21 ms

css

css

39 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

21 ms

animations.min.css

animations.min.css

22 ms

hello-frontend.min.js

hello-frontend.min.js

22 ms

jquery.min.js

jquery.min.js

28 ms

jquery-migrate.min.js

jquery-migrate.min.js

26 ms

jquery.sticky.min.js

jquery.sticky.min.js

26 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

26 ms

imagesloaded.min.js

imagesloaded.min.js

38 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

38 ms

webpack.runtime.min.js

webpack.runtime.min.js

38 ms

frontend-modules.min.js

frontend-modules.min.js

40 ms

hooks.min.js

hooks.min.js

39 ms

i18n.min.js

i18n.min.js

38 ms

frontend.min.js

frontend.min.js

40 ms

waypoints.min.js

waypoints.min.js

41 ms

core.min.js

core.min.js

40 ms

frontend.min.js

frontend.min.js

43 ms

elements-handlers.min.js

elements-handlers.min.js

44 ms

Mealsy_Red-2.webp

Mealsy_Red-2.webp

29 ms

Mealsy_LogoType.webp

Mealsy_LogoType.webp

28 ms

M_Index_Home_POS.png

M_Index_Home_POS.png

30 ms

M_Index_Home_Self.webp

M_Index_Home_Self.webp

29 ms

M_Index_Home_OnlineO.png

M_Index_Home_OnlineO.png

31 ms

M_Index_Home_Mobile.jpg

M_Index_Home_Mobile.jpg

31 ms

M_Website_Icons_POS.webp

M_Website_Icons_POS.webp

30 ms

M_Index_POS-1.webp

M_Index_POS-1.webp

33 ms

M_Index_POS1.webp

M_Index_POS1.webp

32 ms

M_Index_POS2.webp

M_Index_POS2.webp

35 ms

M_Index_POS3.webp

M_Index_POS3.webp

33 ms

M_Index_POS4.webp

M_Index_POS4.webp

32 ms

M_Index_Home_Self-1.webp

M_Index_Home_Self-1.webp

35 ms

M_Website_Icons_SelfOrdering.webp

M_Website_Icons_SelfOrdering.webp

34 ms

M_Website_Icons_OnlineOrdering.webp

M_Website_Icons_OnlineOrdering.webp

35 ms

Mealsy_White-1.webp

Mealsy_White-1.webp

36 ms

Mealsy_LogoTypeWhite.svg

Mealsy_LogoTypeWhite.svg

36 ms

hotjar-2098261.js

hotjar-2098261.js

610 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

15 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

20 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

28 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

36 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

37 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

37 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

37 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

36 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

36 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

38 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

37 ms

fbevents.js

fbevents.js

2249 ms

js

js

445 ms

Accessibility Review

mealsy.ca accessibility score

97

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.

Best Practices

mealsy.ca 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

mealsy.ca 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 Mealsy.ca 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 Mealsy.ca 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

mealsy.ca

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