Tools & Wizards About Us
jsrlife.co.nz screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

jsrlife.co.nz

Quality Used Vehicles | JSR Life Motors

Page Load Speed

5.5 sec in total

First Response

2.1 sec

Resources Loaded

3.1 sec

Page Rendered

273 ms

jsrlife.co.nz screenshot

About Website

Visit jsrlife.co.nz now to see the best up-to-date JSR Life content and also check out these interesting facts you probably never knew about jsrlife.co.nz

Whether you're buying your first car or upgrading, be sure to talk to us about fast, affordable finance and leasing solutions. You’ll deal directly with the person who makes the lending decision and ...

Visit jsrlife.co.nz

Key Findings

We analyzed Jsrlife.co.nz page load time and found that the first response time was 2.1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

jsrlife.co.nz performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value760 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

jsrlife.co.nz

2113 ms

wp-emoji-release.min.js

191 ms

css

23 ms

style.css

93 ms

js_composer_front.css

214 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 86% of them (65 requests) were addressed to the original Jsrlife.co.nz, 5% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Jsrlife.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 684.2 kB (60%)

Content Size

1.1 MB

After Optimization

461.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jsrlife.co.nz main page is 1.1 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. 45% of websites need less resources to load. Javascripts take 422.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 32.9 kB

  • Original 40.4 kB
  • After minification 37.5 kB
  • After compression 7.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 32.9 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 7.8 kB

  • Original 273.8 kB
  • After minification 266.0 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. JSR Life images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 309.4 kB

  • Original 422.3 kB
  • After minification 319.7 kB
  • After compression 112.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 309.4 kB or 73% of the original size.

CSS Optimization

-82%

Potential reduce by 334.2 kB

  • Original 409.5 kB
  • After minification 288.8 kB
  • After compression 75.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. Jsrlife.co.nz needs all CSS files to be minified and compressed as it can save up to 334.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (69%)

Requests Now

70

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jsrlife.co.nz

jsrlife.co.nz

2113 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

191 ms

css

css

23 ms

style.css

style.css

93 ms

js_composer_front.css

js_composer_front.css

214 ms

styles.css

styles.css

93 ms

style.css

style.css

121 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

109 ms

fonts.css

fonts.css

169 ms

icons.css

icons.css

173 ms

icon-transport.css

icon-transport.css

125 ms

style.css

style.css

197 ms

css

css

34 ms

vc-responsive.css

vc-responsive.css

158 ms

jquery.js

jquery.js

260 ms

jquery-migrate.min.js

jquery-migrate.min.js

211 ms

jquery.cycle.all.js

jquery.cycle.all.js

338 ms

dealer-pages.css

dealer-pages.css

613 ms

js_composer_front.js

js_composer_front.js

313 ms

jquery.form.min.js

jquery.form.min.js

304 ms

scripts.js

scripts.js

310 ms

jquery.fitvids.js

jquery.fitvids.js

324 ms

jquery.form.js

jquery.form.js

337 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

354 ms

jquery.checkbox.js

jquery.checkbox.js

358 ms

jquery.countdown.js

jquery.countdown.js

349 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

335 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

354 ms

jquery.mousewheel-3.0.4.pack.js

jquery.mousewheel-3.0.4.pack.js

343 ms

jquery.validate.js

jquery.validate.js

371 ms

common.js

common.js

407 ms

js.js

js.js

406 ms

login.js

login.js

399 ms

style980.css

style980.css

240 ms

style800.css

style800.css

257 ms

style700.css

style700.css

270 ms

style600.css

style600.css

258 ms

style500.css

style500.css

288 ms

style400.css

style400.css

290 ms

ga.js

ga.js

8 ms

3.png

3.png

289 ms

293.jpg

293.jpg

96 ms

290.jpg

290.jpg

95 ms

279.jpg

279.jpg

71 ms

293.jpg

293.jpg

95 ms

290.jpg

290.jpg

68 ms

280.jpg

280.jpg

132 ms

279.jpg

279.jpg

118 ms

278.jpg

278.jpg

121 ms

275.jpg

275.jpg

286 ms

274.jpg

274.jpg

284 ms

273.jpg

273.jpg

288 ms

125.jpg

125.jpg

289 ms

mtf-login.png

mtf-login.png

548 ms

__utm.gif

__utm.gif

20 ms

bg_header.jpg

bg_header.jpg

232 ms

bg_navigation.jpg

bg_navigation.jpg

229 ms

navigation_marker.gif

navigation_marker.gif

228 ms

bg_menu.jpg

bg_menu.jpg

231 ms

bg_content.jpg

bg_content.jpg

230 ms

bg_banner_2.jpg

bg_banner_2.jpg

232 ms

banner_img_2.png

banner_img_2.png

235 ms

bg_banner_1.jpg

bg_banner_1.jpg

234 ms

banner_img_1.png

banner_img_1.png

233 ms

bg_footer.jpg

bg_footer.jpg

231 ms

bg_footer_top.jpg

bg_footer_top.jpg

235 ms

line_1.gif

line_1.gif

235 ms

marker_1.gif

marker_1.gif

236 ms

msNrBgwx3ln3jjNy5b_Syw.ttf

msNrBgwx3ln3jjNy5b_Syw.ttf

25 ms

kTYfCWJhlldPf5LnG4ZnHC3USBnSvpkopQaUR-2r7iU.ttf

kTYfCWJhlldPf5LnG4ZnHC3USBnSvpkopQaUR-2r7iU.ttf

24 ms

8j1DeLkEfJur3t3fXqNMnFNK0UFebWKJmoqv4AQtiLHQBLuADIUlixAQGOWbkIAAgAYyCwASNEsAMjcLIEKAlFUkSyCgIHKrEGAUSxJAGIUViwQIhYsQYDRLEmAYhRWLgEAIhYsQYBRFlZWVm4Af+FsASNsQUARAAA

8j1DeLkEfJur3t3fXqNMnFNK0UFebWKJmoqv4AQtiLHQBLuADIUlixAQGOWbkIAAgAYyCwASNEsAMjcLIEKAlFUkSyCgIHKrEGAUSxJAGIUViwQIhYsQYDRLEmAYhRWLgEAIhYsQYBRFlZWVm4Af+FsASNsQUARAAA

2 ms

icons.svg

icons.svg

256 ms

GpWpM_6S4VQLPNAQ3iWvVaCWcynf_cDxXwCLxiixG1c.ttf

GpWpM_6S4VQLPNAQ3iWvVaCWcynf_cDxXwCLxiixG1c.ttf

10 ms

lILlYDvubYemzYzN7GbLkGeP1y_Bkidl4ESyB_O2G_c.ttf

lILlYDvubYemzYzN7GbLkGeP1y_Bkidl4ESyB_O2G_c.ttf

22 ms

ajax-loader.gif

ajax-loader.gif

104 ms

carousel_navi.jpg

carousel_navi.jpg

29 ms

Accessibility Review

jsrlife.co.nz accessibility score

58

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

jsrlife.co.nz best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

jsrlife.co.nz SEO score

67

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

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Jsrlife.co.nz 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 Jsrlife.co.nz 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

jsrlife.co.nz

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