Tools & Wizards About Us
windycityduelingpianos.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

windycityduelingpianos.com

Windy City Dueling Pianos for Hire - Home - Chicago Illinois Midwest

Page Load Speed

2.2 sec in total

First Response

56 ms

Resources Loaded

2 sec

Page Rendered

135 ms

windycityduelingpianos.com screenshot

About Website

Welcome to windycityduelingpianos.com homepage info - get ready to check Windy City Dueling Pianos best content right away, or after learning these important things about windycityduelingpianos.com

Windy City Dueling Pianos entertainers perform in Chicago, Illinois! Dueling pianos for hire in Chicago, Illinois and Midwest!

Visit windycityduelingpianos.com

Key Findings

We analyzed Windycityduelingpianos.com page load time and found that the first response time was 56 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

windycityduelingpianos.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.433

22/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

www.windycityduelingpianos.com

56 ms

site.css

16 ms

duel.js

23 ms

js

66 ms

getSeal

281 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Windycityduelingpianos.com, 37% (15 requests) were made to P3pprd001.cloudstorage.secureserver.net and 37% (15 requests) were made to Nebula.wsimg.com. The less responsive or slowest element that took the longest time to load (796 ms) relates to the external source Nebula.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 289.7 kB (20%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Windycityduelingpianos.com 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 89.7 kB

  • Original 108.3 kB
  • After minification 108.3 kB
  • After compression 18.6 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 89.7 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 4.9 kB

  • Original 1.0 MB
  • After minification 999.7 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. Windy City Dueling Pianos images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 129.0 kB

  • Original 229.8 kB
  • After minification 229.4 kB
  • After compression 100.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 129.0 kB or 56% of the original size.

CSS Optimization

-77%

Potential reduce by 66.0 kB

  • Original 85.3 kB
  • After minification 85.3 kB
  • After compression 19.3 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. Windycityduelingpianos.com needs all CSS files to be minified and compressed as it can save up to 66.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (48%)

Requests Now

40

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.windycityduelingpianos.com

www.windycityduelingpianos.com

56 ms

site.css

site.css

16 ms

duel.js

duel.js

23 ms

js

js

66 ms

getSeal

getSeal

281 ms

scc-c2.min.js

scc-c2.min.js

41 ms

jq.js

jq.js

404 ms

7388416b2efff92bde2d06c4a90660eb

7388416b2efff92bde2d06c4a90660eb

197 ms

subNavigation.js

subNavigation.js

251 ms

media.gallery.js

media.gallery.js

247 ms

facebookSDKHelper.js

facebookSDKHelper.js

248 ms

056f63793b11dcad8520e660bf2b2e24

056f63793b11dcad8520e660bf2b2e24

512 ms

206cd0fbd523e0f9eda48b596474d5cb

206cd0fbd523e0f9eda48b596474d5cb

553 ms

235f9783b4c56e0fa901da138c5901ae

235f9783b4c56e0fa901da138c5901ae

475 ms

e28ae4cc469d60508dc4250fb147148a

e28ae4cc469d60508dc4250fb147148a

681 ms

siteseal_gd_3_h_l_m.gif

siteseal_gd_3_h_l_m.gif

65 ms

cookiemanager.js

cookiemanager.js

62 ms

iebackground.js

iebackground.js

61 ms

util.instances.js

util.instances.js

61 ms

util.model.js

util.model.js

122 ms

documentHelper.js

documentHelper.js

122 ms

util.fbSDKLoader.js

util.fbSDKLoader.js

122 ms

util.window.js

util.window.js

181 ms

helper.js

helper.js

61 ms

growl.js

growl.js

100 ms

wsb-slideshow-arrows.png

wsb-slideshow-arrows.png

60 ms

645db7a4b6c5df3f4ed0f7fc40782427

645db7a4b6c5df3f4ed0f7fc40782427

746 ms

f8460f5f25438925ae1c1a6df410b8d4

f8460f5f25438925ae1c1a6df410b8d4

796 ms

browser.js

browser.js

62 ms

sf.core.pkg.js

sf.core.pkg.js

79 ms

app.css

app.css

18 ms

sdk.js

sdk.js

14 ms

sdk.js

sdk.js

5 ms

b4e93c7341c22a60be3775bfd9592697

b4e93c7341c22a60be3775bfd9592697

394 ms

94a5a97399df2d20e527c6316a11fa9f

94a5a97399df2d20e527c6316a11fa9f

356 ms

54096df47d6542f2d8ce14f1d4b8adde

54096df47d6542f2d8ce14f1d4b8adde

642 ms

408384ce281e820bd908718d77bee52f

408384ce281e820bd908718d77bee52f

599 ms

69bddaf8e2d63ed90e74fe46d717a9ed

69bddaf8e2d63ed90e74fe46d717a9ed

376 ms

064d5bc63057b86e046324db71266fed

064d5bc63057b86e046324db71266fed

303 ms

6ce513fd77afb4a9b0e461038ed41219

6ce513fd77afb4a9b0e461038ed41219

568 ms

5510d725d5fb4e4ac14d8b5fa84f9f4c

5510d725d5fb4e4ac14d8b5fa84f9f4c

531 ms

Accessibility Review

windycityduelingpianos.com accessibility score

45

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

windycityduelingpianos.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

windycityduelingpianos.com SEO score

77

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

High

Image elements do not have [alt] attributes

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

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

windycityduelingpianos.com

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