Tools & Wizards About Us
petermochrie.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

petermochrie.com

Actor, Public Speaking Coach, Presenter and Auctioneer | Peter Mochrie

Page Load Speed

1.9 sec in total

First Response

42 ms

Resources Loaded

1.3 sec

Page Rendered

555 ms

petermochrie.com screenshot

About Website

Visit petermochrie.com now to see the best up-to-date Peter Mochrie content and also check out these interesting facts you probably never knew about petermochrie.com

PETER MOCHRIE has enjoyed great success as one of Australia’s leading Actors. Peter is also a Presenter, Coach and an Auctioneer.

Visit petermochrie.com

Key Findings

We analyzed Petermochrie.com page load time and found that the first response time was 42 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 40% of websites can load faster.

Performance Metrics

petermochrie.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value21,420 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.466

19/100

15%

TTI (Time to Interactive)

Value40.2 s

0/100

10%

Network Requests Diagram

petermochrie.com

42 ms

petermochrie.com

50 ms

js

111 ms

css

46 ms

css

62 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 58% of them (37 requests) were addressed to the original Petermochrie.com, 13% (8 requests) were made to Youtube.com and 11% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (658 ms) relates to the external source Player.vimeo.com.

Page Optimization Overview & Recommendations

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

Content Size

2.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Petermochrie.com main page is 2.8 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. 60% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 34.9 kB

  • Original 45.0 kB
  • After minification 43.9 kB
  • After compression 10.1 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 34.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.2 MB
  • After minification 2.2 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. Peter Mochrie images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.9 kB

  • Original 475.0 kB
  • After minification 475.0 kB
  • After compression 469.0 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

-2%

Potential reduce by 2.2 kB

  • Original 107.3 kB
  • After minification 107.3 kB
  • After compression 105.1 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. Petermochrie.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (56%)

Requests Now

54

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

petermochrie.com

petermochrie.com

42 ms

petermochrie.com

petermochrie.com

50 ms

js

js

111 ms

css

css

46 ms

css

css

62 ms

css

css

68 ms

style.min.css

style.min.css

21 ms

jquery-ui.css

jquery-ui.css

32 ms

form.min.css

form.min.css

36 ms

style.css

style.css

43 ms

default.css

default.css

45 ms

button.min.css

button.min.css

48 ms

jquery.min.js

jquery.min.js

47 ms

jquery-migrate.min.js

jquery-migrate.min.js

45 ms

core.min.js

core.min.js

49 ms

datepicker.min.js

datepicker.min.js

61 ms

underscore.min.js

underscore.min.js

62 ms

form.min.js

form.min.js

100 ms

jquery.fancybox.css

jquery.fancybox.css

103 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

64 ms

jquery.fitvids.js

jquery.fitvids.js

103 ms

main.js

main.js

107 ms

api.js

api.js

47 ms

backbone.min.js

backbone.min.js

106 ms

wp-api.js

wp-api.js

106 ms

btnsx.min.js

btnsx.min.js

105 ms

YvepvEBqTA0

YvepvEBqTA0

153 ms

OLMQAg_Q-LA

OLMQAg_Q-LA

603 ms

GT8G33bMGlY

GT8G33bMGlY

656 ms

nqrGYneXNRM

nqrGYneXNRM

545 ms

183962711

183962711

658 ms

recaptcha__en.js

recaptcha__en.js

78 ms

logo_big.png

logo_big.png

55 ms

menu-icon.png

menu-icon.png

55 ms

portrait2.jpg

portrait2.jpg

56 ms

Screen-Shot-2019-08-30-at-10.48.32-am.png

Screen-Shot-2019-08-30-at-10.48.32-am.png

114 ms

Peter-Mochrie-ICMI-1024x516.png

Peter-Mochrie-ICMI-1024x516.png

109 ms

Peter-Mochrie-Voiceovers.png

Peter-Mochrie-Voiceovers.png

64 ms

Screen-Shot-2019-05-03-at-12.35.36-pm-1024x576.png

Screen-Shot-2019-05-03-at-12.35.36-pm-1024x576.png

114 ms

facebook.png

facebook.png

109 ms

linkedin.png

linkedin.png

110 ms

youtube.png

youtube.png

112 ms

mail.png

mail.png

113 ms

home-link-1.jpg

home-link-1.jpg

112 ms

home-link-2.jpg

home-link-2.jpg

112 ms

home-link-3.jpg

home-link-3.jpg

128 ms

home-link-4.jpg

home-link-4.jpg

137 ms

home-link-5.jpg

home-link-5.jpg

128 ms

home-link-6.jpg

home-link-6.jpg

135 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

68 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

78 ms

3XFtErwl05Ad_vSCF6Fq7xX2Qtzf.woff

3XFtErwl05Ad_vSCF6Fq7xX2Qtzf.woff

78 ms

3XFzErwl05Ad_vSCF6Fq7xX2R-zb_P8.woff

3XFzErwl05Ad_vSCF6Fq7xX2R-zb_P8.woff

81 ms

www-player.css

www-player.css

17 ms

www-embed-player.js

www-embed-player.js

36 ms

base.js

base.js

62 ms

ad_status.js

ad_status.js

453 ms

PuB7oGltKecOij53fBhYlFeX0y0D4cx2uIMnP4ao6fo.js

PuB7oGltKecOij53fBhYlFeX0y0D4cx2uIMnP4ao6fo.js

396 ms

embed.js

embed.js

348 ms

id

id

165 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

29 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

100 ms

api.js

api.js

90 ms

Accessibility Review

petermochrie.com accessibility score

80

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

<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

Best Practices

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

High

Page has valid source maps

SEO Factors

petermochrie.com SEO score

90

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Petermochrie.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 Petermochrie.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

petermochrie.com

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