Report Summary

  • 40

    Performance

    Renders faster than
    59% 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

  • 91

    SEO

    Google-friendlier than
    70% of websites

pianosmithfield.com

Piano Smithfield | Piano Bar | Live Music Venue | England

Page Load Speed

833 ms in total

First Response

141 ms

Resources Loaded

639 ms

Page Rendered

53 ms

About Website

Visit pianosmithfield.com now to see the best up-to-date Piano Smithfield content and also check out these interesting facts you probably never knew about pianosmithfield.com

Find out about live music and events at Piano Smithfield, our late-night piano bar evenings, table reservations and private hire.

Visit pianosmithfield.com

Key Findings

We analyzed Pianosmithfield.com page load time and found that the first response time was 141 ms and then it took 692 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.

Performance Metrics

pianosmithfield.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

www.pianosmithfield.com

141 ms

minified.js

40 ms

focus-within-polyfill.js

34 ms

polyfill.min.js

30 ms

thunderbolt-commons.8add2233.bundle.min.js

24 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pianosmithfield.com, 45% (18 requests) were made to Static.parastorage.com and 30% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (237 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 924.2 kB (52%)

Content Size

1.8 MB

After Optimization

837.0 kB

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

HTML Optimization

-80%

Potential reduce by 530.7 kB

  • Original 665.1 kB
  • After minification 663.3 kB
  • After compression 134.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 530.7 kB or 80% of the original size.

Image Optimization

-35%

Potential reduce by 251.0 kB

  • Original 712.2 kB
  • After minification 461.2 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, Piano Smithfield needs image optimization as it can save up to 251.0 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-37%

Potential reduce by 142.5 kB

  • Original 384.0 kB
  • After minification 384.0 kB
  • After compression 241.5 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 142.5 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (50%)

Requests Now

20

After Optimization

10

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

Accessibility Review

pianosmithfield.com accessibility score

100

Accessibility Issues

Best Practices

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

High

Page has valid source maps

SEO Factors

pianosmithfield.com SEO score

91

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 doesn't use 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 Pianosmithfield.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 Pianosmithfield.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

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