4.3 sec in total
1.8 sec
2.3 sec
209 ms
Click here to check amazing Paul Hahn content. Otherwise, check out these important facts you probably never knew about paulhahn.com
Family owned and operated company established in 1913, conveniently located in downtown Toronto and one of the oldest piano stores in Canada.
Visit paulhahn.comWe analyzed Paulhahn.com page load time and found that the first response time was 1.8 sec and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
paulhahn.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value7.8 s
3/100
25%
Value6.0 s
46/100
10%
Value430 ms
65/100
30%
Value0
100/100
15%
Value8.3 s
39/100
10%
1818 ms
53 ms
53 ms
50 ms
55 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 91% of them (48 requests) were addressed to the original Paulhahn.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Hello.myfonts.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Paulhahn.com.
Page size can be reduced by 636.0 kB (22%)
2.8 MB
2.2 MB
In fact, the total size of Paulhahn.com main page is 2.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. 35% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 53.1 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 53.1 kB or 79% of the original size.
Potential reduce by 68.8 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. Paul Hahn images are well optimized though.
Potential reduce by 326.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 326.8 kB or 65% of the original size.
Potential reduce by 187.2 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. Paulhahn.com needs all CSS files to be minified and compressed as it can save up to 187.2 kB or 83% of the original size.
Number of requests can be reduced by 39 (75%)
52
13
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Paul Hahn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
paulhahn.com
1818 ms
nextgen_gallery_related_images.css
53 ms
styles.css
53 ms
tipTip.css
50 ms
shortcodes.css
55 ms
lists.css
56 ms
menu-866aa62ff6c16fcab414a76f625ee345.css
61 ms
grid-responsive.css
59 ms
bootstrap.css
89 ms
master-7d3017cf7b30432fec1516b3448ce783.css
75 ms
mediaqueries.css
59 ms
style.css
58 ms
anythingslider.css
61 ms
mootools.js
134 ms
ajax.js
72 ms
jquery.js
108 ms
jquery-migrate.min.js
80 ms
persist.js
80 ms
store.js
81 ms
ngg_store.js
84 ms
jquery.anythingslider.min.js
105 ms
lightbox_context.js
105 ms
icon.js
105 ms
jquery.tipTip.minified.js
105 ms
mootools-mobile.js
106 ms
rokmediaqueries.js
105 ms
roksprocket.js
107 ms
roksprocket.request.js
107 ms
lists.js
107 ms
lists-readmore.js
107 ms
mob-menu.js
108 ms
rokmediaqueries.js
108 ms
rokmediaqueries.js
108 ms
responsive.js
108 ms
css
25 ms
comment-reply.min.js
59 ms
jquery.form.min.js
156 ms
scripts.js
59 ms
thickbox.js
77 ms
26d99e
22 ms
ga.js
9 ms
__utm.gif
153 ms
noise.png
78 ms
ph-logo.png
69 ms
fb_icon.png
67 ms
tw_icon.png
67 ms
paulhahn_slide_piano.jpg
247 ms
nikolai_website_slide.jpg
267 ms
heintzman_action_slide.jpg
268 ms
loadingAnimation.gif
24 ms
26D99E_16_0.woff
34 ms
26D99E_17_0.woff
30 ms
nr-892.min.js
17 ms
paulhahn.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
paulhahn.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
paulhahn.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Paulhahn.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 Paulhahn.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.
paulhahn.com
Open Graph description is not detected on the main page of Paul Hahn. 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: