Tools & Wizards About Us
brightonpianos.com.au screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

brightonpianos.com.au

Brighton Pianos | Adelaide Piano Tuning

Page Load Speed

8 sec in total

First Response

2 sec

Resources Loaded

5.8 sec

Page Rendered

184 ms

brightonpianos.com.au screenshot

About Website

Visit brightonpianos.com.au now to see the best up-to-date Brighton Pianos content and also check out these interesting facts you probably never knew about brightonpianos.com.au

Over 40 years experience tuning upright and grand pianos in Adelaide and regional South Australia areas.

Visit brightonpianos.com.au

Key Findings

We analyzed Brightonpianos.com.au page load time and found that the first response time was 2 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

brightonpianos.com.au performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,070 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

brightonpianos.com.au

1989 ms

reset.css

487 ms

screen.css

1331 ms

flexslider.css

485 ms

jquery.fancybox.css

484 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 48% of them (30 requests) were addressed to the original Brightonpianos.com.au, 19% (12 requests) were made to Maps.googleapis.com and 10% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Brightonpianos.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 816.4 kB (30%)

Content Size

2.7 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brightonpianos.com.au main page is 2.7 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. 50% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 12.3 kB

  • Original 15.8 kB
  • After minification 14.7 kB
  • After compression 3.5 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 12.3 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 27.4 kB

  • Original 1.6 MB
  • After minification 1.6 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. Brighton Pianos images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 739.2 kB

  • Original 1.1 MB
  • After minification 987.5 kB
  • After compression 320.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 739.2 kB or 70% of the original size.

CSS Optimization

-65%

Potential reduce by 37.5 kB

  • Original 57.5 kB
  • After minification 46.5 kB
  • After compression 20.0 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. Brightonpianos.com.au needs all CSS files to be minified and compressed as it can save up to 37.5 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (52%)

Requests Now

56

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brighton 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 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

brightonpianos.com.au

brightonpianos.com.au

1989 ms

reset.css

reset.css

487 ms

screen.css

screen.css

1331 ms

flexslider.css

flexslider.css

485 ms

jquery.fancybox.css

jquery.fancybox.css

484 ms

jcarousel.css

jcarousel.css

1332 ms

modernizr.js

modernizr.js

1237 ms

jquery.min.js

jquery.min.js

1228 ms

jquery.flexslider.js

jquery.flexslider.js

1222 ms

jquery_002.js

jquery_002.js

1373 ms

jcarousel.js

jcarousel.js

1461 ms

jquery.fancybox.js

jquery.fancybox.js

1472 ms

styles.css

styles.css

1176 ms

css

css

25 ms

genericons.css

genericons.css

1265 ms

style.css

style.css

1267 ms

jquery.js

jquery.js

1310 ms

jquery-migrate.min.js

jquery-migrate.min.js

1531 ms

ga.js

ga.js

9 ms

__utm.gif

__utm.gif

12 ms

maps

maps

55 ms

logo.png

logo.png

967 ms

responsive_icon.png

responsive_icon.png

247 ms

tuning.png

tuning.png

2291 ms

rentals.png

rentals.png

1224 ms

removals2.png

removals2.png

1337 ms

new-pianos2.png

new-pianos2.png

2528 ms

hire1.png

hire1.png

1697 ms

home-text1.png

home-text1.png

1212 ms

grand-hire.png

grand-hire.png

2305 ms

products-2.jpg

products-2.jpg

1463 ms

products-3.jpg

products-3.jpg

1576 ms

footerlogo.png

footerlogo.png

1705 ms

border.jpg

border.jpg

1823 ms

embed

embed

372 ms

js

js

57 ms

init_embed.js

init_embed.js

42 ms

common.js

common.js

68 ms

map.js

map.js

88 ms

google4.png

google4.png

148 ms

overlay.js

overlay.js

127 ms

util.js

util.js

143 ms

onion.js

onion.js

142 ms

search_impl.js

search_impl.js

143 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

202 ms

stats.js

stats.js

136 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

96 ms

kh

kh

163 ms

transparent.png

transparent.png

64 ms

controls.js

controls.js

26 ms

vt

vt

111 ms

vt

vt

106 ms

css

css

73 ms

vt

vt

84 ms

vt

vt

94 ms

vt

vt

84 ms

mapcnt6.png

mapcnt6.png

19 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

16 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

23 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

26 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

25 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

14 ms

Accessibility Review

brightonpianos.com.au accessibility score

86

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

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

brightonpianos.com.au 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

SEO Factors

brightonpianos.com.au SEO score

86

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

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 Brightonpianos.com.au 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 Brightonpianos.com.au 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

brightonpianos.com.au

Open Graph description is not detected on the main page of Brighton Pianos. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: