Tools & Wizards About Us
johnoxleynissan.com.au screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

johnoxleynissan.com.au

Nissan Dealer Port Macquarie, NSW | Nissan Sales, Service & Parts Port Macquarie | John Oxley Nissan

Page Load Speed

2.7 sec in total

First Response

66 ms

Resources Loaded

2.1 sec

Page Rendered

481 ms

johnoxleynissan.com.au screenshot

About Website

Click here to check amazing John Oxley Nissan content. Otherwise, check out these important facts you probably never knew about johnoxleynissan.com.au

Looking for an authorised Nissan dealer near you? View Car Sales, Service, Finance & Parts information at John Oxley Nissan today!

Visit johnoxleynissan.com.au

Key Findings

We analyzed Johnoxleynissan.com.au page load time and found that the first response time was 66 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

johnoxleynissan.com.au performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

johnoxleynissan.com.au

66 ms

www.johnoxleynissan.com.au

1247 ms

js

911 ms

Roboto-Bold-Digits.woff2

1466 ms

YEWiGGfUBmneJKJ81ryxQERm

885 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 20% of them (5 requests) were addressed to the original Johnoxleynissan.com.au, 56% (14 requests) were made to Cdn.cms-uploads.i-motor.me and 8% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source S3.ap-southeast-2.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 327.4 kB (11%)

Content Size

3.1 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Johnoxleynissan.com.au main page is 3.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. 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.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 327.3 kB

  • Original 385.8 kB
  • After minification 385.6 kB
  • After compression 58.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 327.3 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.7 MB
  • After minification 2.7 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. John Oxley Nissan images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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.

Requests Breakdown

Number of requests can be reduced by 5 (24%)

Requests Now

21

After Optimization

16

  • Images
  • JavaScript

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Oxley Nissan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

johnoxleynissan.com.au

johnoxleynissan.com.au

66 ms

www.johnoxleynissan.com.au

www.johnoxleynissan.com.au

1247 ms

js

js

911 ms

Roboto-Bold-Digits.woff2

Roboto-Bold-Digits.woff2

1466 ms

YEWiGGfUBmneJKJ81ryxQERm

YEWiGGfUBmneJKJ81ryxQERm

885 ms

i4dsrWqg9KGJW1jbo5EzsiLA

i4dsrWqg9KGJW1jbo5EzsiLA

123 ms

Nb2R1YynUYWfCnGg7XSEr5gY

Nb2R1YynUYWfCnGg7XSEr5gY

125 ms

JGP3BQXN25A9kDscVUTfZ1vb

JGP3BQXN25A9kDscVUTfZ1vb

130 ms

DYn8HZGHu3zhBUgjGgBAs7eS

DYn8HZGHu3zhBUgjGgBAs7eS

128 ms

hYFrUquUaEFzNQivNgrkspBM

hYFrUquUaEFzNQivNgrkspBM

127 ms

XSykdC72F3zwmh6aiuzxUyW3

XSykdC72F3zwmh6aiuzxUyW3

139 ms

xu424WotN6iKdGb5emexeos6

xu424WotN6iKdGb5emexeos6

136 ms

nTBa6a2CvLXvsciTm9621o6N

nTBa6a2CvLXvsciTm9621o6N

142 ms

ir7WJQcFtdwooUQF6JB6YErx

ir7WJQcFtdwooUQF6JB6YErx

132 ms

oxiyjv1dmQGSbmWd3PHjGqUi

oxiyjv1dmQGSbmWd3PHjGqUi

133 ms

ArRjMS24iYiG8aQnGHR5i6h9

ArRjMS24iYiG8aQnGHR5i6h9

133 ms

6wb1YFY1E7QHokwNbfqc2maC

6wb1YFY1E7QHokwNbfqc2maC

136 ms

9abUQdqFXyAQ4xWDF9mo5hVy

9abUQdqFXyAQ4xWDF9mo5hVy

139 ms

icon-arrow-2023.svg

icon-arrow-2023.svg

839 ms

0z9AI2qMkV4nGNgZkAGjAxoAAAAjgAF

0z9AI2qMkV4nGNgZkAGjAxoAAAAjgAF

2 ms

webpack-runtime-d72b8e94dbb9f1de3976.js

webpack-runtime-d72b8e94dbb9f1de3976.js

141 ms

framework-c4dd45296d323ee61723.js

framework-c4dd45296d323ee61723.js

232 ms

app-818b91ffcf8200fa36df.js

app-818b91ffcf8200fa36df.js

253 ms

analytics.js

analytics.js

29 ms

js

js

61 ms

Accessibility Review

johnoxleynissan.com.au accessibility score

97

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-hidden="true"] elements contain focusable descendents

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

johnoxleynissan.com.au best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

johnoxleynissan.com.au SEO score

95

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

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 Johnoxleynissan.com.au 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 Johnoxleynissan.com.au 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

johnoxleynissan.com.au

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