Tools & Wizards About Us
watson.net screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

watson.net

Watson & Associates

Page Load Speed

4.9 sec in total

First Response

198 ms

Resources Loaded

3.5 sec

Page Rendered

1.2 sec

watson.net screenshot

About Website

Click here to check amazing Watson content. Otherwise, check out these important facts you probably never knew about watson.net

Watson & Associates, the Performance Improvement network.

Visit watson.net

Key Findings

We analyzed Watson.net page load time and found that the first response time was 198 ms and then it took 4.7 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.net performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.373

28/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

watson.net

198 ms

www.watsonassociates.nl

587 ms

museredirect.js

122 ms

site_global.css

301 ms

index.css

342 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Watson.net, 61% (51 requests) were made to Watsonassociates.nl and 14% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Watsonassociates.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 787.1 kB (34%)

Content Size

2.3 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Watson.net main page is 2.3 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-44%

Potential reduce by 258 B

  • Original 593 B
  • After minification 547 B
  • After compression 335 B

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 258 B or 44% of the original size.

Image Optimization

-8%

Potential reduce by 113.7 kB

  • Original 1.4 MB
  • After minification 1.3 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

-69%

Potential reduce by 620.6 kB

  • Original 893.0 kB
  • After minification 892.7 kB
  • After compression 272.4 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 620.6 kB or 69% of the original size.

CSS Optimization

-89%

Potential reduce by 52.6 kB

  • Original 59.4 kB
  • After minification 47.8 kB
  • After compression 6.8 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.net needs all CSS files to be minified and compressed as it can save up to 52.6 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (40%)

Requests Now

81

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 81 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 25 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

watson.net

watson.net

198 ms

www.watsonassociates.nl

www.watsonassociates.nl

587 ms

museredirect.js

museredirect.js

122 ms

site_global.css

site_global.css

301 ms

index.css

index.css

342 ms

museutils.js

museutils.js

308 ms

whatinput.js

whatinput.js

301 ms

jquery.musemenu.js

jquery.musemenu.js

301 ms

webpro.js

webpro.js

239 ms

musewpslideshow.js

musewpslideshow.js

347 ms

jquery.museoverlay.js

jquery.museoverlay.js

481 ms

touchswipe.js

touchswipe.js

484 ms

jquery.watch.js

jquery.watch.js

485 ms

jquery.musepolyfill.bgsize.js

jquery.musepolyfill.bgsize.js

486 ms

jquery.scrolleffects.js

jquery.scrolleffects.js

489 ms

electrolize:n4:all.js

electrolize:n4:all.js

54 ms

1

1

198 ms

maps

maps

92 ms

beeldmerk-watson-def.jpg

beeldmerk-watson-def.jpg

151 ms

blank.gif

blank.gif

148 ms

_s3t9884-crop-u1556.jpg

_s3t9884-crop-u1556.jpg

153 ms

_s3t9784-crop-u1570.jpg

_s3t9784-crop-u1570.jpg

155 ms

_s3t9859-crop-u1584.jpg

_s3t9859-crop-u1584.jpg

151 ms

_s3t9829-crop-u1549.jpg

_s3t9829-crop-u1549.jpg

183 ms

_s3t9900-crop-u1563.jpg

_s3t9900-crop-u1563.jpg

427 ms

_s3t0659-crop-u1577.jpg

_s3t0659-crop-u1577.jpg

425 ms

_s3t9788-crop-u1599.jpg

_s3t9788-crop-u1599.jpg

424 ms

_s3t9845verzoek-crop-u1614.jpg

_s3t9845verzoek-crop-u1614.jpg

426 ms

_s3t9813-crop-u1628.jpg

_s3t9813-crop-u1628.jpg

425 ms

_s3t0363-crop-u1592.jpg

_s3t0363-crop-u1592.jpg

424 ms

_s3t0643-crop-u1607.jpg

_s3t0643-crop-u1607.jpg

426 ms

_s3t0347-crop-u1621.jpg

_s3t0347-crop-u1621.jpg

450 ms

_s3t9819-crop-u1643.jpg

_s3t9819-crop-u1643.jpg

449 ms

silhouette.gif

silhouette.gif

449 ms

_s3t0335-crop-u1636.jpg

_s3t0335-crop-u1636.jpg

451 ms

linkedin_circle_black-512.png

linkedin_circle_black-512.png

449 ms

twitter_icon.jpg

twitter_icon.jpg

476 ms

facebook_icon.png

facebook_icon.png

477 ms

u527-17-r.png

u527-17-r.png

477 ms

u527-17-m.png

u527-17-m.png

495 ms

u527-17-fs.png

u527-17-fs.png

496 ms

ar2.png

ar2.png

461 ms

ar.png

ar.png

534 ms

agile.png

agile.png

533 ms

itsm_icon.png

itsm_icon.png

535 ms

people_icon.png

people_icon.png

545 ms

academy_icon.png

academy_icon.png

544 ms

istock_000022861986_xxxlarge.jpg

istock_000022861986_xxxlarge.jpg

1684 ms

water_texture2339.jpg

water_texture2339.jpg

779 ms

u527-17.png

u527-17.png

684 ms

embed

embed

422 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

48 ms

UiLN7VT7293S324gdZtsz9OoJMhAMO1A6JBJWvFe_qJffHLJggMdeMI6MK6gwyTaZA4cdhoXSkoRScmyie8hZAFCdamqOcFzdQ6I.eot

UiLN7VT7293S324gdZtsz9OoJMhAMO1A6JBJWvFe_qJffHLJggMdeMI6MK6gwyTaZA4cdhoXSkoRScmyie8hZAFCdamqOcFzdQ6I.eot

138 ms

pie.js

pie.js

523 ms

istock_000011217377large.jpg

istock_000011217377large.jpg

908 ms

loading.gif

loading.gif

360 ms

p.gif

p.gif

141 ms

js

js

55 ms

init_embed.js

init_embed.js

41 ms

common.js

common.js

60 ms

map.js

map.js

71 ms

google4.png

google4.png

114 ms

overlay.js

overlay.js

22 ms

util.js

util.js

102 ms

onion.js

onion.js

102 ms

search_impl.js

search_impl.js

108 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

178 ms

stats.js

stats.js

77 ms

kh

kh

89 ms

transparent.png

transparent.png

68 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

60 ms

controls.js

controls.js

19 ms

css

css

72 ms

vt

vt

122 ms

vt

vt

122 ms

mapcnt6.png

mapcnt6.png

22 ms

vt

vt

103 ms

vt

vt

99 ms

vt

vt

119 ms

vt

vt

109 ms

vt

vt

138 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

15 ms

istock_000002087389_large.jpg

istock_000002087389_large.jpg

608 ms

istock_000002391791_large.jpg

istock_000002391791_large.jpg

319 ms

Accessibility Review

watson.net accessibility score

33

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

watson.net 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

High

Page has valid source maps

SEO Factors

watson.net SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watson.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Watson.net 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.net

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