Tools & Wizards About Us
jamesmorrison.com.au screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

jamesmorrison.com.au

Home | jamesmorrison

Page Load Speed

1.9 sec in total

First Response

135 ms

Resources Loaded

1.7 sec

Page Rendered

84 ms

jamesmorrison.com.au screenshot

About Website

Click here to check amazing Jamesmorrison content. Otherwise, check out these important facts you probably never knew about jamesmorrison.com.au

Visit jamesmorrison.com.au

Key Findings

We analyzed Jamesmorrison.com.au page load time and found that the first response time was 135 ms and then it took 1.8 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

jamesmorrison.com.au performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

www.jamesmorrison.com

135 ms

minified.js

60 ms

focus-within-polyfill.js

54 ms

polyfill.min.js

53 ms

thunderbolt-commons.7700cd07.bundle.min.js

205 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Jamesmorrison.com.au, 29% (12 requests) were made to Sentry-next.wixpress.com and 27% (11 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (511 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 693.2 kB (46%)

Content Size

1.5 MB

After Optimization

810.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Jamesmorrison.com.au main page is 1.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. 50% of websites need less resources to load. HTML takes 854.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 689.5 kB

  • Original 854.0 kB
  • After minification 852.3 kB
  • After compression 164.4 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 689.5 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 390.9 kB
  • After minification 390.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. Jamesmorrison images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 259.0 kB
  • After minification 259.0 kB
  • After compression 255.4 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 10 (38%)

Requests Now

26

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.jamesmorrison.com

www.jamesmorrison.com

135 ms

minified.js

minified.js

60 ms

focus-within-polyfill.js

focus-within-polyfill.js

54 ms

polyfill.min.js

polyfill.min.js

53 ms

thunderbolt-commons.7700cd07.bundle.min.js

thunderbolt-commons.7700cd07.bundle.min.js

205 ms

main.16c08821.bundle.min.js

main.16c08821.bundle.min.js

226 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

200 ms

lodash.min.js

lodash.min.js

204 ms

react.production.min.js

react.production.min.js

200 ms

react-dom.production.min.js

react-dom.production.min.js

206 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

205 ms

27b316_f2c43d7e7b8d4ca2ad3284af0df3fb10~mv2.jpg

27b316_f2c43d7e7b8d4ca2ad3284af0df3fb10~mv2.jpg

279 ms

bundle.min.js

bundle.min.js

176 ms

27b316_6de793b8d8374dea93909ee7b5e15666~mv2.jpg

27b316_6de793b8d8374dea93909ee7b5e15666~mv2.jpg

225 ms

27b316_348b3ccd995c40448776f5837adc82ea~mv2.jpg

27b316_348b3ccd995c40448776f5837adc82ea~mv2.jpg

332 ms

27b316_0b83657f3b6244f3b1bc5049fabe9b06~mv2.jpg

27b316_0b83657f3b6244f3b1bc5049fabe9b06~mv2.jpg

361 ms

27b316_ad4d36622aee4187902dd1c092ce8be2~mv2.jpg

27b316_ad4d36622aee4187902dd1c092ce8be2~mv2.jpg

368 ms

27b316_b5b423a0d2a2422f9386235441f7ccd8~mv2.jpg

27b316_b5b423a0d2a2422f9386235441f7ccd8~mv2.jpg

256 ms

27b316_15cf5f0718644d4cb57c408a03ec222e~mv2.jpg

27b316_15cf5f0718644d4cb57c408a03ec222e~mv2.jpg

334 ms

27b316_baa3cbce7db84e55b78195027df4dca4~mv2.jpg

27b316_baa3cbce7db84e55b78195027df4dca4~mv2.jpg

454 ms

27b316_db373f15e61d4c17b2fa134e159a5e28~mv2.jpg

27b316_db373f15e61d4c17b2fa134e159a5e28~mv2.jpg

483 ms

27b316_018177710e7a4a988cbc18a71ed2d666~mv2.jpg

27b316_018177710e7a4a988cbc18a71ed2d666~mv2.jpg

511 ms

27b316_2614639064414f5b9af58bf621a0a25a~mv2.jpg

27b316_2614639064414f5b9af58bf621a0a25a~mv2.jpg

502 ms

aDjpMND83pDErGXlVEr-SRsxEYwM7FgeyaSgU71cLG0.woff

aDjpMND83pDErGXlVEr-SRsxEYwM7FgeyaSgU71cLG0.woff

19 ms

9VWMTeb5jtXkNoTv949NpRsxEYwM7FgeyaSgU71cLG0.woff

9VWMTeb5jtXkNoTv949NpRsxEYwM7FgeyaSgU71cLG0.woff

9 ms

135 ms

136 ms

125 ms

126 ms

127 ms

128 ms

160 ms

157 ms

159 ms

156 ms

162 ms

154 ms

deprecation-en.v5.html

deprecation-en.v5.html

7 ms

bolt-performance

bolt-performance

47 ms

deprecation-style.v5.css

deprecation-style.v5.css

13 ms

right-arrow.svg

right-arrow.svg

13 ms

Accessibility Review

jamesmorrison.com.au accessibility score

89

Accessibility Issues

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

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

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

High

Page has valid source maps

SEO Factors

jamesmorrison.com.au SEO score

93

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

jamesmorrison.com.au

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