Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

patrickwatson.net

Patrick Watson - on tour

Page Load Speed

1.4 sec in total

First Response

173 ms

Resources Loaded

1.1 sec

Page Rendered

161 ms

patrickwatson.net screenshot

About Website

Visit patrickwatson.net now to see the best up-to-date Patrick Watson content for United States and also check out these interesting facts you probably never knew about patrickwatson.net

Patrick Watson - new album Better in the Shade

Visit patrickwatson.net

Key Findings

We analyzed Patrickwatson.net page load time and found that the first response time was 173 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

patrickwatson.net performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value750 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

patrickwatson.net

173 ms

styles.css

65 ms

jquery-2.1.3.min.js

254 ms

conversion.js

16 ms

classic-081711.css

9 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 29% of them (6 requests) were addressed to the original Patrickwatson.net, 10% (2 requests) were made to Google-analytics.com and 10% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (630 ms) belongs to the original domain Patrickwatson.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 536.4 kB (37%)

Content Size

1.4 MB

After Optimization

895.1 kB

In fact, the total size of Patrickwatson.net main page is 1.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. 25% of websites need less resources to load. Images take 659.7 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 7.2 kB

  • Original 10.4 kB
  • After minification 9.2 kB
  • After compression 3.2 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 1.2 kB, which is 11% 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 7.2 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 1.9 kB

  • Original 659.7 kB
  • After minification 657.8 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. Patrick Watson images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 320.9 kB

  • Original 511.7 kB
  • After minification 507.1 kB
  • After compression 190.7 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 320.9 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 206.3 kB

  • Original 249.7 kB
  • After minification 248.2 kB
  • After compression 43.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. Patrickwatson.net needs all CSS files to be minified and compressed as it can save up to 206.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (37%)

Requests Now

19

After Optimization

12

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

Accessibility Review

patrickwatson.net accessibility score

95

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.

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

patrickwatson.net best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

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

High

Tap targets are not sized appropriately

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

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