Tools & Wizards About Us
bodysinging.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

bodysinging.com

Voice Lessons Nashville and Online - Body Singing by Breck Alan

Page Load Speed

3 sec in total

First Response

182 ms

Resources Loaded

2.7 sec

Page Rendered

149 ms

bodysinging.com screenshot

About Website

Click here to check amazing Body Singing content. Otherwise, check out these important facts you probably never knew about bodysinging.com

Voice Lessons Nashville. Find your unique voice. Your Body is Your Voice. Bring out the best singer in you

Visit bodysinging.com

Key Findings

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

Performance Metrics

bodysinging.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

39/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value2,990 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

bodysinging.com

182 ms

bodysinging.com

723 ms

flick.css

247 ms

bodysinging.com

547 ms

sbi-styles.min.css

263 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 39% of them (26 requests) were addressed to the original Bodysinging.com, 14% (9 requests) were made to Youtube.com and 12% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Bodysinging.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (61%)

Content Size

1.9 MB

After Optimization

723.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bodysinging.com main page is 1.9 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. 80% 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. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 42.6 kB

  • Original 56.4 kB
  • After minification 55.9 kB
  • After compression 13.8 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 42.6 kB or 76% of the original size.

Image Optimization

-93%

Potential reduce by 1.1 MB

  • Original 1.2 MB
  • After minification 80.6 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. Obviously, Body Singing needs image optimization as it can save up to 1.1 MB or 93% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 20.5 kB

  • Original 539.7 kB
  • After minification 539.7 kB
  • After compression 519.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 3.7 kB

  • Original 113.5 kB
  • After minification 113.5 kB
  • After compression 109.8 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. Bodysinging.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 44 (79%)

Requests Now

56

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Body Singing. 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.

Network Requests Diagram

bodysinging.com

bodysinging.com

182 ms

bodysinging.com

bodysinging.com

723 ms

flick.css

flick.css

247 ms

bodysinging.com

bodysinging.com

547 ms

sbi-styles.min.css

sbi-styles.min.css

263 ms

style.css

style.css

259 ms

style.min.css

style.min.css

311 ms

edd-blocks.css

edd-blocks.css

303 ms

bodysinging-banner-sizes.css

bodysinging-banner-sizes.css

485 ms

wpecpp.css

wpecpp.css

495 ms

edd.min.css

edd.min.css

514 ms

css

css

39 ms

style.css

style.css

559 ms

gppro-custom-1.css

gppro-custom-1.css

551 ms

jquery.min.js

jquery.min.js

793 ms

jquery-migrate.min.js

jquery-migrate.min.js

727 ms

scrollTo.js

scrollTo.js

760 ms

jquery.form.min.js

jquery.form.min.js

781 ms

mailchimp.js

mailchimp.js

781 ms

core.min.js

core.min.js

787 ms

datepicker.js

datepicker.js

1015 ms

css2

css2

56 ms

platform.js

platform.js

25 ms

35 ms

wpecpp.js

wpecpp.js

999 ms

edd-ajax.js

edd-ajax.js

1059 ms

sbi-scripts.min.js

sbi-scripts.min.js

1096 ms

sbi-sprite.png

sbi-sprite.png

235 ms

Screen-Shot-2014-09-24-at-7.29.24-PM-300x174.png

Screen-Shot-2014-09-24-at-7.29.24-PM-300x174.png

98 ms

sdk.js

sdk.js

92 ms

fbevents.js

fbevents.js

98 ms

analytics.js

analytics.js

97 ms

yU_6Y5ABp-E

yU_6Y5ABp-E

245 ms

BANNER2small.png

BANNER2small.png

332 ms

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

161 ms

SlGWmQWMvZQIdix7AFxXmMh3SDw.ttf

SlGWmQWMvZQIdix7AFxXmMh3SDw.ttf

187 ms

SlGWmQWMvZQIdix7AFxXmMh3eDs1Yg.ttf

SlGWmQWMvZQIdix7AFxXmMh3eDs1Yg.ttf

177 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

180 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

180 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

186 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

63 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

77 ms

subscribe_embed

subscribe_embed

150 ms

sdk.js

sdk.js

67 ms

4610806298948407

4610806298948407

142 ms

collect

collect

57 ms

postmessageRelay

postmessageRelay

169 ms

js

js

139 ms

www-subscribe-embed_split_v0.css

www-subscribe-embed_split_v0.css

5 ms

www-subscribe-embed_v0.js

www-subscribe-embed_v0.js

16 ms

AIdro_nJU6VlowG_ldnKPluRN0k1Yk2aeFHlLQNqFr0cTwiSxgQ=s48-c-k-c0x00ffffff-no-rj

AIdro_nJU6VlowG_ldnKPluRN0k1Yk2aeFHlLQNqFr0cTwiSxgQ=s48-c-k-c0x00ffffff-no-rj

449 ms

subscribe_button_branded_lozenge.png

subscribe_button_branded_lozenge.png

24 ms

www-player.css

www-player.css

44 ms

www-embed-player.js

www-embed-player.js

60 ms

base.js

base.js

158 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

74 ms

2254111616-postmessagerelay.js

2254111616-postmessagerelay.js

355 ms

rpc:shindig_random.js

rpc:shindig_random.js

219 ms

ad_status.js

ad_status.js

170 ms

GkV5yKS0-OANEhjyXXxuzTYu8mVL2o5guieYvUh3n1c.js

GkV5yKS0-OANEhjyXXxuzTYu8mVL2o5guieYvUh3n1c.js

132 ms

embed.js

embed.js

51 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

35 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

25 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

24 ms

id

id

36 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

21 ms

Accessibility Review

bodysinging.com accessibility score

92

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.

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

bodysinging.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

bodysinging.com SEO score

88

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bodysinging.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 Bodysinging.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

bodysinging.com

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