Tools & Wizards About Us
watson.bar screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

watson.bar

Watson Bar - Because a Better World Starts with Good Food

Page Load Speed

6 sec in total

First Response

1.2 sec

Resources Loaded

4.1 sec

Page Rendered

830 ms

watson.bar screenshot

About Website

Visit watson.bar now to see the best up-to-date Watson content for Netherlands and also check out these interesting facts you probably never knew about watson.bar

Because a Better World Starts with Good Food

Visit watson.bar

Key Findings

We analyzed Watson.bar page load time and found that the first response time was 1.2 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

watson.bar performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

watson.bar

1151 ms

style.min.css

148 ms

wpautoterms.css

213 ms

styles.css

212 ms

css

37 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 78% of them (38 requests) were addressed to the original Watson.bar, 10% (5 requests) were made to Youtube.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Watson.bar.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.5 kB (3%)

Content Size

4.1 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Watson.bar main page is 4.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 89.2 kB

  • Original 108.7 kB
  • After minification 103.4 kB
  • After compression 19.5 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 89.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 3.8 kB

  • Original 3.7 MB
  • After minification 3.7 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. Watson images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.9 kB

  • Original 251.0 kB
  • After minification 251.0 kB
  • After compression 248.1 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

-10%

Potential reduce by 13.6 kB

  • Original 132.2 kB
  • After minification 123.0 kB
  • After compression 118.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. Watson.bar has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (58%)

Requests Now

45

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watson. 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 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

watson.bar

watson.bar

1151 ms

style.min.css

style.min.css

148 ms

wpautoterms.css

wpautoterms.css

213 ms

styles.css

styles.css

212 ms

css

css

37 ms

bootstrap.css

bootstrap.css

301 ms

style.css

style.css

217 ms

blocks.css

blocks.css

218 ms

fontawesome-all.css

fontawesome-all.css

222 ms

jquery.min.js

jquery.min.js

371 ms

jquery-migrate.min.js

jquery-migrate.min.js

291 ms

dom-ready.min.js

dom-ready.min.js

311 ms

base.js

base.js

296 ms

bootstrap.js

bootstrap.js

318 ms

ngo-organization-custom.js

ngo-organization-custom.js

365 ms

focus-nav.js

focus-nav.js

382 ms

script.js

script.js

36 ms

ssba.css

ssba.css

339 ms

hooks.min.js

hooks.min.js

338 ms

i18n.min.js

i18n.min.js

434 ms

index.js

index.js

445 ms

index.js

index.js

445 ms

ssba.js

ssba.js

445 ms

script.js

script.js

445 ms

x3fhIw8xBXc

x3fhIw8xBXc

188 ms

cropped-Indonesian-87.png

cropped-Indonesian-87.png

150 ms

4446.jpg

4446.jpg

710 ms

1686.jpg

1686.jpg

835 ms

2149040307.jpg

2149040307.jpg

834 ms

%E0%B8%A3%E0%B8%B2%E0%B8%84%E0%B8%B2-%E0%B8%A3%E0%B8%B1%E0%B8%9A-%E0%B8%AA%E0%B8%A3%E0%B9%89%E0%B8%B2%E0%B8%87-%E0%B8%9A%E0%B9%89%E0%B8%B2%E0%B8%99.jpg

%E0%B8%A3%E0%B8%B2%E0%B8%84%E0%B8%B2-%E0%B8%A3%E0%B8%B1%E0%B8%9A-%E0%B8%AA%E0%B8%A3%E0%B9%89%E0%B8%B2%E0%B8%87-%E0%B8%9A%E0%B9%89%E0%B8%B2%E0%B8%99.jpg

538 ms

%E0%B8%99%E0%B8%A1%E0%B8%95%E0%B8%A3%E0%B8%B2%E0%B8%AB%E0%B8%A1%E0%B8%B5.jpg

%E0%B8%99%E0%B8%A1%E0%B8%95%E0%B8%A3%E0%B8%B2%E0%B8%AB%E0%B8%A1%E0%B8%B5.jpg

524 ms

istockphoto-1320126340-612x612-1.jpg

istockphoto-1320126340-612x612-1.jpg

521 ms

istockphoto-1310110490-612x612-1.jpg

istockphoto-1310110490-612x612-1.jpg

522 ms

insurance_000253-1.jpg

insurance_000253-1.jpg

523 ms

close-up-nurse-comforting-ill-patient-hospital-ward.jpg

close-up-nurse-comforting-ill-patient-hospital-ward.jpg

929 ms

facebook.png

facebook.png

538 ms

pinterest.png

pinterest.png

707 ms

twitter.png

twitter.png

707 ms

linkedin.png

linkedin.png

711 ms

fa-regular-400.woff

fa-regular-400.woff

727 ms

fa-solid-900.woff

fa-solid-900.woff

731 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

27 ms

base.js

base.js

59 ms

ad_status.js

ad_status.js

172 ms

u3o6s91JBL8hdS-8zlKaE9_QjMMICyQyS6sMo66aQxY.js

u3o6s91JBL8hdS-8zlKaE9_QjMMICyQyS6sMo66aQxY.js

134 ms

embed.js

embed.js

41 ms

id

id

28 ms

Create

Create

137 ms

Accessibility Review

watson.bar accessibility score

98

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

watson.bar best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

watson.bar SEO score

86

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

Links do not have descriptive text

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

    TH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watson.bar can be misinterpreted by Google and other search engines. Our service has detected that Thai is used on the page, and it does not match the claimed English language. Our system also found out that Watson.bar 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

watson.bar

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