4.6 sec in total
601 ms
3.1 sec
876 ms
Click here to check amazing Hairafter content for India. Otherwise, check out these important facts you probably never knew about hairafter.ca
Voted best hair salon in Toronto. We are one of Toronto’s best hair salons and industry leaders for over 45 years.
Visit hairafter.caWe analyzed Hairafter.ca page load time and found that the first response time was 601 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
hairafter.ca performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value11.0 s
0/100
25%
Value9.2 s
13/100
10%
Value1,370 ms
16/100
30%
Value0
100/100
15%
Value13.9 s
10/100
10%
601 ms
28 ms
147 ms
42 ms
148 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 66% of them (57 requests) were addressed to the original Hairafter.ca, 20% (17 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Hairafter.ca.
Page size can be reduced by 1.4 MB (37%)
3.8 MB
2.4 MB
In fact, the total size of Hairafter.ca main page is 3.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. 75% 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 42.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 42.1 kB or 83% of the original size.
Potential reduce by 17.9 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. Hairafter images are well optimized though.
Potential reduce by 830.3 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 830.3 kB or 73% of the original size.
Potential reduce by 510.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. Hairafter.ca needs all CSS files to be minified and compressed as it can save up to 510.5 kB or 85% of the original size.
Number of requests can be reduced by 35 (54%)
65
30
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hairafter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.hairafter.ca
601 ms
css
28 ms
layerslider.css
147 ms
css
42 ms
sb-instagram.css
148 ms
font-awesome.min.css
9 ms
style.css
151 ms
stylesheet.min.css
617 ms
style_dynamic.php
315 ms
font-awesome.min.css
9 ms
widget.css
124 ms
style.min.css
220 ms
stylesheet_hairafter.css
218 ms
responsive.min.css
289 ms
style_dynamic_responsive.php
356 ms
js_composer.css
363 ms
custom_css.php
863 ms
greensock.js
460 ms
jquery.js
646 ms
jquery-migrate.min.js
436 ms
layerslider.kreaturamedia.jquery.js
579 ms
layerslider.transitions.js
511 ms
sb-instagram.js
468 ms
qode-like.js
519 ms
plugins.js
1117 ms
jquery.carouFredSel-6.2.1.js
730 ms
lemmon-slider.js
591 ms
jquery.mousewheel.min.js
620 ms
jquery.touchSwipe.min.js
654 ms
isotope.pkgd.min.js
735 ms
default_dynamic.php
951 ms
default.min.js
950 ms
custom_js.php
952 ms
js
77 ms
js_composer_front.js
948 ms
jquery.matchHeight-min.js
948 ms
css
19 ms
analytics.js
75 ms
logo4transparent.png
147 ms
logo4transparent1.png
148 ms
logo4dark.png
148 ms
logo_black.png
149 ms
home1.jpg
822 ms
award11.png
267 ms
award10.png
220 ms
award8.png
221 ms
award9.png
222 ms
award4.png
267 ms
award3.png
267 ms
award6.png
268 ms
award7.png
271 ms
award5.png
473 ms
award2.png
309 ms
award1.png
310 ms
sss3.jpg
596 ms
collection2pic.jpg
328 ms
menfeat33.jpg
475 ms
collection3pic.jpg
471 ms
featcol4.jpg
472 ms
collection5pic.jpg
593 ms
cardv3.png
684 ms
scissors2.jpg
474 ms
pattern.png
853 ms
parallax_7A.jpg
1193 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
81 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
81 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
82 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
82 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
81 ms
do7-0avPC2vxor6SN2THGA.ttf
157 ms
Li18TEFObx_yGdzKDoI_ci3USBnSvpkopQaUR-2r7iU.ttf
156 ms
ZKwULyCG95tk6mOqHQfRBC3USBnSvpkopQaUR-2r7iU.ttf
136 ms
cbAbzEjxTdN5KKmS-gA0tS3USBnSvpkopQaUR-2r7iU.ttf
156 ms
rr0ijB5_2nAJsAoZ6vECXaCWcynf_cDxXwCLxiixG1c.ttf
149 ms
STBOO2waD2LpX45SXYjQBS3USBnSvpkopQaUR-2r7iU.ttf
151 ms
WmVKXVcOuffP_qmCpFuyzS3USBnSvpkopQaUR-2r7iU.ttf
151 ms
QoPu455RxV2raYSIFXAMBS3USBnSvpkopQaUR-2r7iU.ttf
151 ms
Ji5epXNcpHu3r63lhS0cTi3USBnSvpkopQaUR-2r7iU.ttf
152 ms
ElegantIcons.woff
526 ms
collect
71 ms
collect
64 ms
F-uvpIj1hF17IDyvQvI50Q.ttf
37 ms
MViwy4K6e56oHcyeMzjbCQ.ttf
36 ms
DK0eTGXiZjN6yA8zAEyM2S5FJMZltoAAwO2fP7iHu2o.ttf
76 ms
collect
204 ms
logo.png
99 ms
hairafter.ca accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hairafter.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
hairafter.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Hairafter.ca 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 Hairafter.ca 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.
hairafter.ca
Open Graph description is not detected on the main page of Hairafter. 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: