Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

jvairanderson.com

Calgary's Jewellery Store since 1925 | J. Vair Anderson Jewellers

Page Load Speed

1.8 sec in total

First Response

35 ms

Resources Loaded

444 ms

Page Rendered

1.3 sec

About Website

Welcome to jvairanderson.com homepage info - get ready to check J Vair Anderson best content right away, or after learning these important things about jvairanderson.com

J. Vair Anderson Jewellers has been Calgary's Finest Jewellery store since 1925. Providing Calgary with Luxury Watches and Jewellery.

Visit jvairanderson.com

Key Findings

We analyzed Jvairanderson.com page load time and found that the first response time was 35 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

jvairanderson.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

jvairanderson.com

35 ms

jvairanderson.com

100 ms

normalize.min.css

14 ms

jquery.selectBox.css

30 ms

font-awesome.css

47 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 79% of them (53 requests) were addressed to the original Jvairanderson.com, 13% (9 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Assets.jvairanderson.com. The less responsive or slowest element that took the longest time to load (196 ms) relates to the external source Static.rolex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.2 kB (35%)

Content Size

425.0 kB

After Optimization

276.8 kB

In fact, the total size of Jvairanderson.com main page is 425.0 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. 60% of websites need less resources to load. Javascripts take 174.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 126.9 kB

  • Original 159.5 kB
  • After minification 151.8 kB
  • After compression 32.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 126.9 kB or 80% of the original size.

JavaScript Optimization

-1%

Potential reduce by 1.3 kB

  • Original 174.3 kB
  • After minification 174.3 kB
  • After compression 172.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

-22%

Potential reduce by 20.0 kB

  • Original 91.3 kB
  • After minification 91.2 kB
  • After compression 71.3 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. Jvairanderson.com needs all CSS files to be minified and compressed as it can save up to 20.0 kB or 22% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

4

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

Accessibility Review

jvairanderson.com accessibility score

91

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

Best Practices

jvairanderson.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

jvairanderson.com SEO score

100

Search Engine Optimization Advices

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

Social Sharing Optimization

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