Tools & Wizards About Us
brianwansink.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

brianwansink.com

Solve & Share - Solve and Share - Here are some solutions to practical eating-related problems

Page Load Speed

1.9 sec in total

First Response

123 ms

Resources Loaded

1.3 sec

Page Rendered

489 ms

brianwansink.com screenshot

About Website

Welcome to brianwansink.com homepage info - get ready to check Brianwansink best content for United States right away, or after learning these important things about brianwansink.com

If you want to feel healthier and happier, here are some tricks and solutions that have worked for others to lose weight, feel better, or improve relationships with their family and friends.

Visit brianwansink.com

Key Findings

We analyzed Brianwansink.com page load time and found that the first response time was 123 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

brianwansink.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value42.3 s

0/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value30.4 s

0/100

10%

Network Requests Diagram

brianwansink.com

123 ms

www.brianwansink.com

181 ms

sites.css

18 ms

fancybox.css

26 ms

social-icons.css

32 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 41% of them (20 requests) were addressed to the original Brianwansink.com, 27% (13 requests) were made to Cdn2.editmysite.com and 6% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (384 ms) relates to the external source Static.zotabox.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 458.2 kB (7%)

Content Size

6.4 MB

After Optimization

6.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brianwansink.com main page is 6.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. Only a small number of websites need less resources to load. Images take 5.9 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 44.1 kB

  • Original 57.1 kB
  • After minification 55.7 kB
  • After compression 13.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 44.1 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 404.7 kB

  • Original 5.9 MB
  • After minification 5.5 MB

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. Brianwansink images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 9.2 kB

  • Original 440.5 kB
  • After minification 440.5 kB
  • After compression 431.3 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 265 B

  • Original 38.7 kB
  • After minification 38.7 kB
  • After compression 38.5 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. Brianwansink.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (63%)

Requests Now

35

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brianwansink.com

brianwansink.com

123 ms

www.brianwansink.com

www.brianwansink.com

181 ms

sites.css

sites.css

18 ms

fancybox.css

fancybox.css

26 ms

social-icons.css

social-icons.css

32 ms

main_style.css

main_style.css

105 ms

font.css

font.css

26 ms

templateArtifacts.js

templateArtifacts.js

109 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

38 ms

stl.js

stl.js

32 ms

main.js

main.js

32 ms

js

js

63 ms

widgets.js

widgets.js

384 ms

player.js

player.js

48 ms

email-decode.min.js

email-decode.min.js

24 ms

plugins.js

plugins.js

193 ms

custom.js

custom.js

180 ms

main-customer-accounts-site.js

main-customer-accounts-site.js

32 ms

js

js

106 ms

js

js

178 ms

973994550

973994550

299 ms

973923268

973923268

234 ms

bg_feed.gif

bg_feed.gif

16 ms

1195563128.png

1195563128.png

226 ms

oig3-fvmwjriiptxdlnaqkws6_orig.jpeg

oig3-fvmwjriiptxdlnaqkws6_orig.jpeg

218 ms

img-2393_orig.jpg

img-2393_orig.jpg

216 ms

screen-shot-2021-03-17-at-2-28-40-pm_orig.png

screen-shot-2021-03-17-at-2-28-40-pm_orig.png

217 ms

wansink-interview-woman-with-fork-georgia-russian-3-22-23-mindless-eating_orig.jpg

wansink-interview-woman-with-fork-georgia-russian-3-22-23-mindless-eating_orig.jpg

219 ms

screen-shot-2021-03-17-at-7-32-51-pm_orig.png

screen-shot-2021-03-17-at-7-32-51-pm_orig.png

227 ms

low-res-small-i-love-these-two-three-books-slim-by-design-mindless-eating-asian-woman-fiverr-photo-copy-2_orig.jpg

low-res-small-i-love-these-two-three-books-slim-by-design-mindless-eating-asian-woman-fiverr-photo-copy-2_orig.jpg

219 ms

ga.js

ga.js

156 ms

snowday262.js

snowday262.js

154 ms

widgets.js

widgets.js

154 ms

Cento-medium.woff

Cento-medium.woff

261 ms

Cento-light.woff

Cento-light.woff

175 ms

Cento-bold.woff

Cento-bold.woff

204 ms

bold.woff

bold.woff

51 ms

regular.woff

regular.woff

50 ms

wsocial.woff

wsocial.woff

51 ms

sdk.js

sdk.js

57 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

61 ms

sdk.js

sdk.js

8 ms

49 ms

settings

settings

77 ms

api.js

api.js

12 ms

Cento-light.ttf

Cento-light.ttf

172 ms

tp2

tp2

123 ms

Cento-bold.ttf

Cento-bold.ttf

371 ms

Cento-medium.ttf

Cento-medium.ttf

188 ms

Accessibility Review

brianwansink.com accessibility score

86

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

SEO Factors

brianwansink.com SEO score

83

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

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

brianwansink.com

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