Tools & Wizards About Us
mealsqueeze.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

mealsqueeze.com

Google Domains Hosted Site

Page Load Speed

4.4 sec in total

First Response

215 ms

Resources Loaded

3.8 sec

Page Rendered

412 ms

mealsqueeze.com screenshot

About Website

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

Family-friendly weekly meal plans created by a registered dietitian. Comes with 7 balanced recipes that are easy to make and budget-friendly. Use the categorized shopping list to make grocery shoppi...

Visit mealsqueeze.com

Key Findings

We analyzed Mealsqueeze.com page load time and found that the first response time was 215 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

mealsqueeze.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,100 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

mealsqueeze.com

215 ms

www.mealsqueeze.com

231 ms

www.mealsqueeze.com

463 ms

gdprscript.js

134 ms

js

136 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 19% of them (14 requests) were addressed to the original Mealsqueeze.com, 26% (19 requests) were made to Fonts.gstatic.com and 16% (12 requests) were made to Cdn2.editmysite.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.6 kB (30%)

Content Size

869.2 kB

After Optimization

604.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mealsqueeze.com main page is 869.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. 70% of websites need less resources to load. Javascripts take 321.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 84.8 kB

  • Original 103.0 kB
  • After minification 101.2 kB
  • After compression 18.3 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 84.8 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 292.1 kB
  • After minification 292.1 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. Mealsqueeze images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 79.8 kB

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

CSS Optimization

-66%

Potential reduce by 100.0 kB

  • Original 152.7 kB
  • After minification 148.3 kB
  • After compression 52.6 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. Mealsqueeze.com needs all CSS files to be minified and compressed as it can save up to 100.0 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (73%)

Requests Now

48

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mealsqueeze.com

mealsqueeze.com

215 ms

www.mealsqueeze.com

www.mealsqueeze.com

231 ms

www.mealsqueeze.com

www.mealsqueeze.com

463 ms

gdprscript.js

gdprscript.js

134 ms

js

js

136 ms

signup-form-widget.min.js

signup-form-widget.min.js

343 ms

sites.css

sites.css

322 ms

fancybox.css

fancybox.css

375 ms

social-icons.css

social-icons.css

477 ms

main_style.css

main_style.css

342 ms

css

css

274 ms

css

css

320 ms

css

css

374 ms

css

css

480 ms

css

css

480 ms

site_membership.css

site_membership.css

470 ms

templateArtifacts.js

templateArtifacts.js

512 ms

jquery.min.js

jquery.min.js

339 ms

stl.js

stl.js

386 ms

main.js

main.js

593 ms

main-membership-site.js

main-membership-site.js

449 ms

commerce-core.js

commerce-core.js

474 ms

main-commerce-browse.js

main-commerce-browse.js

589 ms

js

js

337 ms

widgets.js

widgets.js

1066 ms

weebly-anchor.js

weebly-anchor.js

591 ms

plugins.js

plugins.js

1064 ms

custom.js

custom.js

1065 ms

main-customer-accounts-site.js

main-customer-accounts-site.js

1151 ms

345 ms

analytics.js

analytics.js

225 ms

jquery.js

jquery.js

791 ms

collect

collect

709 ms

jquery.min.js

jquery.min.js

279 ms

visit

visit

1159 ms

x

x

1157 ms

clickstream

clickstream

1158 ms

collect

collect

218 ms

white-logo-transparent-2x.png

white-logo-transparent-2x.png

218 ms

birdseye-header-text_1_orig.png

birdseye-header-text_1_orig.png

217 ms

ad-based-recipes.png

ad-based-recipes.png

1095 ms

Food-Plate.jpg

Food-Plate.jpg

496 ms

mem5YaGs126MiZpBA-UN_r8OUuhv.woff

mem5YaGs126MiZpBA-UN_r8OUuhv.woff

942 ms

mem5YaGs126MiZpBA-UN_r8OXOhv.woff

mem5YaGs126MiZpBA-UN_r8OXOhv.woff

1187 ms

mem8YaGs126MiZpBA-UFVZ0d.woff

mem8YaGs126MiZpBA-UFVZ0d.woff

1188 ms

mem8YaGs126MiZpBA-UFW50d.woff

mem8YaGs126MiZpBA-UFW50d.woff

1291 ms

mem5YaGs126MiZpBA-UN7rgOUuhv.woff

mem5YaGs126MiZpBA-UN7rgOUuhv.woff

1288 ms

mem5YaGs126MiZpBA-UN7rgOXOhv.woff

mem5YaGs126MiZpBA-UN7rgOXOhv.woff

1291 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrc.woff

1187 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrc.woff

1291 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrc.woff

1291 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrc.woff

1289 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5aDdvQ.woff

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5aDdvQ.woff

1310 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd5aDdvQ.woff

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd5aDdvQ.woff

1311 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd5aDdvQ.woff

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd5aDdvQ.woff

1310 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd5aDdvQ.woff

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd5aDdvQ.woff

1311 ms

mem6YaGs126MiZpBA-UFUK0Zdcs.woff

mem6YaGs126MiZpBA-UFUK0Zdcs.woff

1308 ms

mem6YaGs126MiZpBA-UFUK0Xdcs.woff

mem6YaGs126MiZpBA-UFUK0Xdcs.woff

1311 ms

memnYaGs126MiZpBA-UFUKWyV9hlIqU.woff

memnYaGs126MiZpBA-UFUKWyV9hlIqU.woff

1312 ms

memnYaGs126MiZpBA-UFUKWiUNhrIqU.woff

memnYaGs126MiZpBA-UFUKWiUNhrIqU.woff

1311 ms

memnYaGs126MiZpBA-UFUKWiUNhlIqU.woff

memnYaGs126MiZpBA-UFUKWiUNhlIqU.woff

1312 ms

api.js

api.js

865 ms

ga.js

ga.js

864 ms

snowday262.js

snowday262.js

512 ms

api.js

api.js

748 ms

m-outer-26f06e6dfafc73ef8d70171c2397785d.html

m-outer-26f06e6dfafc73ef8d70171c2397785d.html

95 ms

563 ms

552 ms

567 ms

m-outer-db271181c879d28f392f9d0ac8fdd7c5.js

m-outer-db271181c879d28f392f9d0ac8fdd7c5.js

204 ms

inner.html

inner.html

409 ms

recaptcha__en.js

recaptcha__en.js

58 ms

signup-form-widget.css

signup-form-widget.css

20 ms

Accessibility Review

mealsqueeze.com accessibility score

100

Accessibility Issues

Best Practices

mealsqueeze.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

mealsqueeze.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

Links are not crawlable

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mealsqueeze.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Mealsqueeze.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

mealsqueeze.com

Open Graph data is detected on the main page of Mealsqueeze. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: