Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

watch84.com

WATCH84 - Jonathan Gorczyca - Product Design & Development - Buffalo, NY

Page Load Speed

969 ms in total

First Response

79 ms

Resources Loaded

658 ms

Page Rendered

232 ms

watch84.com screenshot

About Website

Welcome to watch84.com homepage info - get ready to check WATCH84 best content right away, or after learning these important things about watch84.com

Designer and developer located in Buffalo, NY. I also enjoy building products, companies, and strategy. Let's talk!

Visit watch84.com

Key Findings

We analyzed Watch84.com page load time and found that the first response time was 79 ms and then it took 890 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

watch84.com performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value3.1 s

92/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

watch84.com

79 ms

www.watch84.com

58 ms

js

143 ms

bootstrap.min.css

51 ms

font-awesome.min.css

92 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 50% of them (13 requests) were addressed to the original Watch84.com, 27% (7 requests) were made to Fonts.gstatic.com and 12% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (203 ms) relates to the external source Fonts.googleapis.com.

Page Optimization Overview & Recommendations

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

Content Size

124.3 kB

After Optimization

115.2 kB

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

HTML Optimization

-77%

Potential reduce by 6.7 kB

  • Original 8.7 kB
  • After minification 6.6 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 2.1 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 6.7 kB or 77% of the original size.

JavaScript Optimization

-1%

Potential reduce by 1.2 kB

  • Original 84.1 kB
  • After minification 84.1 kB
  • After compression 82.9 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

-4%

Potential reduce by 1.2 kB

  • Original 31.6 kB
  • After minification 31.6 kB
  • After compression 30.4 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. Watch84.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (82%)

Requests Now

17

After Optimization

3

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

Accessibility Review

watch84.com accessibility score

100

Accessibility Issues

Best Practices

watch84.com best practices score

83

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

SEO Factors

watch84.com 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 Watch84.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 Watch84.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

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