Tools & Wizards About Us
pianoweek.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

pianoweek.com

PIANO WEEK International Festival & Summer School

Page Load Speed

5.8 sec in total

First Response

223 ms

Resources Loaded

4.6 sec

Page Rendered

947 ms

pianoweek.com screenshot

About Website

Click here to check amazing PIANO WEEK content. Otherwise, check out these important facts you probably never knew about pianoweek.com

A world-class piano summer school for pianists of all ages and abilities. Join us in the UK, Italy and Japan and get inspired by our bespoke programme.

Visit pianoweek.com

Key Findings

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

Performance Metrics

pianoweek.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value43.0 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value2,500 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

pianoweek.com

223 ms

pianoweek.com

1802 ms

wp-emoji-release.min.js

246 ms

converter.css

273 ms

tp_twitter_plugin.css

277 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 70% of them (76 requests) were addressed to the original Pianoweek.com, 12% (13 requests) were made to Youtube.com and 4% (4 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Pianoweek.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (15%)

Content Size

15.9 MB

After Optimization

13.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pianoweek.com main page is 15.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 14.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 225.7 kB

  • Original 265.0 kB
  • After minification 238.8 kB
  • After compression 39.3 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 225.7 kB or 85% of the original size.

Image Optimization

-12%

Potential reduce by 1.8 MB

  • Original 14.7 MB
  • After minification 12.8 MB

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, PIANO WEEK needs image optimization as it can save up to 1.8 MB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-50%

Potential reduce by 364.8 kB

  • Original 723.8 kB
  • After minification 622.9 kB
  • After compression 359.0 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 364.8 kB or 50% of the original size.

CSS Optimization

-6%

Potential reduce by 13.2 kB

  • Original 230.8 kB
  • After minification 230.7 kB
  • After compression 217.6 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. Pianoweek.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 59 (61%)

Requests Now

96

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pianoweek.com

pianoweek.com

223 ms

pianoweek.com

pianoweek.com

1802 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

246 ms

converter.css

converter.css

273 ms

tp_twitter_plugin.css

tp_twitter_plugin.css

277 ms

mashsb.min.css

mashsb.min.css

376 ms

styles.css

styles.css

282 ms

woocommerce-layout.css

woocommerce-layout.css

284 ms

woocommerce.css

woocommerce.css

339 ms

dashicons.min.css

dashicons.min.css

455 ms

tickets.css

tickets.css

368 ms

tribe-events-full.min.css

tribe-events-full.min.css

377 ms

tribe-events-theme.min.css

tribe-events-theme.min.css

379 ms

css

css

35 ms

style.css

style.css

432 ms

shortcodes.css

shortcodes.css

459 ms

shortcodes.css

shortcodes.css

467 ms

shortcodes_responsive.css

shortcodes_responsive.css

470 ms

magnific_popup.css

magnific_popup.css

471 ms

masterslider.main.css

masterslider.main.css

523 ms

custom.css

custom.css

546 ms

jquery.min.js

jquery.min.js

28 ms

mashsb.min.js

mashsb.min.js

642 ms

jquery.deparam.js

jquery.deparam.js

561 ms

jquery.cookie.js

jquery.cookie.js

562 ms

js

js

100 ms

lvs3cyn.css

lvs3cyn.css

212 ms

aitwitter.css

aitwitter.css

503 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

555 ms

jquery_cookie.min.js

jquery_cookie.min.js

574 ms

jquery.form.min.js

jquery.form.min.js

594 ms

scripts.js

scripts.js

597 ms

add-to-cart.min.js

add-to-cart.min.js

596 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

645 ms

woocommerce.min.js

woocommerce.min.js

665 ms

attendees-list.js

attendees-list.js

677 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

687 ms

custom.js

custom.js

876 ms

smoothscroll.js

smoothscroll.js

691 ms

meta.js

meta.js

734 ms

jquery.fitvids.js

jquery.fitvids.js

755 ms

waypoints.min.js

waypoints.min.js

686 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

606 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

875 ms

wp-embed.min.js

wp-embed.min.js

619 ms

salvattore.min.js

salvattore.min.js

633 ms

style.css

style.css

597 ms

analytics.js

analytics.js

100 ms

p.css

p.css

95 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

114 ms

home-background2.jpg

home-background2.jpg

206 ms

btn_buynow_SM.gif

btn_buynow_SM.gif

51 ms

pixel.gif

pixel.gif

54 ms

UPDATED-POST-1-photo.jpg

UPDATED-POST-1-photo.jpg

1258 ms

UPDATED-POST-2-photo.jpg

UPDATED-POST-2-photo.jpg

1024 ms

FOLIGNO3-400x250.jpg

FOLIGNO3-400x250.jpg

131 ms

tokyo3-1-400x250.jpg

tokyo3-1-400x250.jpg

132 ms

tw-bird.png

tw-bird.png

151 ms

qr-code.jpg

qr-code.jpg

203 ms

fbC.png

fbC.png

204 ms

fbBW.png

fbBW.png

273 ms

twitterC.png

twitterC.png

300 ms

twitterBW.png

twitterBW.png

305 ms

vimeo.png

vimeo.png

305 ms

vimeoBW.png

vimeoBW.png

316 ms

youtubeC.png

youtubeC.png

372 ms

youtubeBW.png

youtubeBW.png

440 ms

wechatC.png

wechatC.png

440 ms

wechatBW.png

wechatBW.png

442 ms

PW-mini-LOGO.png

PW-mini-LOGO.png

842 ms

logo-moreton.jpg

logo-moreton.jpg

843 ms

Bangkok-logo.png

Bangkok-logo.png

844 ms

logo-foligno.jpg

logo-foligno.jpg

844 ms

logo-sankt-goar.jpg

logo-sankt-goar.jpg

844 ms

beijing-logo.jpg

beijing-logo.jpg

848 ms

logo-500px.png

logo-500px.png

846 ms

collect

collect

26 ms

sourcesanspro-light-webfont.woff

sourcesanspro-light-webfont.woff

825 ms

sourcesanspro-extralight-webfont.woff

sourcesanspro-extralight-webfont.woff

925 ms

modules.ttf

modules.ttf

919 ms

e3tUJ8HGENE

e3tUJ8HGENE

230 ms

live_stream

live_stream

251 ms

js

js

99 ms

d

d

5 ms

lato-light-webfont.woff

lato-light-webfont.woff

878 ms

e55ac1260e692ce0816db1180.js

e55ac1260e692ce0816db1180.js

127 ms

ajax.js

ajax.js

875 ms

ajax-mob.js

ajax-mob.js

908 ms

embed.js

embed.js

47 ms

www-player.css

www-player.css

21 ms

www-embed-player.js

www-embed-player.js

20 ms

base.js

base.js

19 ms

e3tUJ8HGENE

e3tUJ8HGENE

4 ms

live_stream

live_stream

2 ms

e3tUJ8HGENE

e3tUJ8HGENE

539 ms

live_stream

live_stream

77 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

66 ms

ad_status.js

ad_status.js

364 ms

embed.js

embed.js

241 ms

RnAEGhf-XX_BTbKPyrocfzPG9wxH_4lxfCPxVnxswRc.js

RnAEGhf-XX_BTbKPyrocfzPG9wxH_4lxfCPxVnxswRc.js

112 ms

id

id

43 ms

Create

Create

164 ms

Create

Create

165 ms

GenerateIT

GenerateIT

14 ms

GenerateIT

GenerateIT

15 ms

tribe-events-full-mobile.min.css

tribe-events-full-mobile.min.css

92 ms

tribe-events-theme-mobile.min.css

tribe-events-theme-mobile.min.css

92 ms

Accessibility Review

pianoweek.com accessibility score

66

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

pianoweek.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pianoweek.com SEO score

91

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

Image elements do not have [alt] attributes

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

pianoweek.com

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