Tools & Wizards About Us
nakai.ca screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

nakai.ca

NAKAI Group - Aveda Salons in Moncton and Saint John, NB

Page Load Speed

3.7 sec in total

First Response

91 ms

Resources Loaded

3.3 sec

Page Rendered

356 ms

nakai.ca screenshot

About Website

Visit nakai.ca now to see the best up-to-date NAKAI content and also check out these interesting facts you probably never knew about nakai.ca

NAKAI, the best spas and salons in Moncton and Saint John, NB, are full service Aveda spas and salons offering spa services, haircuts, custom Aveda color, and more. Gift cards available in-store and b...

Visit nakai.ca

Key Findings

We analyzed Nakai.ca page load time and found that the first response time was 91 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

nakai.ca performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

nakai.ca

91 ms

nakai.ca

2633 ms

sbi-styles.min.css

47 ms

style.min.css

80 ms

classic-themes.min.css

83 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 71% of them (41 requests) were addressed to the original Nakai.ca, 9% (5 requests) were made to Use.typekit.net and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Nakai.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.7 kB (2%)

Content Size

2.5 MB

After Optimization

2.4 MB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Nakai.ca main page is 2.5 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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. This web page is already compressed.

Image Optimization

-2%

Potential reduce by 41.5 kB

  • Original 2.3 MB
  • After minification 2.3 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. NAKAI images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 628 B

  • Original 133.6 kB
  • After minification 133.4 kB
  • After compression 132.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-12%

Potential reduce by 2.5 kB

  • Original 21.9 kB
  • After minification 21.6 kB
  • After compression 19.4 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. Nakai.ca needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (67%)

Requests Now

51

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nakai.ca

nakai.ca

91 ms

nakai.ca

nakai.ca

2633 ms

sbi-styles.min.css

sbi-styles.min.css

47 ms

style.min.css

style.min.css

80 ms

classic-themes.min.css

classic-themes.min.css

83 ms

styles.css

styles.css

90 ms

team.css

team.css

83 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

83 ms

style.min.css

style.min.css

108 ms

style.min.css

style.min.css

113 ms

style.css

style.css

115 ms

oti5lye.css

oti5lye.css

112 ms

im-theme-styles.css

im-theme-styles.css

114 ms

wp-featherlight.min.css

wp-featherlight.min.css

113 ms

ytprefs.min.css

ytprefs.min.css

118 ms

jquery.min.js

jquery.min.js

164 ms

jquery-migrate.min.js

jquery-migrate.min.js

141 ms

js

js

83 ms

ytprefs.min.js

ytprefs.min.js

142 ms

js

js

133 ms

font-awesome.min.css

font-awesome.min.css

64 ms

js

js

101 ms

row_classes.js

row_classes.js

142 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

224 ms

frontend.min.js

frontend.min.js

153 ms

scripts.js

scripts.js

229 ms

jquery.sticky.min.js

jquery.sticky.min.js

64 ms

what-input.min.js

what-input.min.js

296 ms

foundation.min.js

foundation.min.js

298 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

77 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

86 ms

scripts.min.js

scripts.min.js

297 ms

wpFeatherlight.pkgd.min.js

wpFeatherlight.pkgd.min.js

297 ms

fitvids.min.js

fitvids.min.js

297 ms

sbi-scripts.min.js

sbi-scripts.min.js

394 ms

p.css

p.css

26 ms

LIGHT_LARGE_LOGO_KAYAK.png.png

LIGHT_LARGE_LOGO_KAYAK.png.png

201 ms

nakai-phone-widget.js

nakai-phone-widget.js

200 ms

sbi-sprite.png

sbi-sprite.png

199 ms

logo.png

logo.png

199 ms

background.jpg

background.jpg

198 ms

0002-PromoButton-P1-GiftCard.jpg

0002-PromoButton-P1-GiftCard.jpg

198 ms

p3.jpg

p3.jpg

241 ms

p2.jpg

p2.jpg

262 ms

0002-AccoladesImage.jpg

0002-AccoladesImage.jpg

222 ms

footleft.jpg

footleft.jpg

263 ms

SJ-Boutique-5.jpg

SJ-Boutique-5.jpg

337 ms

Aveda_logo_white-200x60-1.png

Aveda_logo_white-200x60-1.png

238 ms

0002-HomeHeader-P1-Color.jpg

0002-HomeHeader-P1-Color.jpg

152 ms

Desktop-2.jpg

Desktop-2.jpg

191 ms

Desktop3.jpg

Desktop3.jpg

153 ms

d

d

19 ms

d

d

23 ms

d

d

27 ms

d

d

31 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

19 ms

sms-cta.css

sms-cta.css

68 ms

cartographer.png

cartographer.png

76 ms

Accessibility Review

nakai.ca accessibility score

73

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

[role] values are not valid

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

nakai.ca 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

nakai.ca SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nakai.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nakai.ca 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

nakai.ca

Open Graph description is not detected on the main page of NAKAI. 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: