1.1 sec in total
157 ms
699 ms
213 ms
Visit barrysax.com now to see the best up-to-date Barry Sax content and also check out these interesting facts you probably never knew about barrysax.com
Soloist, widely performed composer and host of The Barry Sax Show Podcast.
Visit barrysax.comWe analyzed Barrysax.com page load time and found that the first response time was 157 ms and then it took 912 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.
barrysax.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value6.5 s
9/100
25%
Value3.9 s
82/100
10%
Value410 ms
67/100
30%
Value0
100/100
15%
Value7.5 s
47/100
10%
157 ms
68 ms
35 ms
49 ms
47 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 54% of them (45 requests) were addressed to the original Barrysax.com, 36% (30 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (296 ms) relates to the external source I0.wp.com.
Page size can be reduced by 354.2 kB (41%)
873.2 kB
519.0 kB
In fact, the total size of Barrysax.com main page is 873.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 336.1 kB which makes up the majority of the site volume.
Potential reduce by 295.5 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 295.5 kB or 88% of the original size.
Potential reduce by 0 B
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. Barry Sax images are well optimized though.
Potential reduce by 39.2 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 39.2 kB or 12% of the original size.
Potential reduce by 19.5 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. Barrysax.com needs all CSS files to be minified and compressed as it can save up to 19.5 kB or 19% of the original size.
Number of requests can be reduced by 44 (88%)
50
6
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Barry Sax. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
barrysax.com
157 ms
barrysax.com
68 ms
mediaelementplayer-legacy.min.css
35 ms
wp-mediaelement.min.css
49 ms
ladda.min.css
47 ms
picker.classic.css
46 ms
picker.classic.date.css
47 ms
intlTelInput.css
81 ms
bookly-main.css
87 ms
bootstrap.min.css
59 ms
customer-profile.css
53 ms
pagenavi-css.css
52 ms
style.css
53 ms
css
97 ms
lazyload-shared.css
78 ms
jetpack.css
59 ms
jquery.min.js
69 ms
jquery-migrate.min.js
67 ms
spin.min.js
67 ms
ladda.min.js
68 ms
moment.min.js
72 ms
hammer.min.js
69 ms
jquery.hammer.min.js
69 ms
picker.js
69 ms
picker.date.js
70 ms
bookly.min.js
71 ms
intlTelInput.min.js
70 ms
customer-profile.js
71 ms
et-core-unified-205522.min.css
72 ms
image-cdn.js
118 ms
idle-timer.min.js
118 ms
custom.js
118 ms
lazyload-shared.js
127 ms
lazyload-youtube.js
121 ms
lazyload-vimeo.js
122 ms
scripts.min.js
131 ms
smoothscroll.js
123 ms
jquery.fitvids.js
121 ms
e-202407.js
24 ms
easypiechart.js
123 ms
salvattore.js
118 ms
common.js
108 ms
mediaelement-and-player.min.js
113 ms
mediaelement-migrate.min.js
107 ms
wp-mediaelement.min.js
111 ms
gtm.js
209 ms
DSC_9661.jpg
191 ms
Elipsos.jpg
296 ms
MUSX-Site-Logo-150x150.png
155 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
45 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
69 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff
71 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
70 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff
68 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
69 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
52 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff
95 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
95 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff
70 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
96 ms
modules.ttf
19 ms
pxiByp8kv8JHgFVrLEj6V1g.woff
94 ms
pxiByp8kv8JHgFVrLEj6V1s.ttf
95 ms
pxiByp8kv8JHgFVrLCz7V1g.woff
97 ms
pxiByp8kv8JHgFVrLCz7V1s.ttf
100 ms
pxiByp8kv8JHgFVrLDD4V1g.woff
97 ms
pxiByp8kv8JHgFVrLDD4V1s.ttf
99 ms
pxiByp8kv8JHgFVrLBT5V1g.woff
97 ms
pxiByp8kv8JHgFVrLBT5V1s.ttf
97 ms
pxiByp8kv8JHgFVrLGT9V1g.woff
99 ms
pxiByp8kv8JHgFVrLGT9V1s.ttf
101 ms
pxiEyp8kv8JHgFVrFJM.woff
103 ms
pxiEyp8kv8JHgFVrFJA.ttf
101 ms
pxiByp8kv8JHgFVrLDz8V1g.woff
102 ms
pxiByp8kv8JHgFVrLDz8V1s.ttf
101 ms
pxiByp8kv8JHgFVrLFj_V1g.woff
102 ms
pxiByp8kv8JHgFVrLFj_V1s.ttf
106 ms
pxiGyp8kv8JHgFVrLPTedA.woff
103 ms
pxiGyp8kv8JHgFVrLPTedw.ttf
107 ms
analytics.js
57 ms
fbevents.js
71 ms
collect
33 ms
barrysax.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
barrysax.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
barrysax.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Barrysax.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 Barrysax.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.
barrysax.com
Open Graph data is detected on the main page of Barry Sax. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: