Tools & Wizards About Us
zenph.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

zenph.com

Steinway Spirio Player Pianos | Steinway & Sons

Page Load Speed

3.9 sec in total

First Response

11 ms

Resources Loaded

3.1 sec

Page Rendered

807 ms

zenph.com screenshot

About Website

Click here to check amazing Zenph content. Otherwise, check out these important facts you probably never knew about zenph.com

Steinway Spirio player pianos are high-resolution self-playing pianos that bring the world’s finest artistry and engineering to your home or performance hall.

Visit zenph.com

Key Findings

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

Performance Metrics

zenph.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value2,810 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

zenph.com

11 ms

spirio

28 ms

spirio

354 ms

jquery-1.9.1.min~2023-10-24-19-04-54-874~cache.js

19 ms

jquery-ui-1.11.4.min~2023-10-24-19-05-14-996~cache.js

36 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Zenph.com, 26% (23 requests) were made to Steinway.com and 14% (13 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 279.3 kB (36%)

Content Size

766.3 kB

After Optimization

487.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Zenph.com main page is 766.3 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. 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. HTML takes 393.3 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 243.7 kB

  • Original 393.3 kB
  • After minification 356.0 kB
  • After compression 149.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 243.7 kB or 62% of the original size.

JavaScript Optimization

-12%

Potential reduce by 35.0 kB

  • Original 294.8 kB
  • After minification 294.8 kB
  • After compression 259.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 35.0 kB or 12% of the original size.

CSS Optimization

-1%

Potential reduce by 643 B

  • Original 78.2 kB
  • After minification 78.2 kB
  • After compression 77.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. Zenph.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

63

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zenph.com

zenph.com

11 ms

spirio

spirio

28 ms

spirio

spirio

354 ms

jquery-1.9.1.min~2023-10-24-19-04-54-874~cache.js

jquery-1.9.1.min~2023-10-24-19-04-54-874~cache.js

19 ms

jquery-ui-1.11.4.min~2023-10-24-19-05-14-996~cache.js

jquery-ui-1.11.4.min~2023-10-24-19-05-14-996~cache.js

36 ms

plugins.min~2024-04-29-16-47-50-000~cache.js

plugins.min~2024-04-29-16-47-50-000~cache.js

71 ms

comp.min~2023-12-05-15-48-25-447~cache.js

comp.min~2023-12-05-15-48-25-447~cache.js

65 ms

new-main~2024-04-08-20-58-51-305~cache.css

new-main~2024-04-08-20-58-51-305~cache.css

69 ms

fonts.css

fonts.css

109 ms

kvw5odd.js

kvw5odd.js

110 ms

js

js

69 ms

1C6DA38D27D635299.css

1C6DA38D27D635299.css

108 ms

gtm.js

gtm.js

160 ms

lp.1.js

lp.1.js

160 ms

ss-logo2.svg

ss-logo2.svg

128 ms

TfQj3vAI7sk

TfQj3vAI7sk

267 ms

ss-lyre2.svg

ss-lyre2.svg

198 ms

spirio_r_fma.jpg

spirio_r_fma.jpg

200 ms

spirio_catalog_fma.jpg

spirio_catalog_fma.jpg

239 ms

retail_april24_fma.jpg

retail_april24_fma.jpg

238 ms

ipad_spirio-r.jpg

ipad_spirio-r.jpg

198 ms

PB_STEINWAY_SON_030215_04_213-2_CMJN300_square.jpg

PB_STEINWAY_SON_030215_04_213-2_CMJN300_square.jpg

198 ms

artist_grid_osborne.jpg

artist_grid_osborne.jpg

235 ms

brass_pedals_square.jpg

brass_pedals_square.jpg

231 ms

PB_STEINWAY_SON_030215_17_226_CMJN300_square.jpg

PB_STEINWAY_SON_030215_17_226_CMJN300_square.jpg

231 ms

model_dimensions_m_square_spirio_r2.jpg

model_dimensions_m_square_spirio_r2.jpg

228 ms

model_dimensions_b_square_spirio_r.jpg

model_dimensions_b_square_spirio_r.jpg

367 ms

model_dimensions_d_square2.jpg

model_dimensions_d_square2.jpg

369 ms

arrow.svg

arrow.svg

235 ms

analytics.js

analytics.js

122 ms

js

js

118 ms

AWVLOMg=

AWVLOMg=

8 ms

nnD3LqmWSLYNandTPHUxD4r56K9Lf8yqJCL52yY5EvmnnRzFOaOZZKMQ576nt5dbjBm6u3kK9WFzOYM8yZ1I9yKNIHvCI4UaEW7rb8akjeUhfGMQr4Yz8rxRn0jeJZjF3fIjjc8STQIe91A5IVLPi86ZzylZIjB58U6UOqw0LGx7c6b+308BMpfwFlSzjI

nnD3LqmWSLYNandTPHUxD4r56K9Lf8yqJCL52yY5EvmnnRzFOaOZZKMQ576nt5dbjBm6u3kK9WFzOYM8yZ1I9yKNIHvCI4UaEW7rb8akjeUhfGMQr4Yz8rxRn0jeJZjF3fIjjc8STQIe91A5IVLPi86ZzylZIjB58U6UOqw0LGx7c6b+308BMpfwFlSzjI

8 ms

icomoon.ttf

icomoon.ttf

254 ms

g.pixel

g.pixel

263 ms

9d335078-d17e-4993-bb73-1625da307330.js

9d335078-d17e-4993-bb73-1625da307330.js

431 ms

roundtrip.js

roundtrip.js

396 ms

destination

destination

285 ms

bat.js

bat.js

462 ms

1576.js

1576.js

522 ms

fbevents.js

fbevents.js

423 ms

www-player.css

www-player.css

203 ms

www-embed-player.js

www-embed-player.js

341 ms

base.js

base.js

552 ms

collect

collect

175 ms

insight.min.js

insight.min.js

373 ms

icomoon.woff

icomoon.woff

111 ms

d

d

167 ms

d

d

298 ms

d

d

249 ms

p.gif

p.gif

281 ms

tp2

tp2

176 ms

collect

collect

206 ms

index.js

index.js

105 ms

ga-audiences

ga-audiences

1704 ms

2NXUZ677DJD5TN37IVVUEY

2NXUZ677DJD5TN37IVVUEY

321 ms

pp.html

pp.html

309 ms

ad_status.js

ad_status.js

217 ms

qPVc89Xtqb-imYcu3PoxhWFQIHn6RU05s_zP8PhWsV0.js

qPVc89Xtqb-imYcu3PoxhWFQIHn6RU05s_zP8PhWsV0.js

156 ms

embed.js

embed.js

72 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

159 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

161 ms

NNIPMNN6XRBO7IDIYDX4VX.js

NNIPMNN6XRBO7IDIYDX4VX.js

277 ms

Create

Create

107 ms

id

id

89 ms

GenerateIT

GenerateIT

15 ms

adadvisor.gif

adadvisor.gif

46 ms

li_sync

li_sync

22 ms

out

out

6 ms

sendrolling.js

sendrolling.js

5 ms

out

out

10 ms

out

out

12 ms

out

out

12 ms

out

out

15 ms

out

out

15 ms

out

out

15 ms

out

out

17 ms

out

out

18 ms

out

out

21 ms

out

out

18 ms

pixel

pixel

80 ms

tap.php

tap.php

74 ms

Pug

Pug

70 ms

xuid

xuid

6 ms

pixel

pixel

16 ms

rum

rum

32 ms

sync

sync

18 ms

sd

sd

29 ms

in

in

4 ms

bounce

bounce

39 ms

Accessibility Review

zenph.com accessibility score

71

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes are not valid or misspelled

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

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

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

zenph.com best practices score

83

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

Page has valid source maps

SEO Factors

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

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zenph.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 Zenph.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

zenph.com

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