Tools & Wizards About Us
williameddins.com screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

williameddins.com

William Eddins | William Eddins

Page Load Speed

2.6 sec in total

First Response

31 ms

Resources Loaded

2.4 sec

Page Rendered

162 ms

williameddins.com screenshot

About Website

Click here to check amazing William Eddins content. Otherwise, check out these important facts you probably never knew about williameddins.com

musician and entrepreneur William Eddins is the Music Director Emeritus of the Edmonton Symphony Orchestra and a frequent guest conductor of major...

Visit williameddins.com

Key Findings

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

Performance Metrics

williameddins.com performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

williameddins.com

31 ms

williameddins.com

2127 ms

style.min.css

9 ms

style.css

13 ms

magnific-popup.css

20 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 76% of them (28 requests) were addressed to the original Williameddins.com, 22% (8 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Williameddins.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 192.2 kB (26%)

Content Size

736.7 kB

After Optimization

544.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 21.5 kB

  • Original 28.7 kB
  • After minification 28.3 kB
  • After compression 7.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. 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 21.5 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 394.8 kB
  • After minification 394.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. William Eddins images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 66.7 kB

  • Original 134.4 kB
  • After minification 134.4 kB
  • After compression 67.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 66.7 kB or 50% of the original size.

CSS Optimization

-58%

Potential reduce by 104.1 kB

  • Original 178.8 kB
  • After minification 177.1 kB
  • After compression 74.7 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. Williameddins.com needs all CSS files to be minified and compressed as it can save up to 104.1 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (85%)

Requests Now

27

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

williameddins.com

williameddins.com

31 ms

williameddins.com

williameddins.com

2127 ms

style.min.css

style.min.css

9 ms

style.css

style.css

13 ms

magnific-popup.css

magnific-popup.css

20 ms

flexslider.css

flexslider.css

18 ms

owl.carousel.css

owl.carousel.css

19 ms

owl.theme.default.css

owl.theme.default.css

18 ms

style.css

style.css

15 ms

css

css

28 ms

genericons.css

genericons.css

20 ms

components.min.css

components.min.css

25 ms

font-awesome.min.css

font-awesome.min.css

23 ms

editor-fe.min.css

editor-fe.min.css

27 ms

custom-styles.css

custom-styles.css

28 ms

application.min.css

application.min.css

30 ms

jquery.min.js

jquery.min.js

32 ms

jquery-migrate.min.js

jquery-migrate.min.js

31 ms

imagesloaded.min.js

imagesloaded.min.js

31 ms

masonry.min.js

masonry.min.js

33 ms

jquery.masonry.min.js

jquery.masonry.min.js

33 ms

argent.js

argent.js

37 ms

navigation.js

navigation.js

33 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

35 ms

public.min.js

public.min.js

37 ms

application.min.js

application.min.js

41 ms

genericons.css

genericons.css

23 ms

cropped-EDIT_JRD6706-3.jpg

cropped-EDIT_JRD6706-3.jpg

38 ms

0_38_768_1023_20220829_NR_BillEddins_DSC4687-Edit-web-768x1152.jpg

0_38_768_1023_20220829_NR_BillEddins_DSC4687-Edit-web-768x1152.jpg

39 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7ilwkzuA_qNBQ.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7ilwkzuA_qNBQ.ttf

48 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7ilwkzuA_qNBQ.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7ilwkzuA_qNBQ.ttf

86 ms

4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlYHuJqvmSCnqsV8z9c.ttf

4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlYHuJqvmSCnqsV8z9c.ttf

100 ms

4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlbgv5qvmSCnqsV8z9c.ttf

4UaSrEBBsBhlBjvfkSLk3abBFkvpkARTPlbgv5qvmSCnqsV8z9c.ttf

92 ms

4UacrEBBsBhlBjvfkQjt71kZfyBzPgNGERI49aqmkySFru1-.ttf

4UacrEBBsBhlBjvfkQjt71kZfyBzPgNGERI49aqmkySFru1-.ttf

93 ms

4UacrEBBsBhlBjvfkQjt71kZfyBzPgNG9hU49aqmkySFru1-.ttf

4UacrEBBsBhlBjvfkQjt71kZfyBzPgNG9hU49aqmkySFru1-.ttf

93 ms

u-4V0qWljRw-Pd815fNqc8T_wAFcX-c37MPiNYlWniJ2hJXH9fKVy0bqIf6lB8y_.ttf

u-4V0qWljRw-Pd815fNqc8T_wAFcX-c37MPiNYlWniJ2hJXH9fKVy0bqIf6lB8y_.ttf

93 ms

u-4V0qWljRw-Pd815fNqc8T_wAFcX-c37MPiNYlWniJ2hJXHIPWVy0bqIf6lB8y_.ttf

u-4V0qWljRw-Pd815fNqc8T_wAFcX-c37MPiNYlWniJ2hJXHIPWVy0bqIf6lB8y_.ttf

124 ms

Accessibility Review

williameddins.com accessibility score

100

Accessibility Issues

Best Practices

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

SEO Factors

williameddins.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 Williameddins.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 Williameddins.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

williameddins.com

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