Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

johnashtonthomas.com

Orchestrator | John Ashton Thomas

Page Load Speed

4.8 sec in total

First Response

1.3 sec

Resources Loaded

3.2 sec

Page Rendered

307 ms

johnashtonthomas.com screenshot

About Website

Visit johnashtonthomas.com now to see the best up-to-date John Ashton Thomas content and also check out these interesting facts you probably never knew about johnashtonthomas.com

Welcome to the site of world renowed orchestrator, composer and musican, John Ashton Thomas.

Visit johnashtonthomas.com

Key Findings

We analyzed Johnashtonthomas.com page load time and found that the first response time was 1.3 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

johnashtonthomas.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

16/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

johnashtonthomas.com

1340 ms

site.css

222 ms

jquery-1.7.2.min.js

762 ms

jquery.innerfade.js

232 ms

jat-custom.js

279 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 82% of them (9 requests) were addressed to the original Johnashtonthomas.com, 18% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Johnashtonthomas.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.9 kB (16%)

Content Size

420.7 kB

After Optimization

351.9 kB

In fact, the total size of Johnashtonthomas.com main page is 420.7 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. Only 10% of websites need less resources to load. Images take 298.4 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 2.0 kB

  • Original 3.4 kB
  • After minification 3.2 kB
  • After compression 1.4 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 2.0 kB or 58% of the original size.

Image Optimization

-0%

Potential reduce by 419 B

  • Original 298.4 kB
  • After minification 298.0 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. John Ashton Thomas images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 65.4 kB

  • Original 117.2 kB
  • After minification 114.6 kB
  • After compression 51.8 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 65.4 kB or 56% of the original size.

CSS Optimization

-65%

Potential reduce by 1.1 kB

  • Original 1.7 kB
  • After minification 1.5 kB
  • After compression 604 B

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. Johnashtonthomas.com needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (30%)

Requests Now

10

After Optimization

7

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

Accessibility Review

johnashtonthomas.com 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

johnashtonthomas.com 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

Page has valid source maps

SEO Factors

johnashtonthomas.com SEO score

96

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

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 Johnashtonthomas.com 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 Johnashtonthomas.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 John Ashton Thomas. 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: